|27 Oct 2016||#1|
BSOD while doing nothing in particular
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 Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7601
Service Pack: 1_0
Files that help describe the problem:
Read our privacy statement online:
Windows 7 Privacy Statement
If the online privacy statement is not available, please read our privacy statement offline:
|My System Specs|
|30 Oct 2016||#5|
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.
|My System Specs|
|29 Nov 2016||#7|
Out of curiosity, do you also know why ntoskrnl.exe is not the cause?
Please run following tests
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums
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.
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.
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.
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.
|My System Specs|
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 21:59.