BSOD with blame on ntoskrnl.exe and ntkrnlmp.exe

Ray2003 · 28 Aug 2014

Hi, I've been a longtime viewer (client?) of this site, and you guys have done a fantastic job fixing some of my issues in the past and I was wondering if you can help me again. My computer crashed today, and when I ran my WhoCrashed software, the following popped up:

On Thu 8/28/2014 1:42:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082814-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8801867EF68, 0x1, 0xFFFFF800037CA474, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Thu 8/28/2014 1:42:22 PM 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: 0x50 (0xFFFFF8801867EF68, 0x1, 0xFFFFF800037CA474, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

In the last BSOD, it was deemed my Nvidia drivers needed updating so I downloaded the Nvidia GeForce Experience, which currently states my drivers are up to date. The past process could be seen here: BSOD while watching video (not porn!).

Anyways, I've uploaded my memory dump files here: https://onedrive.live.com/?cid=9183E...F542F4D665!119

Hope you guys can help out! I sincerely appreciate it!

Arc · 02 Sep 2014

Ray2003 said:

Anyways, I've uploaded my memory dump files here: https://onedrive.live.com/?cid=9183E...F542F4D665!119

We need minidumps and other necessary files.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Ray2003 · 17 Sep 2014

Okay, I've attached the minidump files along with my memory dump files here.

https://onedrive.live.com/?cid=9183E...F542F4D665!119

Hope someone can help!

Arc · 17 Sep 2014

Blue Screen of Death (BSOD) Posting Instructions.

Ray2003 · 18 Sep 2014

OK, I've done all the steps with the SF Diagnostics tool. Lately, my computer's monitor has actually gone black even though my computer is still on (and it's not because a cable got unplugged) and once the computer restarted (with no minidump file created; this happened 2 days ago) and another time, it completely froze (also about 2 days ago). Anyways, I hope you can help, and I apologize for not following instructions earlier!

Arc · 19 Sep 2014

Remove it from startup.

Code:

Install LastPass FF RunOnce    c:\progra~2\common~1\lpunin~1.exe -q -name=lastpass -ffuuid support@lastpass.com    Public    Common Startup

And then enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

______________________________________________________

Code:

BugCheck 50, {fffff8801867ef68, 1, fffff800037ca474, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PspGetSetContextInternal+30c )

Followup: MachineOwner
---------

Ray2003 · 22 Sep 2014

Hi, I've removed the Install LastPass startup and then ran the Driver Verifier according to instructions. When it restarted, the computer wouldn't even restart till it fixed itself. Then it was. I ran WhoCrashed and saw something else on the log so I ran Drive Verifier (since SF Diagnostic kept on crashing itself now!) and zipped the resulting file that popped up on the desktop. I hope I did everything right.

Ray2003 · 27 Sep 2014

Hello, is anyone there who can help? I'd sincerely appreciate it.

Arc · 27 Sep 2014

Ray2003 said:

Hello, is anyone there who can help? I'd sincerely appreciate it.

Code:

BugCheck C9, {228, fffff88001187f74, fffff980030f0d80, 0}

*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+2f74 )

Followup: MachineOwner
---------

iaStor is Intel Rapid Storage, disc controller driver. Can be used in two different modes. The procedure to deal with it is totally different for every mode.

PxHlpa64 can come from a lot of programs including Roxio and many others.

To determine the proper procedure to deal with the issue, we need to know some more details, we need to see some more files.

But the upload does not contain the msinfo32.nfo file there. The systeminfo.txt file is blanked out, too.

Saying it again, mate ..... if you are reluctant to supply the data, we cannot assist you. And that is why I did not respond earlier ..... I asked for the data many a times, but you are not supplying them, I dont know why.

Ray2003 · 27 Sep 2014

"I asked for the data many a times, but you are not supplying them, I dont know why."

It's because the procedures for uploading (the Blue Screen of Death (BSOD) Posting Instructions) aren't working for me. Sf Diagnostic crashes every time I run it (I've downloaded it a few times already and have included a screenshot), and DM Log Collector clearly doesn't collect the necessary info. In fact, DM Log Collector doesn't do what it says it should (download a zipped file onto my desktop). It doesn't do this on my computer. It doesn't even show the file. You have to stop the program in order for the file to not disappear.

If you have any other way to collect the info, please let me know. But Options 1 and 2 no the Blue Screen posting instructions are problematic--at least on my computer. I'll try to run it again.