Computer is sick

[loaderXI]

Just started getting a blue screen on this rig...Any input welcomed and needed...I did search for solution but hoping someone has personal insight

Device name    DESKTOP-L62B2NG
Processor    AMD FX(tm)-8350 Eight-Core Processor              4.01 GHz
Installed RAM    16.0 GB (7.90 GB usable)
Device ID    ED6C6CBF-FC70-4C51-9B64-15A629F769DE
Product ID    00330-71327-78584-AAOEM
System type    64-bit operating system, x64-based processor
Edition    Windows 10 Pro
Version    20H2
Installed on    ‎6/‎19/‎2020
OS build    19042.1237
Experience    Windows Feature Experience Pack 120.2212.3530.0
 

[TBB]

If you can get to it - try this

https://windowsreport.com/kmode-exception-windows-10/

[CW4]

Since it's a NTSF failure, you might want to run chkdsk /f from the CMD prompt to check for errors.  Will take a while if it's a large drive.

[loaderXI]

41 minutes ago, CW4 said:

Since it's a NTSF failure, you might want to run chkdsk /f from the CMD prompt to check for errors.  Will take a while if it's a large drive.

Hmmm this is what I get

C:\Users\FX-8350>chkdsk
Access Denied as you do not have sufficient privileges or
the disk may be locked by another process.
You have to invoke this utility running in elevated mode
and make sure the disk is unlocked.

[loaderXI]

C:\WINDOWS\system32>chkdsk
The type of the file system is NTFS.

WARNING!  /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
  684544 file records processed.
File verification completed.
 Phase duration (File record verification): 7.75 seconds.
  7063 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.48 milliseconds.

Stage 2: Examining file name linkage ...
  2222 reparse records processed.
  941508 index entries processed.
Index verification completed.
 Phase duration (Index verification): 13.88 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 2.01 seconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.48 milliseconds.
  2222 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 14.69 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 71.83 milliseconds.
  128483 data files processed.
 Phase duration (Data attribute verification): 0.55 milliseconds.
CHKDSK is verifying Usn Journal...
  39243472 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 293.51 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 999093699 KB total disk space.
 575262080 KB in 434823 files.
    187672 KB in 128484 indexes.
         0 KB in bad sectors.
    826107 KB in use by the system.
     65536 KB occupied by the log file.
 422817840 KB available on disk.

      4096 bytes in each allocation unit.
 249773424 total allocation units on disk.
 105704460 allocation units available on disk.
Total duration: 24.04 seconds (24048 ms).

C:\WINDOWS\system32>

[Barron]

1 hour ago, loaderXI said:

Just started getting a blue screen on this rig...Any input welcomed and needed...I did search for solution but hoping someone has personal insight

Device name    DESKTOP-L62B2NG
Processor    AMD FX(tm)-8350 Eight-Core Processor              4.01 GHz
Installed RAM    16.0 GB (7.90 GB usable)
Device ID    ED6C6CBF-FC70-4C51-9B64-15A629F769DE
Product ID    00330-71327-78584-AAOEM
System type    64-bit operating system, x64-based processor
Edition    Windows 10 Pro
Version    20H2
Installed on    ‎6/‎19/‎2020
OS build    19042.1237
Experience    Windows Feature Experience Pack 120.2212.3530.0
 

Strange I used to have that CPU myself, whats your GPU? There was new drivers released this week also

I had this installed before when I was getting a lot of BSOD's before : https://www.nirsoft.net/utils/blue_screen_view.html

It will show you what drivers or system files caused the most recent BSOD, you can then work your way from there to try fix the issue. Saves you a lot of time rather than going through event history

 

Sorry just noticed the 16gb of ram and (7.90gb usable), its more than likely the issue. You need to go into msconfig to change it back to normal

Tutorial here: https://appuals.com/windows-10-wont-use-full-ram/

Edited October 8, 2021 by Barron

[KaptCrunch]

looks  likw 1 bad stick of ram,  try another set and play with  the ram voltage in small incroments till bsod stops, and check bios Note  need to know MB Revision  RevX.xx is written on MB before you start and matches model for some manufactures use different chip vendors hench the  Rev. 

update for current micro-codes   with correct Rev of MB

[Krackennutz]

Want the good news sorry not one,used to getthis a lot with with W10 pro so went back to basic Home version, you can do everything across web, but that stop code is a Windows security message that the boot laoder has corrupted, so Windows sends Stop Code its a bug on Pro,you can just keep installing windows and it will come back sooner or later but yay all not lost!!

By looks you can run W11 down the iso and put it on a usb stick, boot it up and setup windows 11 via upgrade

[TheHammer]

yup bad memory

 

[Krackennutz]

guess none noticed  in BSOD screen reason failed Ntfs sys !

besides  using a win 11 update, if you have your Windows disk, pop it in select repair advanced then Command Prompt  open that type in it  sfc/scannow, hopefully if its set in command prompt to administrator it should run sfc and fix any bad files

Besides doom i put above worst case is HD is failing many believe they works for donkeys  years sorry they do not:   https://www.pcgamer.com/how-long-do-hard-drives-last/

 

[CW4]

Loader try running it as "C:\WINDOWS\system32>chkdsk /r"  It will check the entire drive for bad sectors.  If you have more than 1 drive you night have to do this for all of them but probably not.

[KaptCrunch]

On 10/8/2021 at 11:50 AM, CW4 said:

Loader try running it as "C:\WINDOWS\system32>chkdsk /r It will check the entire drive for bad sectors.  If you have more than 1 drive you night have to do this for all of them but probably not.

do only HDD type  not SSD for will kill it Defragmenting 

CHKDSK /F: Check for disk errors, not bad sectors. CHKDSK /R: Locate the bad sectors on the target hard disk and try to recover the readable information from the bad sectors (implies /F). CHKDSK /X: Forces the volume to dismount first, if necessary. It also includes the functionality of /f.

[J3st3r]

990fx motherboard?  Have you ever replaced the CMOS Battery? They have a life of 5-7 years. Dads computer had a similar issue and I went into the bios and it had defaulted everything I had set including memory timings,Boot priority and OS type. It has an older AMD 970 motherboard and a cheap AMD FX-4200 Quad-Core CPU in it.   

Since the memory controller is on the CPU I would try reseating the CPU and reapply fresh thermal compound. Pull the CPU and blow out the socket with compressed air. When you drop it back, place your finger on the top of the CPU and flip the locking leaver back and forth a couple times before locking it down. Pull the memory and reeseat it as well.  

 

Raising the CPU/NB voltage might get you up and running enough to do some testing. It will dramatically increase memory compatibility and stability especially when overclocking the CPU. CPU/NB Manual Voltage - Set between 1.25v-1.3v

 

I hit 5.8ghz stable with my old FX8320 but backed it down to 5.42ghz because it was getting a bit warmer than I liked with my old Corsair H80 AIO. I ran it at 5.42 for over 5 years and never had a single issue with a CPU/NB voltage of 1.275. 

[AyaqGuyaq]

Corrupted midget porn vids?  Man, I'm just askin' for @J3st3r!!  Lol.  Ayaq

[CW4]

Forgot all about that SSD and chkdsk thing... Like KaptCrunch says, just don't do it.