BSOD out of nowhere (no changes to system and hardware)

Toggle sidebar Toggle sidebar
D

daniel222

Reputable
Jul 11, 2016
22
0
4,510
Hello,
So the story goes as follows... The PC is all fine and dandy, nothing unusuall, and then all of a sudden, whilst playing R6:S, I get a complete freeze and moments later, the infamous BSOD. The error code is DPC_WATCHDOG_VIOLATION and after running the WhoCrashed analysis I find out that the cause might have been the "ntoskrnl.exe" and "hal.dll"

Now I have no idea what those two do and I do realise that those are system related and a simple system restart (since I have seperate drives for my windows and games) would do just fine. But I do not wish to do this simply because I hate how that resets all the settings etc. So I'm willing to do that as a last resort.

Also the system did not restart by itself... (after the diagnostic data was collected on the bluescreen I mean) I had to turn it off by holding the power button. By simply pressing it again I gain nothing but a working gpu, fans, cooler, etc., red led light on the motherboard and no display. I turn the PC off, and turning it on again does the same. I'm only able to get it running after turning off the PSU with the switch and pressing the power button (to discharge the system).

You are my last hope as any other forum I wisited didnt help. I already checked the chipset drivers and gpu drivers are up to date aswell.

I trust in tomshardware proffesionals since they have helped me out before, sorry for the long post, and thanks in advance!
 
Sort by date Sort by votes


Okay so here goes...

https://mega.nz/#!0exRjBwQ!360XrXJ04O7xYB23HM7gl2Xk2vekxGUxpovBheRiu0I <--- thats the zip folder from the diagnostics...

This is the first time that I ever had any problems with this build. It's running smoothly for a year now.

Also do you need me to do all of the other steps in the link? Such as driver verifyer and ram tester and HDD diagnostics??

thnx








 
Upvote 0 Downvote


Sooo as I understand it, the fact that the system did not self restart after the BSOD, meant that the data that it gathered was corrupted? Also I would like to know if you have any idea as to why was my system not booting properly after the BSOD. The red LED light on the motherboard I mean.

I ckecked both drives and it's all fine.

The HDTunePro tests are green all the way. Or do you actually need the screenshots of the benchmarks and other tests?

The SeaTools did not spot anything either (I did all the available tests on both drives)

As to the RAM test, I won't be able to do that now, it is quite late where I live, I will most definetely do that tomorrow.

thnx again



 
Upvote 0 Downvote
Or that the location where the memory is temporary saved is bad. Either way, or any other possible reason why this happened, it's not good.

Boot issues can happen for various reasons, possible reason is RAM simply is bad or that something with a drive is bad that software cannot detect.

I need the results of the benchmark and SMART.

You could run the test overnight.
 
Upvote 0 Downvote


Okay, just so that I'm doing everything correctly, do I leave all the test and bencmark settings on default (in HDTunePro)?

 
Upvote 0 Downvote


Well I have the free trial anyway. : )


https://mega.nz/#!QHQjUSAK!MqnV3w_iUp1dSVEDJNhCJJchW5L1hXPSpPE31q5QuDw <----- So here is the SMART

https://mega.nz/#!xCwDRK5B!ndr0XBPPFI4b7YGDF4oaRSVvFRD1YrazvIre_vpt_lc <----- And here is the benchmark

https://mega.nz/#!5KQkABZZ!GC2KrO68reVef680Y5Vxc1ZYe6OAYQgHf697cOGBBLg <----- Extra tests

https://mega.nz/#!lb4Twa5L!K62cVq19Umg7S1nHm0VJLv9M9fJN71QEPxalxOJ7dWU <------ Random Access


When attempting to run the file benchmark it says "I/O error" and aborts the test.
 
Upvote 0 Downvote
No, there are other programs we could use in case needed :)

Could you upload the chkdsk log, to create the log run following command in powershell.
get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

Chkdsk should always report that it ran fine, because that means it fixed things.
 
Upvote 0 Downvote


When I ran the chkdsk in command prompt, it told me to restart, closed everything, did that all fine, and then as if nothing happened, boots up, no message, nothing. Is that how its supposed to be?

So I copy the command in there, press enter, and then what? Run the chkdsk again?

sorry if I sound nooby : P
thnx
 
Upvote 0 Downvote


Hmm so whats left to do then?

I guess I'll do the RAM test. And post an update tomorrow.

thnx for your time. : )
 
Upvote 0 Downvote


Maybe I'm an idiot, but I can't seem to boot from the USB drive to get the ram test going.
I install the memtest software for usb's all fine, load up bios to put the usb hard disk as first priority, in fact I remove my SSD as an option completely. But all it does is just enter the bios again, because it can't seem to read the USB drive.

Am I doing something wrong??
 
Upvote 0 Downvote


Yea, that's the problem, in the boot options, it only has my SSD.

And fast boot was already disabled.
 
Upvote 0 Downvote


Yeye, the fast startup, the msi fast boot, and the standart fast boot are all turned off.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom