bluescreen ntoskrnl.exe

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  • Hello everyone We want to personally apologize to everyone for the downtime that we've experienced. We are working to get everything back up as quickly as possible. Due to the issues we've had, your password will need to be reset. Please click the button that says "Forgot Your Password" and change it. We are working to have things back to normal. Emails are fixed and should now send properly. Thank you all for your patience. Thanks, PCHF Management
Status
Not open for further replies.

kanki

PCHF Member
Oct 25, 2016
34
1
27
so past week or two my windows task bar would randomly freeze up and i would have to do a hard reset (if i tried closing via windows it would take hours before it closed) but today for the first time in nearly two years i got a bsod.
specs:
i7 4790k
gtx 970
8gb 1600mhz ram
660w psu gold
msi z97m gaming motherboard
here is a copy of the minidump if anyone wants to help me out
 

Attachments

Hi there kanki and welcome to PCHF :)

I've moved your thread over to the Windows 10 BSOD section. I'll analyze your dump files shortly and let you know :)
 
Hi again,

I've analyzed your dump file, and nothing out of the ordinary pops out. Sometimes a BSOD will occur once and then never again. I see that this BSOD occured 2 weeks ago. Have you had any other BSODs?
 
Hi again,

I've analyzed your dump file, and nothing out of the ordinary pops out. Sometimes a BSOD will occur once and then never again. I see that this BSOD occured 2 weeks ago. Have you had any other BSODs?
erh no this bsod happend like 8 hours ago?, and i havent had a bsod since i reinstalled windows back in april 2015
 
Oops my bad. I misread your header lol.

Did you run through the BSOD prework? If not, please do so :)

There's no underlying cause or STOP code embedded in the file, so it's unknown what caused the crash. Couple questions for you:

1.) Did you add any new hardware recently?
2.) Did you install any new software just before it crashed?
 
Oops my bad. I misread your header lol.

Did you run through the BSOD prework? If not, please do so :)

There's no underlying cause or STOP code embedded in the file, so it's unknown what caused the crash. Couple questions for you:

1.) Did you add any new hardware recently?
2.) Did you install any new software just before it crashed?
changed from my 680 to a 970
no new software though
and here is the file doing what the thread youve made said.
 

Attachments

Sorry about the delay. Had a busy day today.

Further analysis reveals you received a DPC_WATCHDOG_VIOLATION BSOD. This occurs when the DPC period is exhausted, usually when a hardware Interrupt Request takes too long. Fortunately it doesn't indicate a problem with hardware or software as a stack trace didn't produce any outbound or inbound calls to the EBX register, which will push the offending driver to the top of the stack :)

You should be safe from further BSODs, as a DPC BSOD will usually occur only once and a reboot will fix it. :) If you experience further BSODs, please let us know :)
 
Sorry about the delay. Had a busy day today.

Further analysis reveals you received a DPC_WATCHDOG_VIOLATION BSOD. This occurs when the DPC period is exhausted, usually when a hardware Interrupt Request takes too long. Fortunately it doesn't indicate a problem with hardware or software as a stack trace didn't produce any outbound or inbound calls to the EBX register, which will push the offending driver to the top of the stack :)

You should be safe from further BSODs, as a DPC BSOD will usually occur only once and a reboot will fix it. :) If you experience further BSODs, please let us know :)
ah! ok glad to hear its nothing major, did reinstall windows tho as it hasnt been cleaned since 10 came out, only issue i occured with the clean windows is in chrome that gifs/videos are misscolored in the first few seconds and that typing in chrome is laggish
 
Are your graphics drivers up to date? Usually miscoloration indicates an out-of-date video driver.
hmm windows 10 installed the nvidia driver before i had the chance to but i did update it.should i download ddu and remove it? and reinstall?
 
Yes. :) Give it a whirl and reboot after doing so. Download a fresh driver from nvidia, run ddu, reboot, install the fresh driver, and reboot once more :) That should hopefully fix it

Sent from my SM-G935T using Tapatalk
 
Yes. :) Give it a whirl and reboot after doing so. Download a fresh driver from nvidia, run ddu, reboot, install the fresh driver, and reboot once more :) That should hopefully fix it

Sent from my SM-G935T using Tapatalk
did what you said, but gifs still do the black pixelated thing when i play them
 
used revouninstaller to remove chrome, but still happends, the edge browser is fine dunno why its happening with chrome
 
Download ResetBrowser To your desktop.

Right click and run as administrator.

vwUeyaZ.png


Click on Reset Chrome - Allow completion.



Now reboot your machine.
 
Download ResetBrowser To your desktop.

Right click and run as administrator.

vwUeyaZ.png


Click on Reset Chrome - Allow completion.



Now reboot your machine.
hey, found a workaound where i simply removed hardware accelaration (or something amongst those lines)
and it fixed it, i did post a thread on the chromes forums and seem others with the same browser version n gpu series900/1000 has same issues.
 
Yes. :) Give it a whirl and reboot after doing so. Download a fresh driver from nvidia, run ddu, reboot, install the fresh driver, and reboot once more :) That should hopefully fix it

Sent from my SM-G935T using Tapatalk
hey again :) the bsod seems to have been caused by a program
BugCheck 133, {1, 1e00, 0, 0}
*** WARNING: Unable to verify timestamp for EasyAntiCheat.sys
*** ERROR: Module load completed but symbols could not be loaded for EasyAntiCheat.sys

well thats according to a guy on the tenforums, but seems likely as i was playing rust which uses that program for anti cheating.
 
Status
Not open for further replies.