random BSOD

sneyepr · 12 Feb 2010

please help! 3 or 4 times a day getting BSOD. could be reading E-mail or doing nothing.
On Fri 2/12/2010 1:09:58 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80002EA1798)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Dump file: C:\Windows\Minidump\021210-24351-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

memory and drivers all seem ok? mini dump attached. thanks

**Pauly** · 12 Feb 2010

Only one dmp file there please post a few more for cross reference say last 5 or 10

Dump contains error 0x7F check here for info BSOD Index

I would run a ram check Memtest86+ - Advanced Memory Diagnostic Tool and a HDD check HD Diagnostic and a system file scan
start>cmd.exe>right click run as admin>type sfc /scannow

Other things can be bios or AV look into these if necessary, try these options and post back your results

You also have some old drivers on your system i would look into updating these

DRHARD64.sys 01/12/2005 09:39:47
hpdskflt.sys 18/03/2008 21:25:31
Accelerometer.sys 18/03/2008 21:25:31
SynTP.sys 24/07/2008 23:10:28
enecir.sys 04/09/2008 09:47:58
000.fcl 26/09/2008 13:11:22
jmcr.sys 20/10/2008 09:31:04
agrsm64.sys 21/11/2008 22:05:20

Hope this helps

sneyepr · 12 Feb 2010

sfc /scannow was negative. caught in continual BSOD's here is a zip of the latest mini dumps.

mw2player · 12 Feb 2010

Stop 7F, 0x00000008 (double-fault) error occurs because of a single-bit error in the ESP register

If you scroll down to more infomation, 3, thats what i got when i run the debugger on the newest dump file you provided. Except for arg 2,3,4 had diffrent numbers and letters, but i think thats just an example.

"This problem occurs if one or more of the processors in the computer:
Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
Are damaged or defective.
Are operating outside their specified ranges for temperature, power, or other conditions."

I dont know, im not to expeirnced but that is what i have found, i dont think you should trust what i say since im beginner, but i would like to compare my findings to someone more expeirnced.

**Capt.Jack Sparrow** · 12 Feb 2010

sneyepr said:

sfc /scannow was negative. caught in continual BSOD's here is a zip of the latest mini dumps.

Hello,

Did you run the Memtest and HD Diaganostic that Pauly suggested ?? How did it turn up ?

- Captain

sneyepr · 12 Feb 2010

burned memtest iso to cd. caused two bsod's. how do i run the test? can't seem to boot computer from the cd? what am i doing wrong? the windows 7 memory test says memory is ok. hate to reformat and reinstall only to find out its a hardware problem. thanks for any help. here is the newest minidump

usasma · 13 Feb 2010

On HP's you tap "Esc" as the HP logo appears
That will get you to the Selection menu.
On newer HP's you'll then press "F9" to access the boot device selection menu

Alternatively, you can access the BIOS and set the CD/DVD drive as the first in the boot sequence.

sneyepr · 13 Feb 2010

memory and hard drive are ok. bsod can happen with nothing running. any other ideas?

usasma · 13 Feb 2010

All are STOP 0x7F errors (more info on "Usual Causes" and "Resolving the problem" here: BSOD Index)
All blame ntkrnlmp.exe - the kernel (core) of the operating system. This is probably wrong as corruption of the kernel will cause a lot of other problems other than an occasional BSOD. So, we look elsewhere....

So, please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

Code:

000.fcl      Fri Sep 26 09:11:22 2008 - CyberLink FCL Driver - http://www.carrona.org/dvrref.html#0
Accelerometer.sys Tue Mar 18 17:25:31 2008 - HP Mobile Data Protection System Accelerometer - http://www.carrona.org/dvrref.html#a
agrsm64.sys  Fri Nov 21 17:05:20 2008 - Agere Systems Soft Modem - http://www.carrona.org/dvrref.html#a
DRHARD64.sys Thu Dec 01 04:39:47 2005 - Dr.  Hardware System Info - http://www.carrona.org/dvrref.html#d
enecir.sys   Thu Sep 04 05:47:58 2008 - ENE Consumer IR Driver for eHome - http://www.carrona.org/dvrref.html#e
hpdskflt.sys Tue Mar 18 17:25:31 2008 - HP Mobile Data Protection System Disk Filter - http://www.carrona.org/dvrref.html#h
jmcr.sys     Mon Oct 20 05:31:04 2008 - JMicron JMB38X Memory Card Reader Driver - http://www.carrona.org/dvrref.html#j
SynTP.sys    Thu Jul 24 19:10:28 2008 - Synaptic Touch Pad Driver - http://www.carrona.org/dvrref.html#s

If you continue to get BSOD's after updating the above drivers (as was also recommended by Pauly in Post #2), please run Driver Verifier according to these directions. I'm unsure if it will help, but it can't hurt in these circumstances.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 13:38:27.900 2010 (GMT-5)
System Uptime: 0 days 0:29:28.851
BugCheck 7F, {8, 80050033, 406f8, fffff80002e957a0}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 16:06:42.595 2010 (GMT-5)
System Uptime: 0 days 0:17:17.936
BugCheck 7F, {8, 80050033, 406f8, fffff80002e4b798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 13:44:28.385 2010 (GMT-5)
System Uptime: 0 days 0:05:25.710
BugCheck 7F, {8, 80050033, 406f8, fffff80002e8d798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 13:08:25.931 2010 (GMT-5)
System Uptime: 0 days 0:41:16.272
BugCheck 7F, {8, 80050033, 406f8, fffff80002e4f7a0}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 15:13:22.029 2010 (GMT-5)
System Uptime: 0 days 1:27:51.979
BugCheck 7F, {8, 80050033, 406f8, fffff80002e85798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 15:19:23.416 2010 (GMT-5)
System Uptime: 0 days 0:05:22.367
BugCheck 7F, {8, 80050033, 406f8, fffff80002e41798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 15:48:42.841 2010 (GMT-5)
System Uptime: 0 days 0:22:33.182
BugCheck 7F, {8, 80050033, 406f8, fffff80002e8a798}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Feb 12 15:25:21.677 2010 (GMT-5)
System Uptime: 0 days 0:02:10.628
BugCheck 7F, {8, 80050033, 406f8, fffff80002e9d7a0}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Nero.exe

sneyepr · 14 Feb 2010

thanks for all your help! so far, no bsod. i think the major problem was the Synaptic Touch Pad Driver needed to be updated. i could not find updates for the following:

000.fcl i have version 1.4.0.2126
Accelerometer.sys i have version 3.10.1.6
agrsm64.sys i have version 2.1.92
hpdskflt.sys i have version 3.10.1.6

was surprised how unhelpful the hp website is for updating drivers. any ideas where i can get these updates without lots of jumping through hoops!!?? thanks again for the help.