Ask a new question

BSOD caused about once every two days by NTOSKRNL.EXE

Every once in a while, when I am doing basically anything such as browsing the web or playing a game or even leaving the computer idle, my computer will slow down for a sec, a blue screen will quickly flash on the screen, and then return to the screen it was on before the BSOD. However, the computer would then be frozen and the CPU usage goes up drastically for some reason (I can tell by the CPU fans spinning up fast almost immediately) until I force shut the computer down. Because the blue screen never stayed on long enough to read, I decided to install an app called Blue Screen View to read the minidumps created by them. A picture of the results is in the attachment below, but basically, all of the blue screens had the string PAGE_FAULT_IN_NONPAGED_AREA with the cause of each of them all leading to NTOSKRNL.EXE. How do I fix this?

Please zip up the dump files and share them via OneDrive so that I can have a look at them. Many thanks.
Phil C

One good turn deserves another!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Sure thing, here you go!

https://1drv.ms/u/s!AvrNmF43ayMvhEfThTR0tPQtDmiF?e=VvulLA

Let me know if that works.

-Raffi

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello again,

I have processed all your dumps.  The broad overview is that most are caused by the the graphics driver.  The two different codes are clock watchdog timeouts but these really need the full kernel dump (memory.dmp) for analysis and these will be long gone now as they get overwritten each time.

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Thu Nov 12 04:08:15.028 2020 (UTC + 0:00)

System Uptime: 26 days 16:23:39.621

BugCheck 50, {fffff88019350708, 1, fffff880110e3340, 2}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Probably caused by: nvlddmkm.sys ( nvlddmkm+d6340 )

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Fri Oct 16 11:43:14.453 2020 (UTC + 0:00)

System Uptime: 15 days 20:22:40.972

BugCheck 50, {fffff8807ef30f78, 1, fffff8801118e340, 5}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Probably caused by: nvlddmkm.sys ( nvlddmkm+d6340 )

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Sat Sep 12 07:17:03.470 2020 (UTC + 0:00)

System Uptime: 1 days 11:51:01.813

BugCheck 50, {fffff88027ba0000, 1, fffff880111ca340, 2}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Probably caused by: nvlddmkm.sys ( nvlddmkm+d6340 )

BUGCHECK_STR:  0x50

PROCESS_NAME:  WizardGraphica

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Tue Aug  4 03:47:21.338 2020 (UTC + 0:00)

System Uptime: 2 days 21:58:16.167

BugCheck 50, {fffff88006394578, 1, fffff8801112b340, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Probably caused by: nvlddmkm.sys ( nvlddmkm+d6340 )

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Fri Jul 24 07:32:04.426 2020 (UTC + 0:00)

System Uptime: 41 days 12:08:11.723

BugCheck 101, {31, 0, fffff880009e7180, 1}

Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c8e )

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

PROCESS_NAME:  mDNSResponder.

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Fri Jun 12 19:17:54.339 2020 (UTC + 0:00)

System Uptime: 1 days 2:10:06.055

BugCheck 101, {31, 0, fffff88002fde180, 3}

Probably caused by: ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c8e )

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT

PROCESS_NAME:  System

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Sun May 31 20:40:27.539 2020 (UTC + 0:00)

System Uptime: 10 days 0:20:38.980

BugCheck 50, {fffff88024000000, 1, fffff880111c0340, 2}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Probably caused by: nvlddmkm.sys ( nvlddmkm+d6340 )

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Sat May 16 20:38:49.336 2020 (UTC + 0:00)

System Uptime: 0 days 0:14:44.663

BugCheck 50, {fffff88027330ee8, 1, fffff88011104340, 2}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Probably caused by: nvlddmkm.sys ( nvlddmkm+d6340 )

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Sat May 16 20:22:14.967 2020 (UTC + 0:00)

System Uptime: 9 days 21:30:11.114

BugCheck 50, {fffff8806f4e0ee8, 1, fffff88011104340, 5}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Probably caused by: nvlddmkm.sys ( nvlddmkm+d6340 )

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Built by: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707

Debug session time: Wed May  6 22:51:21.383 2020 (UTC + 0:00)

System Uptime: 5 days 19:37:08.659

BugCheck 50, {fffff880670b0ee8, 1, fffff880110f3340, 5}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Probably caused by: nvlddmkm.sys ( nvlddmkm+d6340 )

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

According to these dump files you are only getting them about once a month since June after a more frequent spike in May.  

I would suggest that you roll back your graphics driver to an earlier one.  You can do this from within Device Manager.

https://www.guidingtech.com/9834/how-to-roll-back-drivers-in-windows-7/

Phil C

One good turn deserves another!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated May 18, 2021 Views 193 Applies to: