BSOD from cold boot if computer has been off a while

stone616 · 30 Oct 2015

BSOD happens only when the computer cold boots from a prolonged inactive state. If the PC is off for several hours and is turned on it occurs. Computer typically blue screens, sometimes it freezes at the bios splash screen where they Windows 10 circular loading icon appears on this Gigabyte. I've seen multiple reasons for the occurrence such as bad pooler caller and irql not less or equal. The BSOD happens once then after the computer functions as normal with no other issues.

Power supply, graphics card, and SSD were both pulled from a previous build with zero issues in that build. New to this build is the motherboard, processor, and RAM.

Ran Memtest86 with no errors for 8 passes but I just realized it was after the initial cold boot BSOD and not going from the inactive state to the test directly. Will be swapping out the RAM at Microcenter today just to eliminate that possibility.

Windows 10 was a clean install but it happened on the previous install, BIOS is flashed to the most recent release.

axe0 · 30 Oct 2015

Hi stone616,

Welcome to the 10forums.

The NTFS in the stacks could point to a faulty/failing hard drive/SSD

Code:

STACK_TEXT:  
ffffd000`26570650 fffff801`0a73bee7 : ffffc002`07a43420 ffffd000`26570940 ffffe000`94c64180 ffffe000`00000001 : nt!RtlDelete+0x8a
ffffd000`26570680 fffff801`0a68c665 : ffffc002`07a43420 ffffd000`26570940 00000000`00000000 00000000`00000012 : NTFS!NtfsFullDeleteLcb+0x47
ffffd000`265706b0 fffff801`0a73c16b : ffffe000`9e0c0838 ffffe000`94c64180 ffffc002`07a43010 ffffc002`07a43420 : NTFS!NtfsTeardownFromLcb+0x145
ffffd000`26570750 fffff801`0a68d170 : ffffe000`9e0c0838 ffffd000`26570852 ffffc002`07a43420 ffffe000`9e0c0838 : NTFS!NtfsTeardownStructures+0xdb
ffffd000`265707d0 fffff801`0a73e191 : ffffd000`26570978 ffffd000`00000001 ffffd000`26570940 ffffe000`9e0c0838 : NTFS!NtfsDecrementCloseCounts+0xd0
ffffd000`26570810 fffff801`0a73b612 : ffffe000`9e0c0838 ffffc002`07a43150 ffffc002`07a43010 ffffe000`94c64180 : NTFS!NtfsCommonClose+0x401
ffffd000`265708e0 fffff803`2208cdd9 : fffff803`223ec340 ffffe000`949af040 fffff803`223ec200 fffff803`223ec340 : NTFS!NtfsFspCloseInternal+0x1a6
ffffd000`26570a70 fffff803`220f9558 : ffffffff`ffffffff 00000000`00000080 fffff803`223ec340 ffffe000`949af040 : nt!ExpWorkerThread+0xe9
ffffd000`26570b00 fffff803`221663c6 : ffffd001`029ee180 ffffe000`949af040 ffffe000`98a1a800 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x58
ffffd000`26570b60 00000000`00000000 : ffffd000`26571000 ffffd000`2656a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

Diagnostics Test

HDD & SSD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Disk Check - Windows 7 Help Forums

stone616 · 08 Nov 2015

Update on this for people having similar issues. I swapped out my memory going from 4 x 4 sticks of DDR4 at 16 GBs to 2 x 8 sticks of DDR4 at 16 GBs and all my issues are completely gone. Over the last week I've had zero BSoD occurrences. It was either bad memory or the other two slots I'm not not using in the motherboard are bad. I'm leaning towards bad memory sticks. I'll move the RAM to the other slots in the next week just to make sure.