Solved BSOD while doing nothing in particular

[ba12348]

Update, see post 6
I recently (last week) upgraded my hardware, since then I've been getting occasional blue screens. I put in a new mobo, new CPU, and new graphics card, but I did NOT change the psu (I've actually got a new one that I intend to install tomorrow), memory, or storage drives*. Since I did this upgrade I've been getting BSODs occasionally, with no particular action causing it, the last one happened while watching youtube, and I've put the computer through several games and one Hitman Absolution graphics benchmark that I ran for about 30 mins. After the first crash I did some searching that resulted in me opening the case back up, re-checking all cables and re-seating the graphics card. I thought I had it fixed as I went 4 days without a problem (after 3 crashes in 2 days), then, crunch. Graphics drivers are up to date, mobo drivers are updated a-la the included disk, the only thing that has NOT been done is run a startup repair with the windows disk because for reasons I've yet to determine the drive does not show up as bootable...

*I actually have 2 2TB HDDs, one of which is not connected, but the only thing on it is a backup of the other HDD.

Information that comes up after the restart:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFF88021ADF3BE
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88001499219
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102716-36941-01.dmp
C:\Users\ba12348\AppData\Local\Temp\WER-37268-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[ba12348]

Update: new 750 watt PSU installed, memory re-seated, CPU cooler re-seated w/ new thermal paste (it had to be moved anyway, Noctua coolers are massive), all SATA and power cables re-seated, backup drive connected.

Will update this post again if the BSOD happens again.

 

[aodonnell311]

So, any success with the BSOD errors? Sounds like we are having similar problems, and I have also recently installed a Noctua air cooler...

I'd be interested to know if that solved your problem...

CHeers!

-A

 

[axe0]

Hi ba12348,

Welcome to the 7forums and apologies for the delay.

Are you still in need of help?

 

[ba12348]

I have not seen anything since I posted that last message, but keep in mind it's only been two days and the last BSOD was 4 days in the making. I strongly suspect the power supply was at fault, my old one was a 550 watt and that just seems slightly anemic for a GTX 1080. I'm tentatively calling it solved but will update this post if it happens again.

 

[ba12348]

I thought they were gone, I was wrong. BlueScreenView blames NTOSKRNL.exe for the crashes, but from my research I know that's probably not the cause.

 

[axe0]

Good research
Out of curiosity, do you also know why ntoskrnl.exe is not the cause?


Please run following tests

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 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.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[ba12348]

Thanks, I'll be going to work in a couple hours so I'll start the memory test then. From what I found it gets blamed for the crash because it finds something unexpected in memory that it thought it had reserved, and crashes the computer to prevent damage.

 

[axe0]

The ntoskrnl.exe gets blamed because it is the last active (basically saying), but it doesn't crash the system nor does it do such things with the memory (AFAIK).

 

[ba12348]

Memtest completed 3 passes with 0 errors, I'll find time to do the whole test later but I need the computer to finish up some schoolwork. Verifier has been started.
FYI 32gb of ram is entirely too much if you ever want to check it for errors.

 

[axe0]

FYI 32gb of ram is entirely too much if you ever want to check it for errors.

We're aware of that, 8GB takes about a single night to finish (8-10h). 16GB could take up to 1 or 2 days, 32GB takes at least a few days.

 

[ba12348]

Good(ish) news, I've managed to produce another BSOD. Rather interestingly it did NOT produce a dump file despite saying it was. I was sitting there when it happened and the check string was "driver IRQL not less or equal" New log collection file attached, not that I think it's any different from the last.

 

[axe0]

Please remove some files to increase the free space to at least 10-15%.
Every partition needs at least 10-15% free space so Windows can do its thing in the background.

   Warning

Less free space could cause BSOD's

 

[ba12348]

You mean on the C: drive? I've been kicking myself for doing that ever since I built this computer, next one will be a full size SSD, who knows maybe by then they won't cost your first born child. I'll clean it up when I get home tonight and report back if there are more issues.

 

[ba12348]

Solution found: Old network driver. My particular motherboard requires a 3rd party network driver, without it installed there is no connection at all. So, I installed the driver that came on the disk with the board. After it crashed yet again I dug a little deeper and found that netio.exe was causing the BSOD, according to the dump file. Updating to the most recent network driver, from Gigabyte's website, seems to have fixed the issue. Thank you for your help Axe!