BSOD PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl.exe?

Tomahawk1 · Sep 30, 2015

I have been getting many BSOD crashes in the last few days (~16) mostly when the system is idle, but recently while in use also. I rolled back my nvidia driver and ran memtest with no errors. I don't know what to try next besides system restore. I don't understand the dump info (here's the bluescreenview of the last 2)

093015-17687-01.dmp 9/30/2015 3:34:06 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff803`3132e85a ffffd000`c66b64e8 ffffd000`c66b5cf0 ntoskrnl.exe ntoskrnl.exe+12685a x64 ntoskrnl.exe+12685a C:\Windows\Minidump\093015-17687-01.dmp 8 15 9600 389,488 9/30/2015 3:35:38 AM

093015-14156-01.dmp 9/30/2015 1:32:48 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff901`428944c0 00000000`00000000 fffff960`001bc6a7 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+14f9a0 x64 ntoskrnl.exe+14f9a0 C:\Windows\Minidump\093015-14156-01.dmp 8 15 9600 391,936 9/30/2015 1:34:39 AM

Any advise on what to do next?

Rumbletum · Sep 30, 2015

Check your HDD

neieus · Sep 30, 2015

Download who crashed and have it read the minidump information provided from the blue screen then post it here. That will give us more of an idea of what's going on. Looking at what you have provided already the ntoskrnl will only crash due to a device driver so with luck that dump data will tell you which driver caused the problem.

R4lNM4N · Sep 30, 2015

Failing PSU's will cause random BSOD's. The key here is the intermittent error. Don't suppose you have a spare PSU?

http://www.techrepublic.com/blog/10-things/10-tips-for-coping-with-blue-screen-errors/

Tomahawk1 · Sep 30, 2015

neieus :

Here is what whocrashed told me for the last few dumps, doesn't look like it knows which driver it is. Do you think I can rule out hardware?

On Wed 9/30/2015 10:34:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093015-17687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x12685A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8033132E85A, 0xFFFFD000C66B64E8, 0xFFFFD000C66B5CF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 9/30/2015 10:34:06 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8033132E85A, 0xFFFFD000C66B64E8, 0xFFFFD000C66B5CF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 9/30/2015 8:32:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093015-14156-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960001BC6A7)
Bugcheck code: 0x50 (0xFFFFF901428944C0, 0x0, 0xFFFFF960001BC6A7, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Tue 9/29/2015 8:02:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092915-13000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0x139 (0x3, 0xFFFFD001DA5EA820, 0xFFFFD001DA5EA778, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Tomahawk1 · Sep 30, 2015

R4lNM4N :

R4lNM4N · Sep 30, 2015

Tomahawk1 :

And you didn't take you eye off the tester for hours right? And would have totally saw if there was a spike or surge on any one of those connectors (which would cause a BSOD) right? And why test it under load when these seem to happen when idle?

Tomahawk1 · Sep 30, 2015

R4lNM4N :

Tomahawk1 :

And you didn't take you eye off the tester for hours right? And would have totally saw if there was a spike or surge on any one of those connectors (which would cause a BSOD) right? And why test it under load when these seem to happen when idle?

No I didn't I was just really hoping it wasn't the PSU. Now I have the problem of buying a cheaper psu to test it or just going ahead and buying a new $150 PSU and hoping that fixes it.

R4lNM4N · Sep 30, 2015

Tomahawk1 :

In that situation, I would go "borrow one" lol

You can get one from a BestBuy or Staples. Use it for a day or two and return it. If it does happen to be the PSU,...
A) It's probably easier to swap it out than digging through all those BSOD logs
B) You can get a high quality PSU for well under $150 (unless you need like 1200Watts or something)

Here's a calculator...http://coolermaster.outervision.com/ remember you want one a few hundred watts more than the minimum requirement

johnbl · Sep 30, 2015

first two bugcheck were cause by a bad memory address.
can not tell what caused the last few with the data provided.

My guess is you have memory problems or a driver that is corrupting kernel data in memory.
you can put the memory dumps on a server and post a link if you want someone to take a quick look.

run memtest86 and confirm your physical ram and BIOS RAM timings are ok.

last two bugchecks are common with memory problems, malware attacks and corruption of kernel data belonging to the respective drivers.
on windows 7 you could run cmd.exe as an admin and run
sfc.exe /scannow
(but most malware will have corrupted the hidden backup copies this command uses)
on window 8.x and above you can run
dism.exe /online /cleanup-image /restorehealth
and you have a good chance to fix corruption caused by malware. it gets the new copies of the corrupted windows files from the microsoft update server.

if you do find corrupt binaries, it is a good idea to try to figure out why they were corrupted.
IE run a malwarebytes scan, or if you just installed the OS, using a thumb drive or USB drive look for problems in the USB drivers. (error detection on USB is off by default so you can get lots of nice corrupted files and never know)

Tomahawk1 · Oct 1, 2015

johnbl :

https://drive.google.com/folderview?id=0B4EodB7yZa7AeVZreEExYUpFSk0&usp=sharing

Here's a link to the dumps. I did a memtest86x (v. 6.2) run twice and it came back with 0 errors (about 14 hrs each). I reseated the ram also. Just ran the dism.exe and nothing came up. will wait and see if it crashes again. My next step might be to replace the PSU, and see if that helps. All my scans show no malware. Thanks you your guys help!

R4lNM4N · Oct 1, 2015

Tomahawk1 :

johnbl :

https://drive.google.com/folderview?id=0B4EodB7yZa7AeVZreEExYUpFSk0&usp=sharing

Here's a link to the dumps. I did a memtest86x (v. 6.2) run twice and it came back with 0 errors (about 14 hrs each). I reseated the ram also. Just ran the dism.exe and nothing came up. will wait and see if it crashes again. My next step might be to replace the PSU, and see if that helps. All my scans show no malware. Thanks you your guys help!

Just another thought I have here...you said this started about 16 days ago. Can you see in your installed programs if anything was installed or updated since then? Have you recently updated any drivers? Also, check out Windows update history and see if any of the recent updates match that time frame as well. Also maybe look into system restore to see if your system has saved a potential restore point dating before these errors started.

johnbl · Oct 1, 2015

looking at the bugchecks, most current first.

first one: bad memory address passed to kernel

remove both overclocking drivers:
C:\Program Files (x86)\Intel\Extreme Tuning Utility\Drivers\IocDriver\64bit\iocbios2.sys Tue Jun 17 23:48:56 2014
C:\Program Files (x86)\AVG\AVG PC TuneUp\TuneUpUtilitiesDriver64.sys Mon May 11 04:07:27 2015

Tomahawk1 · Oct 2, 2015

R4lNM4N :

Tomahawk1 :

Just another thought I have here...you said this started about 16 days ago. Can you see in your installed programs if anything was installed or updated since then? Have you recently updated any drivers? Also, check out Windows update history and see if any of the recent updates match that time frame as well. Also maybe look into system restore to see if your system has saved a potential restore point dating before these errors started.

I had to go pretty far back, but this did the trick. This was my last resort as I had to go back about 6 months as that was the only restore point that I didn't have before the problem cropped up. Unfortunately I was never able to determine what driver it was, so I have to slowly reinstall various things until it crops up again. Thanks everyone!

Tomahawk1 · Oct 2, 2015

johnbl :

These two drivers are still there after the restore, and the system seems to run fine. Do you think I should remove the programs to be safe?

R4lNM4N · Oct 2, 2015

Tomahawk1 :

Well the first one looks like an overclocking utility, have you been using it to overclock your system? The other one looks like some sort of driver updater (junkware) from AVG. If you use that AVG thing to update your drivers, I'm thinking it installed a bad driver version for one of your hardware components. It;s a general recommendation that you get your drivers from Windows update or the hardware manufacturer directly (preferably the later.)

R4lNM4N · Oct 2, 2015

johnbl :

Nice job, I want to learn how to do that

BSOD PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl.exe?

Reputable

Distinguished

Distinguished

Distinguished

Reputable

Reputable

Distinguished

Reputable

Distinguished

Polypheme

Reputable

Distinguished

Polypheme

Reputable

Reputable

Distinguished

Distinguished

Share this page