Windows 10: Random BSODs while gaming/browsing

Let me get straight to it. I have been on Windows 10 since the free upgrade offer. I have had 0 issues up until recently where my PC would randomly crash and most of the BSOD's would list CRITICAL_PROCESS_DIED. Most of the time I would be playing League of Legends and other times just browsing the internet. This would happen at least once a day (I use this PC only for about 1-4 hours and the BSODs were random).


After doing some research online I ran "sfc /scannow" and the system passed the integrity test. A few days in to the issue I cleared my prefetch folder and the system was once again stable for a few days and then the BSODs happened again. Clearing the prefetch folder would give me a few stable days and the back to the usual BSODs. After a few days I noticed that my graphics card (Asus HD7950 OC2) died (vertical lines on the screen), this made me believe that the PC must have been crashing to the graphic card failing slowly.


I went ahead and purchased a new entry level card (Sapphire RX460) and I didnt see the crash for a few days, but it came back to the same issue again. This time around the PC would BSOD sometimes or it would just freeze while I was in game, the cursor would move around but the PC itself was frozen (ctrl+alt+del etc nothing worked). At other times the CRITICAL_PROCESS_DIED BSOD would come up and the PC would be stuck at 0% collection of the dump. I am not sure if it helps but the audio would be kind of stuck too.


The most annoying part is I cannot just keep pressing the power button to power off or use the reset button because my SSD doesnt get detected when doing that and I have to do a power cycle on the SSD which would take up about 40-60 mins. Trust me when I tell you that I have tried everything and I am contacting you guys as a last resort because I have no idea what to do now.


I am someone who tries to google as much as possible to resolve an issue and this one has me dumbfounded. Any help with this would be highly appreciated.


PC Specs,
Processor - Intel i7-3770
Mobo - Asus P8Z77-V
RAM - Corsair Vengeance 8 GB DDR3
PSU - Corsair 650W Modular
Graphics Card - Sapphire RX460
SSD - Intel 330 180 GB
Hard Disk - Hitachi HD721010DlE630 1 TB 7200 RPM

EDIT: The disks pass SMART checks and have no errors listed in their SMART attributes ie no pending sectors/offline uncorrectable etc.

EDIT 2: The PC just froze again when browsing but it came back to life and I immediately opened the event viewer to see if I could find something useful and I found three warnings,
1 - Reset to device, \Device\RaidPort0, was issued.
2 - The IO operation at logical block address 0x46ea30 for Disk 0 (PDO name: \Device\00000034) was retried.
3 - Reset to device, \Device\RaidPort0, was issued.

Could this mean that the SSD is failing? A SMART output of the SSD - Error logging capability: (0x01) Error logging supported. General P - Pastebin.com

:)

 

random Freezing leads to BSOD. I give up.

Hi, I just bought this laptop Lenovo Legion Y720 and installed a NVMe SSD for Windows.

I'm using Windows 10 HSL edition came from Lenovo.

For no reason I got random freezing while playing games or just browsing and do other chill stuff and that leads to BSOD.

Please help me identify and solve this thing...

I attached multiple Minidump file from the BSOD.

091917-6406-01.dmp

092217-5984-01.dmp

please help me solve this..

 

BSODs when I use different programs. ntoskrnl.exe named as one of the causes in each dumpfile.

Hey, I've had some problems with my PC for a while now. Bought it dec 2015 and problems started in January.

I have been getting random BSODs and random crashes to desktop. Usually when browsing the web (and watching videos) and playing games. It's happened alot so i have a link to one drive with different information:

- The computed is built by me. Not branded. The motherboard is msi z170a pc mate.

- This is is a link to a one driver folder with: 1. System information file. 2. Driver view report. 3. Windows dump files (for bsod's last 14 days)

Offentligt

 

Is the firmware of the SSD up to date?

 

Yes, I am on the latest firmware available for this drive.

 

The 'pre-fail' status of some SMART attributes are not critical to failure of the SSD itself.
However, this does not mean the SSD is not the cause, because the SMART is not the only thing that should be checked.







Diagnostics Test

HDD TEST
*Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

HDTune Results,
Attachment 103929Attachment 103928


Since I do not have another windows machine I scheduled the "chkdsk /R" on the next boot. On the next boot it seemed like the progress was stuck at 16%, but I let it run overnight. The next day the machine showed that it failed to boot properly and wanted me to do a system restore. Thinking something was wrong I connected the SSD to a different PC to check the SMART status and it looked fine. So I connected the SSD back to the PC and windows booted up without forcing me to do a restore.

I checked the event viewer but it seems like boot time chkdsk logs arent saved. How do I get the log from chkdsk in my case?
I also noticed a new message in the event viewer (same timestamp as the one when the PC booted up after reconnecting the SSD),
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000074 (0x0000000000000002, 0xffffa980545dba70, 0x0000000000000002, 0xffffffffc0000185). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 2c9b84a7-b401-4204-8d99-11db6a12d4ea.

Seems like there was another BSOD somewhere that I didnt notice, I have attached the minidump.

 

Please upload a new zip from the DM Log Collector, due to circumstances my system temporary won't be able to open files that are not supported by Windows Explorer.

A log is saved in the event viewer when chkdsk is finished, if no log is present it means that chkdsk couldn't finish its job as it was interrupted.

 

I have uploaded the latest zip from the log collector.

I will try to run chkdsk again and hopefully it completes this time. Are you sure that it logs to the event viewer even when run at boot time (because it is the system drive)? I ask only because the thread you pointed me to (Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums) states this,

 

I have one more question,
Is it normal for a SSD to not get detected when hitting the reset switch on the front panel? When my PC gets a BSOD I cant just hit the reset button and boot back. The disk doesnt get detected and I have to leave the PC on for 20 mins and then shut it down, wait for about 2 more mins and then start it for the disk to get detected and to boot in to Windows. Sometimes I have to do this 2 times. Sometimes I just shut down and use the PC the next day.

Crucial lays out this process informatively here - Why did my SSD "disappear" from my system? - Crucial Community
However, I do not use a Crucial SSD. Is this issue normal for all SSDs? If not I think investing in a SSD which doesnt have this issue is worthwhile because you do not want to be locked out of your PC for 1 hour when something crashes. I am looking at the Samsung 850 Evo 250 GB, but I do not want to purchase it if this issue is common for all SSDs, so some advice on this would be helpful too.

Thanks.

 

I am 100% sure, I ran chkdsk on my system drive today and checked the result in event viewer *Smile
The only difference is that the tag is different, the tag is 'Wininit'.
If you can find a chkdsk log with the tag 'Wininit' then it means chkdsk did save the log *Smile
Code: Log Name: Application Source: Microsoft-Windows-Wininit Date: 01-Oct-16 11:20:09 Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: DESKTOP-FO9QHGA Description: Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 436992 file records processed. File verification completed. 6751 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 501022 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Cleaning up 937 unused index entries from index $SII of file 0x9. Cleaning up 937 unused index entries from index $SDH of file 0x9. Cleaning up 937 unused security descriptors. Security descriptor verification completed. 32016 data files processed. CHKDSK is verifying Usn Journal... 33924832 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 436976 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 53385808 free clusters processed. Free space verification is complete. Windows has scanned the file system and found no problems. No further action is required. 244478975 KB total disk space. 30285932 KB in 133598 files. 102568 KB in 32017 indexes. 0 KB in bad sectors. 547243 KB in use by the system. 65536 KB occupied by the log file. 213543232 KB available on disk. 4096 bytes in each allocation unit. 61119743 total allocation units on disk. 53385808 allocation units available on disk. Internal Info: 00 ab 06 00 df 86 02 00 22 fa 04 00 00 00 00 00 ........"....... dd 00 00 00 66 00 00 00 00 00 00 00 00 00 00 00 ....f........... Windows has finished checking your disk. Please wait while your computer restarts.[/quote]

The dump 0x74 is a bad configuration of the system information.
System information is loaded into the temporary part of the registry everytime the system boots, this so the system knows what it works with. To be able to do this the system information must be loaded into the memory.
I can't remember the exact process of what happens again, so I'm not sure if the system information is verified before it is loaded into the temporary registry.

My point, with the 0x74 the suspected causes are the memory (information being loaded in bad memory) or a registry issue.

I would like to start with a memory diagnostics test, as that is easier. Please read the instructions below carefully.









Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

Let it run for almost 24h and this was the result,
Attachment 104085

 

This is something for myself, so I don't have to look in the dump everytime.
Code: 0: kd> !thread ffffe10e6429d080 e THREAD ffffe10e6429d080 Cid 0004.02c8 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0 Not impersonating GetUlongFromAddress: unable to read from fffff8016e307924 Owning Process ffffe10e622216c0 Image: System Attached Process N/A Image: N/A fffff78000000000: Unable to get shared data Wait Start TickCount 1589676 Context Switch Count 3 IdealProcessor: 0 ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address nt!CmpLoadHiveThread (0xfffff8016e559498) Stack Init ffffa980545dbc90 Current ffffa98055548790 Base ffffa980545dc000 Limit ffffa980545d6000 Call 0 Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5 Child-SP RetAddr Call Site ffffa980`545db9a8 fffff801`6e60356d nt!KeBugCheckEx ffffa980`545db9b0 fffff801`6e0e4255 nt! ?? ::NNGAKEGL::`string'+0x7a4bd // nt!CmpLoadHiveThread ffffa980`545dbc10 fffff801`6e161576 nt!PspSystemThreadStartup+0x41 ffffa980`545dbc60 00000000`00000000 nt!KiStartSystemThread+0x16[/quote]





Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• When it is finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of SFC and post it.

 

SFC came out clean,
Attachment 104092

 

I've done a little more digging:
Code: 0: kd> .bugcheck Bugcheck code 00000074 Arguments 00000000`00000002 ffffa980`545dba70 00000000`00000002 ffffffff`c0000185 0: kd> !error ffffffff`c0000185 Error code: (NTSTATUS) 0xc0000185 (3221225861) - The I/O device reported an I/O error.[/quote] I would ask you to list all peripheral devices connected to your computer

Please (re)move some files to increase the free space to at least 15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background, 15% is to be on the safe side.


Warning Less free space could cause BSODs or other problems, because Windows cannot perform the tasks it needs to do in the background!


Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.