Are my BSOD's hardware related

[Deleted member 1443762]

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

 

[Colif]

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.

 

[Paul NZ]

Same here the only things I install (and WU can install) are the video drivers, the wireless USB adapter.

I dont worry about the sound or LAN (dont use LAN anyway, I use wireless). Through device manager

 

[Deleted member 1443762]

Before buying new hardware, I would make sure PC isn't suffering from another drivers errors instead

You can try running driver verifer just read the instructions carefully. It is part of windows designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run Who crashed and see what driver it reveals

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.

 

[Deleted member 1443762]

Any info on these?
Pic 1 https://mega.nz/#!3xJ00LhY!80L5IqN5NqistAsZ_rE0Cby0CGSQeVhS4i5L0ExRhCQ
Pic 2 https://mega.nz/#!LpomXB5Q!r4oaXPsqNlcdiDDaH0pjz00Gaf4vHn5cxDJVeuoQyQs

The first one is to do with Nvidia kernel mode driver.

 

[Paul NZ]

But is it crashing?

 

[Deleted member 1443762]

But is it crashing?

No, this is just bringing up what happened around the time of BSOD^.

 

[Paul NZ]

The 2nd pic if you didnt press the on/off button to turn it off, can mean a faulty PSU

 

[Deleted member 1443762]

The 2nd pic if you didnt press the on/off button to turn it off, can mean a faulty PSU

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

 

[Paul NZ]

The 41(63) error may / will restart the computer it wont crash it. And wont log a stop error crash in event viewer

 

[Deleted member 1443762]

The 41(63) error may / will restart the computer it wont crash it. And wont log a stop error crash in event viewer

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.

 

[Paul NZ]

Error 41 isnt a BSOD/crash. Its a restart of the system. Which can happen if the PSU is faulty

It's similar to a BSOD but it isnt a BSOD/crash

 

[Deleted member 1443762]

Error 41 isnt a BSOD/crash. Its a restart of the system. Which can happen if the PSU is faulty

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

 

[Paul NZ]

Possible since it restarts when it crashes

 

[Deleted member 1443762]

Possible since it restarts when it crashes

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?

 

[Paul NZ]

Either replace / RMA the card or get the driver for the videocard off the site (ASUS. Gigabyte, whatever the brand of the card is). Not from Nvidia or AMD.

 

[Deleted member 1443762]

Either replace / RMA the card or get the driver for the videocard off the site (ASUS. Gigabyte, whatever the brand of the card is). Not from Nvidia or AMD.

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.

 

[Paul NZ]

No probs

 

[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.