loaderXI Posted October 8, 2021 Member ID: 252 Group: +++ COD2 Head Admin Followers: 71 Topic Count: 392 Topics Per Day: 0.07 Content Count: 6417 Content Per Day: 1.20 Reputation: 6494 Achievement Points: 54334 Solved Content: 0 Days Won: 30 Joined: 09/05/09 Status: Offline Last Seen: 20 hours ago Birthday: 03/22/1965 Device: Windows Share Posted October 8, 2021 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 Link to comment Share on other sites More sharing options... Awards
TBB Posted October 8, 2021 Member ID: 989 Group: *** Clan Members Followers: 25 Topic Count: 263 Topics Per Day: 0.05 Content Count: 18101 Content Per Day: 3.47 Reputation: 20116 Achievement Points: 132635 Solved Content: 0 Days Won: 263 Joined: 01/07/10 Status: Offline Last Seen: 17 hours ago Birthday: 01/27/1946 Device: Windows Share Posted October 8, 2021 If you can get to it - try this https://windowsreport.com/kmode-exception-windows-10/ Link to comment Share on other sites More sharing options... Awards
CW4 Posted October 8, 2021 Member ID: 2902 Group: *** Clan Members Followers: 15 Topic Count: 15 Topics Per Day: 0.00 Content Count: 229 Content Per Day: 0.05 Reputation: 213 Achievement Points: 1672 Solved Content: 0 Days Won: 1 Joined: 10/17/11 Status: Offline Last Seen: April 2 Birthday: 06/11/1952 Device: Windows Share Posted October 8, 2021 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. Link to comment Share on other sites More sharing options... Awards
loaderXI Posted October 8, 2021 Member ID: 252 Group: +++ COD2 Head Admin Followers: 71 Topic Count: 392 Topics Per Day: 0.07 Content Count: 6417 Content Per Day: 1.20 Reputation: 6494 Achievement Points: 54334 Solved Content: 0 Days Won: 30 Joined: 09/05/09 Status: Offline Last Seen: 20 hours ago Birthday: 03/22/1965 Device: Windows Author Share Posted October 8, 2021 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. Link to comment Share on other sites More sharing options... Awards
loaderXI Posted October 8, 2021 Member ID: 252 Group: +++ COD2 Head Admin Followers: 71 Topic Count: 392 Topics Per Day: 0.07 Content Count: 6417 Content Per Day: 1.20 Reputation: 6494 Achievement Points: 54334 Solved Content: 0 Days Won: 30 Joined: 09/05/09 Status: Offline Last Seen: 20 hours ago Birthday: 03/22/1965 Device: Windows Author Share Posted October 8, 2021 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> Link to comment Share on other sites More sharing options... Awards
Barron Posted October 8, 2021 Member ID: 20987 Group: +++ Insurgency Head Admin Followers: 21 Topic Count: 190 Topics Per Day: 0.05 Content Count: 1794 Content Per Day: 0.49 Reputation: 1775 Achievement Points: 14304 Solved Content: 0 Days Won: 0 Joined: 03/21/14 Status: Offline Last Seen: April 12 Birthday: 01/09/1996 Device: Windows Share Posted October 8, 2021 (edited) 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 Link to comment Share on other sites More sharing options... Awards
KaptCrunch Posted October 8, 2021 Member ID: 389 Group: *** Clan Members Followers: 45 Topic Count: 295 Topics Per Day: 0.06 Content Count: 4454 Content Per Day: 0.84 Reputation: 3616 Achievement Points: 36411 Solved Content: 0 Days Won: 39 Joined: 09/14/09 Status: Offline Last Seen: 9 hours ago Birthday: 01/01/1970 Device: Windows Share Posted October 8, 2021 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 MtDeW 1 Link to comment Share on other sites More sharing options... Awards
Krackennutz Posted October 8, 2021 Member ID: 22889 Group: ** Registered Users Followers: 1 Topic Count: 65 Topics Per Day: 0.02 Content Count: 348 Content Per Day: 0.11 Reputation: 412 Achievement Points: 2824 Solved Content: 0 Days Won: 1 Joined: 07/14/15 Status: Offline Last Seen: Saturday at 10:13 PM Device: Windows Share Posted October 8, 2021 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 Link to comment Share on other sites More sharing options...
TheHammer Posted October 8, 2021 Member ID: 4101 Group: *** Clan Members Followers: 22 Topic Count: 54 Topics Per Day: 0.01 Content Count: 1124 Content Per Day: 0.27 Reputation: 792 Achievement Points: 8736 Solved Content: 0 Days Won: 0 Joined: 12/05/12 Status: Offline Last Seen: Wednesday at 08:46 AM Birthday: 07/08/1962 Device: Windows Share Posted October 8, 2021 yup bad memory MtDeW 1 Link to comment Share on other sites More sharing options... Awards
Krackennutz Posted October 8, 2021 Member ID: 22889 Group: ** Registered Users Followers: 1 Topic Count: 65 Topics Per Day: 0.02 Content Count: 348 Content Per Day: 0.11 Reputation: 412 Achievement Points: 2824 Solved Content: 0 Days Won: 1 Joined: 07/14/15 Status: Offline Last Seen: Saturday at 10:13 PM Device: Windows Share Posted October 8, 2021 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/ Link to comment Share on other sites More sharing options...
CW4 Posted October 8, 2021 Member ID: 2902 Group: *** Clan Members Followers: 15 Topic Count: 15 Topics Per Day: 0.00 Content Count: 229 Content Per Day: 0.05 Reputation: 213 Achievement Points: 1672 Solved Content: 0 Days Won: 1 Joined: 10/17/11 Status: Offline Last Seen: April 2 Birthday: 06/11/1952 Device: Windows Share Posted October 8, 2021 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. Link to comment Share on other sites More sharing options... Awards
KaptCrunch Posted October 9, 2021 Member ID: 389 Group: *** Clan Members Followers: 45 Topic Count: 295 Topics Per Day: 0.06 Content Count: 4454 Content Per Day: 0.84 Reputation: 3616 Achievement Points: 36411 Solved Content: 0 Days Won: 39 Joined: 09/14/09 Status: Offline Last Seen: 9 hours ago Birthday: 01/01/1970 Device: Windows Share Posted October 9, 2021 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. Link to comment Share on other sites More sharing options... Awards
J3st3r Posted October 10, 2021 Member ID: 2162 Group: ++ COD4 Admin Followers: 153 Topic Count: 152 Topics Per Day: 0.03 Content Count: 5083 Content Per Day: 1.05 Reputation: 5009 Achievement Points: 44628 Solved Content: 0 Days Won: 22 Joined: 01/25/11 Status: Offline Last Seen: Wednesday at 03:49 AM Birthday: 02/26/1972 Device: Windows Share Posted October 10, 2021 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. loaderXI 1 Link to comment Share on other sites More sharing options... Awards
AyaqGuyaq Posted October 10, 2021 Member ID: 3773 Group: ***- Inactive Clan Members Followers: 39 Topic Count: 30 Topics Per Day: 0.01 Content Count: 3138 Content Per Day: 0.74 Reputation: 2983 Achievement Points: 24456 Solved Content: 0 Days Won: 10 Joined: 10/06/12 Status: Offline Last Seen: January 29, 2022 Birthday: 11/03/1966 Share Posted October 10, 2021 Corrupted midget porn vids? Man, I'm just askin' for @J3st3r!! Lol. Ayaq J3st3r, Hoth, loaderXI and 1 other 3 1 Link to comment Share on other sites More sharing options... Awards
CW4 Posted October 10, 2021 Member ID: 2902 Group: *** Clan Members Followers: 15 Topic Count: 15 Topics Per Day: 0.00 Content Count: 229 Content Per Day: 0.05 Reputation: 213 Achievement Points: 1672 Solved Content: 0 Days Won: 1 Joined: 10/17/11 Status: Offline Last Seen: April 2 Birthday: 06/11/1952 Device: Windows Share Posted October 10, 2021 Forgot all about that SSD and chkdsk thing... Like KaptCrunch says, just don't do it. Link to comment Share on other sites More sharing options... Awards
Recommended Posts