Are my BSOD's hardware related

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
D

Deleted member 1443762

Guest
17/04/2017 UPDATE: Small update if anyone finds this thread. No BSOD's since I reinstalled Windows 8.1 through the original CD and installed the drivers from the motherboard CD (later updating chipset and audio through MSI's site).

I reinstalled the RAM and GPU (just taking them out and putting back in), and swapped out the PSU for a brand new one. So far no issues. Not a definite fix but somehow did the job. Also to note: using Game Ready Driver: 378.92 - WHQL

-

Second time I've had to make a thread on this out of pure desperation.

After a clean install of 8.1 I am still encountering BSOD's. They usually happen during games/after exiting games.

Most recent one is Kmode exception not handled. wdf01000.sys
Previous ones have been System service exception, memory managment, page fault in nonpaged area. ntosknrl.exe

PC was fine for about 2 years. (I'm using the same hardware still)

What I have tried to fix the problem:

- chkdsk /f /r on all drives: Nothing found
- sfc /scannow: Nothing found
- Full system scan: No Threats found

- MemTest86: 7 Hours approx to complete: Nothing found
- Windows Memory Diagnostic: Nothing found

- Re-installing the RAM
- Re-installing the GPU

- Used DDU to remove Nvidia drivers and reinstalled the latest one: Still BSOD
- Used DDU to remove Nvidia drivers and reinstalled with the very first one: Still BSOD
- Used DDU to remove Nvidia drivers and reinstalled with a 2016 one: Still BSOD


If anyone know's anything or if this is hardware related please tell me. I have stress tested the GPU and nothing happens with that. However previous research told me that it could be a failing card. I don't mind buying a new one but would like to make sure first. Thanks
 
Solution
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)

its possible directions slightly different for Win 8, I couldn't find anything specific to it. If you upload those Paul may be able to find the actual problem for you
I installed the Intel software updater on my last install and it never ever finished updating so I just ignore it now. I don't know if I have current drivers for everything but as PC is working I don't worry. If boot speed got too slow I might go look again but I think i have latest for motherboard now.
 


I did that before, blue screened immediately and I was stuck in a loop. The BSOD code was something to do with Driver Verifier which was expected but it didn't show anything else apart from that. I got back through Safe Mode and just decided to re-install Windows. Unfortunately I forgot to check the Minidump folder, I was expecting the BSOD to say something specific instead.
 


This was when the BSOD happened. I think that ID is irrelevant?
 


Yea, isn't Event 41 just obvious because the system had to shut down because of a BSOD? We now know that DirectX or some other driver was the BSOD cause.
 


Yea I know. What I'm saying is that 41 happened seconds after the BSOD happened. Obviously 41 is expected after a BSOD?
 


Yeah exactly. Honestly I'm coming to an end now with this. Do you think a new GPU would fix these driver problems. I know it could be something else causing a conflict but surely this would be a good step to take to help eliminate the problem?
 


I'll be testing the card tomorrow on another system, if any issues occur I'll be hitting checkout. Thanks for all your help and Colif.
 
All event 41 (63) shows is windows ran a report at start up and found windows had not shut down correctly the previous times. This means windows doesn't know what cause was. Normally points at a hardware problem. If win 10 knew what cause was it would likely produce a BSOD. No BSOD, it doesn't know.