- Thread Author
- #1
Solution
This memory dump blames your networking driver - e1c62x64.sys It's a driver component of your Intel wired network card. Please:
- download a fresh copy of the driver package from Link Removed
- un-install the current drivers from your system
- install the freshly downloaded driver package and monitor for further BSOD's.
Also, the old Ghost drivers are still installed and working.
Please manually remove them this way:
- download a fresh copy of the driver package from Link Removed
- un-install the current drivers from your system
- install the freshly downloaded driver package and monitor for further BSOD's.
Also, the old Ghost drivers are still installed and working.
Please manually remove them this way:
To safely remove symsnap.sys and v2imount.sys
1. Create a System Repair Disc. Go to Start...All Programs...Maintenance...Create a System Repair Disc
2. Create a System Restore Point
3. Download and install Autoruns (free from here: Autoruns for Windows ). Search within Autoruns for anything that...
- Joined
- Mar 22, 2010
- Messages
- 3,046
Most likely due to Microsoft Virtual PC (who's drivers date from 2007) - un-install it (do not reinstall it, the older drivers are not compatible with Win7)
Could also be due to n outdated copy of Symantec/Norton Ghost or Backup. Un-install it immediately (it's drivers date from 2006 - before Win7 was a twinkle in Bill Gates' eye!)
GEARAspiWDM.sys also dates from 2006 (it most often belongs to iTunes). Please either update or un-install iTunes.
Please provide this info for a more complete analysis: Link Removed
Analysis:
The following is for information purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Could also be due to n outdated copy of Symantec/Norton Ghost or Backup. Un-install it immediately (it's drivers date from 2006 - before Win7 was a twinkle in Bill Gates' eye!)
GEARAspiWDM.sys also dates from 2006 (it most often belongs to iTunes). Please either update or un-install iTunes.
Please provide this info for a more complete analysis: Link Removed
Analysis:
The following is for information purposes only.
Code:
[FONT=lucida console]**************************Sun Sep 23 18:59:32.896 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\092312-12542-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 1:33:22.895[/B]
BugCheck Code: [B]BugCheck 9F, {3, fffffa8006768e30, fffff80000ba2748, fffffa800b689750}[/B]
*** WARNING: Unable to verify timestamp for VMNetSrv.sys
*** ERROR: Module load completed but symbols could not be loaded for VMNetSrv.sys
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]ntkrnlmp[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: [B]WmiPrvSE.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x9F_3_IMAGE_ntkrnlmp[/B]
CPUID: "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: [B]3410[/B]
BIOS Version 0906
BIOS Release Date 03/26/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[FONT=lucida console]**************************Sun Sep 23 18:59:32.896 2012 (UTC - 4:00)**************************
[B]GEARAspiWDM.sys Mon Aug 7 13:11:19 2006 (44D77437)[/B]
[B]symsnap.sys Fri Dec 15 19:25:20 2006 (45833CF0)[/B]
[B]v2imount.sys Mon Jan 15 12:03:19 2007 (45ABB3D7)[/B]
[B]VMNetSrv.sys Thu May 3 08:56:52 2007 (4639DC14)[/B]
[B]vmm.sys Tue Apr 7 09:25:54 2009 (49DB5462)[/B]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
ICCWDT.sys Wed Aug 18 04:27:45 2010 (4C6B9981)
AsIO.sys Mon Aug 23 21:53:02 2010 (4C7325FE)
vpcnfltr.sys Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys Sat Nov 20 06:35:31 2010 (4CE7B283)
vpchbus.sys Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcvmm.sys Sat Nov 20 06:35:48 2010 (4CE7B294)
e1c62x64.sys Wed Jul 20 12:37:53 2011 (4E270461)
ndisrd.sys Fri Aug 12 06:14:50 2011 (4E44FD1A)
ASUSFILTER.sys Tue Sep 20 11:46:33 2011 (4E78B559)
asmtxhci.sys Wed Nov 2 23:00:22 2011 (4EB203C6)
asmthub3.sys Wed Nov 2 23:00:32 2011 (4EB203D0)
HECIx64.sys Wed Nov 9 19:52:25 2011 (4EBB2049)
iaStor.sys Tue Nov 29 22:39:19 2011 (4ED5A567)
RTKVHD64.sys Tue Jan 3 05:51:09 2012 (4F02DD9D)
asahci64.sys Thu Jan 5 00:08:19 2012 (4F053043)
iusb3hub.sys Thu Jan 5 06:54:43 2012 (4F058F83)
iusb3xhc.sys Thu Jan 5 06:54:45 2012 (4F058F85)
iusb3hcs.sys Thu Jan 5 06:56:40 2012 (4F058FF8)
MpFilter.sys Fri Mar 9 06:05:26 2012 (4F59E3F6)
igdkmd64.sys Mon Mar 19 19:31:54 2012 (4F67C1EA)
VBoxNetFlt.sys Tue May 22 08:25:37 2012 (4FBB85C1)
VBoxDrv.sys Tue May 22 08:25:38 2012 (4FBB85C2)
VBoxUSBMon.sys Tue May 22 08:25:39 2012 (4FBB85C3)
VBoxNetAdp.sys Tue May 22 08:25:39 2012 (4FBB85C3)
[/FONT]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Last edited:
- Thread Author
- #3
Thanks Usama. That sounds plausible (I won't be able to do the uninstall for a few days as I'm away from home). I recall now that
I got some warnings when I installed Virtual PC and Norton Ghost from my old Vista machine but I went ahead and insalled them anyway so totally my fault.
I tried using the MS Win Debug utility to identify the bad drivers using the crash dump but I couldn't see useful data in the output
but to be honest I'm not too familar with this utility. How did you identify these drivers? It would be very useful to know for future reference. Thanks in advance!
Olefin
I got some warnings when I installed Virtual PC and Norton Ghost from my old Vista machine but I went ahead and insalled them anyway so totally my fault.
I tried using the MS Win Debug utility to identify the bad drivers using the crash dump but I couldn't see useful data in the output
but to be honest I'm not too familar with this utility. How did you identify these drivers? It would be very useful to know for future reference. Thanks in advance!
Olefin
- Joined
- Mar 22, 2010
- Messages
- 3,046
Well, it's a long story - and we cheat a bit.
The most important command in the debugger is "!analyze -v" - that gives a verbose output (and there's usually a link for it that you can click on in the debugger).
We run different commands through the command line debugger - but also use the other reports extensively.
Here's my latest description of how I do it: Link Removed
I use a program devised by jcgriff2 and then rewritten and improved by writhziden - it automates a lot of the work and screens out a lot of the data that we use. BUT, it still requires a lot of experience to become comfortable with it.
At the bottom of the above link you'll find links to earlier versions of my attempts to describe what I do.
The most important command in the debugger is "!analyze -v" - that gives a verbose output (and there's usually a link for it that you can click on in the debugger).
We run different commands through the command line debugger - but also use the other reports extensively.
Here's my latest description of how I do it: Link Removed
I use a program devised by jcgriff2 and then rewritten and improved by writhziden - it automates a lot of the work and screens out a lot of the data that we use. BUT, it still requires a lot of experience to become comfortable with it.
At the bottom of the above link you'll find links to earlier versions of my attempts to describe what I do.
- Thread Author
- #5
Hi usasma
I removed Norton Ghost and uninstalled the old Virtual PC s/w and replaced it with the new
version from the MS web site for Win 7 64 bit but I'm still getting the same BSOD.
I had a look at my drivers using DriverView and of those drivers which have a Created_Date
they are all 2009 or later so I'm not sure what could be causing he problem.
Any ideas? I've attached a system dump.
Olefin
I removed Norton Ghost and uninstalled the old Virtual PC s/w and replaced it with the new
version from the MS web site for Win 7 64 bit but I'm still getting the same BSOD.
I had a look at my drivers using DriverView and of those drivers which have a Created_Date
they are all 2009 or later so I'm not sure what could be causing he problem.
Any ideas? I've attached a system dump.
Olefin
Attachments
- Joined
- Mar 22, 2010
- Messages
- 3,046
This memory dump blames your networking driver - e1c62x64.sys It's a driver component of your Intel wired network card. Please:
- download a fresh copy of the driver package from Link Removed
- un-install the current drivers from your system
- install the freshly downloaded driver package and monitor for further BSOD's.
Also, the old Ghost drivers are still installed and working.
Please manually remove them this way:
Analysis:
The following is for information purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
- download a fresh copy of the driver package from Link Removed
- un-install the current drivers from your system
- install the freshly downloaded driver package and monitor for further BSOD's.
Also, the old Ghost drivers are still installed and working.
Please manually remove them this way:
To safely remove symsnap.sys and v2imount.sys
1. Create a System Repair Disc. Go to Start...All Programs...Maintenance...Create a System Repair Disc
2. Create a System Restore Point
3. Download and install Autoruns (free from here: Autoruns for Windows ). Search within Autoruns for anything that uses symsnap.sys or v2imount.sys (also search for Norton or Ghost). Disable them by removing the checkmark from the far left column.
4. Check in services.msc for any Norton/Norton Ghost/symsnap/v2imount services. Disable any that you may find.
5. Check Device Manager (to include the View...Show hidden devices menu) and see if there are any Norton/Norton Ghost/symsnap/v2imount entries. If so, disable them (later on you can un-install them).
6. Rename symsnap.sys to symsnap.BAD and v2imount.sys to v2imount.BAD (should be located in C:\Windows\System32\drivers folder)
7. Reboot
If the system won't boot, use the System Repair Disc (Command Prompt option) to re-rename symsnap.BAD to symsnap.sys and v2imount.BAD to v2imount.sys
Then use the System Repair Disc (System Restore option) to restore the system to the state it was in prior to attempting to remove the driver.
Good luck!
Analysis:
The following is for information purposes only.
Code:
[font=lucida console]**************************Sat Oct 6 18:58:43.005 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100612-12339-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 1:34:23.004[/B]
BugCheck Code: [B]BugCheck 9F, {3, fffffa8007660a10, fffff80004c373d8, fffffa8009c39b00}[/B]
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by :[B]pci.sys[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0x9F_3_e1c62x64_IMAGE_pci.sys[/B]
CPUID: "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: [B]3410[/B]
BIOS Version 0906
BIOS Release Date 03/26/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 6 18:58:43.005 2012 (UTC - 4:00)**************************
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Sat Oct 6 18:58:43.005 2012 (UTC - 4:00)**************************
[B]symsnap.sys Fri Dec 15 19:25:20 2006 (45833CF0)[/B]
[B]v2imount.sys Mon Jan 15 12:03:19 2007 (45ABB3D7)[/B]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
ICCWDT.sys Wed Aug 18 04:27:45 2010 (4C6B9981)
AsIO.sys Mon Aug 23 21:53:02 2010 (4C7325FE)
vpcnfltr.sys Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys Sat Nov 20 06:35:31 2010 (4CE7B283)
vpchbus.sys Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcvmm.sys Sat Nov 20 06:35:48 2010 (4CE7B294)
e1c62x64.sys Wed Jul 20 12:37:53 2011 (4E270461)
ndisrd.sys Fri Aug 12 06:14:50 2011 (4E44FD1A)
ASUSFILTER.sys Tue Sep 20 11:46:33 2011 (4E78B559)
asmtxhci.sys Wed Nov 2 23:00:22 2011 (4EB203C6)
asmthub3.sys Wed Nov 2 23:00:32 2011 (4EB203D0)
HECIx64.sys Wed Nov 9 19:52:25 2011 (4EBB2049)
iaStor.sys Tue Nov 29 22:39:19 2011 (4ED5A567)
RTKVHD64.sys Tue Jan 3 05:51:09 2012 (4F02DD9D)
asahci64.sys Thu Jan 5 00:08:19 2012 (4F053043)
iusb3hub.sys Thu Jan 5 06:54:43 2012 (4F058F83)
iusb3xhc.sys Thu Jan 5 06:54:45 2012 (4F058F85)
iusb3hcs.sys Thu Jan 5 06:56:40 2012 (4F058FF8)
igdkmd64.sys Mon Mar 19 19:31:54 2012 (4F67C1EA)
VBoxNetFlt.sys Tue May 22 08:25:37 2012 (4FBB85C1)
VBoxDrv.sys Tue May 22 08:25:38 2012 (4FBB85C2)
VBoxUSBMon.sys Tue May 22 08:25:39 2012 (4FBB85C3)
VBoxNetAdp.sys Tue May 22 08:25:39 2012 (4FBB85C3)
eudskacs.sys Fri Aug 3 11:34:10 2012 (501BEF72)
eubakup.sys Fri Aug 3 11:34:14 2012 (501BEF76)
EuFdDisk.sys Fri Aug 3 11:34:39 2012 (501BEF8F)
EUBKMON.sys Mon Aug 20 03:55:45 2012 (5031ED81)
MpFilter.sys Thu Aug 23 19:03:14 2012 (5036B6B2)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
- Thread Author
- #9
Hi usasma
I still get the Driver_Power_Failure BSOD on a fairly regular basis, I renamed the old drivers
as you suggested, ran autoruns and couldn't find any references to ghost, norton etc, simlarly in services.msc no refs found, updated the driver for the wired network card. I've attached the latest minidump. Thanks
Regards
Olefin
I still get the Driver_Power_Failure BSOD on a fairly regular basis, I renamed the old drivers
as you suggested, ran autoruns and couldn't find any references to ghost, norton etc, simlarly in services.msc no refs found, updated the driver for the wired network card. I've attached the latest minidump. Thanks
Regards
Olefin
Attachments
- Joined
- Mar 22, 2010
- Messages
- 3,046
Memory dump still blames your network driver.
The most likely issue is a broken network card (IME), but it can also be other programs using the network card improperly.
Trying a new card (and removing/disabling the old one) would be a good test. Replacement cards are handy to have, and they generally cost around $15 to $20 (US).
The vmm.sys driver is still present. Un-installing the VMWare software is advisable at this point. You can reinstall the latest, Win7 compatible version once you determine if it's to blame for the BSOD's (or not).
If neither of these fix the problem, then try running Driver Verifier according to these instructions: Link Removed
Analysis:
The following is for informational purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
The most likely issue is a broken network card (IME), but it can also be other programs using the network card improperly.
Trying a new card (and removing/disabling the old one) would be a good test. Replacement cards are handy to have, and they generally cost around $15 to $20 (US).
The vmm.sys driver is still present. Un-installing the VMWare software is advisable at this point. You can reinstall the latest, Win7 compatible version once you determine if it's to blame for the BSOD's (or not).
If neither of these fix the problem, then try running Driver Verifier according to these instructions: Link Removed
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Mon Mar 4 21:59:59.882 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030413-12916-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 1:33:36.882[/B]
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
Probably caused by :[B]pci.sys[/B]
BugCheck [B]9F, {3, fffffa8006e85a10, fffff80000b9c3d8, fffffa800b60a210}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006e85a10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800b60a210, The blocked IRP
BUGCHECK_STR: 0x9F
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x9F_3_e1c62x64_IMAGE_pci.sys[/B]
CPUID: "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: [B]3410[/B]
BIOS Version 0906
BIOS Release Date 03/26/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Mon Mar 4 21:59:59.882 2013 (UTC - 5:00)**************************
[B]vmm.sys Tue Apr 7 09:25:54 2009 (49DB5462)[/B]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
ICCWDT.sys Wed Aug 18 04:27:45 2010 (4C6B9981)
AsIO.sys Mon Aug 23 21:53:02 2010 (4C7325FE)
vpcnfltr.sys Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys Sat Nov 20 06:35:31 2010 (4CE7B283)
vpchbus.sys Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcvmm.sys Sat Nov 20 06:35:48 2010 (4CE7B294)
ndisrd.sys Fri Aug 12 06:14:50 2011 (4E44FD1A)
ASUSFILTER.sys Tue Sep 20 11:46:33 2011 (4E78B559)
asmtxhci.sys Wed Nov 2 23:00:22 2011 (4EB203C6)
asmthub3.sys Wed Nov 2 23:00:32 2011 (4EB203D0)
iaStor.sys Tue Nov 29 22:39:19 2011 (4ED5A567)
RTKVHD64.sys Tue Jan 3 05:51:09 2012 (4F02DD9D)
asahci64.sys Thu Jan 5 00:08:19 2012 (4F053043)
iusb3hub.sys Thu Jan 5 06:54:43 2012 (4F058F83)
iusb3xhc.sys Thu Jan 5 06:54:45 2012 (4F058F85)
iusb3hcs.sys Thu Jan 5 06:56:40 2012 (4F058FF8)
VBoxNetFlt.sys Tue May 22 08:25:37 2012 (4FBB85C1)
VBoxDrv.sys Tue May 22 08:25:38 2012 (4FBB85C2)
VBoxUSBMon.sys Tue May 22 08:25:39 2012 (4FBB85C3)
HECIx64.sys Mon Jul 2 18:14:58 2012 (4FF21D62)
eudskacs.sys Fri Aug 3 11:34:10 2012 (501BEF72)
eubakup.sys Fri Aug 3 11:34:14 2012 (501BEF76)
EuFdDisk.sys Fri Aug 3 11:34:39 2012 (501BEF8F)
e1c62x64.sys Fri Aug 10 18:44:15 2012 (50258EBF)
EUBKMON.sys Mon Aug 20 03:55:45 2012 (5031ED81)
MpFilter.sys Wed Oct 31 18:43:06 2012 (5091A97A)
igdkmd64.sys Wed Dec 12 19:42:26 2012 (50C92472)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
- Thread Author
- #11
Hi usasma
I believe the VMM.sys is for MS Windows Virtual PC (I downloaded the win 7 version after uninstalling virtual PC 2007). I occasionally get other BSOD's as well, this evening I got a SYSTEM_EXCEPTION (see attached minidump) and sometimes I get BAD_POOL_HEADER and memory excpetion BSOD's. Maybe it's a bad motherboard or perhaps it's a bad network card
as you suggested, it would be good to find out if the SYSTEM_EXCEPTION was caused by the samer driver. I have scanned for viruses, spyware, malware but nothing showed up.
Olefin
I believe the VMM.sys is for MS Windows Virtual PC (I downloaded the win 7 version after uninstalling virtual PC 2007). I occasionally get other BSOD's as well, this evening I got a SYSTEM_EXCEPTION (see attached minidump) and sometimes I get BAD_POOL_HEADER and memory excpetion BSOD's. Maybe it's a bad motherboard or perhaps it's a bad network card
as you suggested, it would be good to find out if the SYSTEM_EXCEPTION was caused by the samer driver. I have scanned for viruses, spyware, malware but nothing showed up.
Olefin
Attachments
- Joined
- Mar 22, 2010
- Messages
- 3,046
Nothing specific in this one - but the vmm.sys is still present.
Please uninstall the Win7 Virtual PC program to see if that helps. You can always reinstall it later on.
Analysis:
The following is for informational purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Please uninstall the Win7 Virtual PC program to see if that helps. You can always reinstall it later on.
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Tue Mar 5 21:11:21.487 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\030513-13930-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 1:07:17.487[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )[/B]
BugCheck [B]3B, {c0000005, fffff80002c71b45, fffff8800a2e4ac0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002c71b45, Address of the instruction which caused the bugcheck
Arg3: fffff8800a2e4ac0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: lsass.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0[/B]
CPUID: "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: [B]3410[/B]
BIOS Version 0906
BIOS Release Date 03/26/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Tue Mar 5 21:11:21.487 2013 (UTC - 5:00)**************************
[B]vmm.sys Tue Apr 7 09:25:54 2009 (49DB5462)[/B]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
ICCWDT.sys Wed Aug 18 04:27:45 2010 (4C6B9981)
AsIO.sys Mon Aug 23 21:53:02 2010 (4C7325FE)
vpcnfltr.sys Sat Nov 20 06:35:20 2010 (4CE7B278)
vpcusb.sys Sat Nov 20 06:35:31 2010 (4CE7B283)
vpchbus.sys Sat Nov 20 06:35:38 2010 (4CE7B28A)
vpcvmm.sys Sat Nov 20 06:35:48 2010 (4CE7B294)
ndisrd.sys Fri Aug 12 06:14:50 2011 (4E44FD1A)
ASUSFILTER.sys Tue Sep 20 11:46:33 2011 (4E78B559)
asmtxhci.sys Wed Nov 2 23:00:22 2011 (4EB203C6)
asmthub3.sys Wed Nov 2 23:00:32 2011 (4EB203D0)
iaStor.sys Tue Nov 29 22:39:19 2011 (4ED5A567)
RTKVHD64.sys Tue Jan 3 05:51:09 2012 (4F02DD9D)
asahci64.sys Thu Jan 5 00:08:19 2012 (4F053043)
iusb3hub.sys Thu Jan 5 06:54:43 2012 (4F058F83)
iusb3xhc.sys Thu Jan 5 06:54:45 2012 (4F058F85)
iusb3hcs.sys Thu Jan 5 06:56:40 2012 (4F058FF8)
VBoxNetFlt.sys Tue May 22 08:25:37 2012 (4FBB85C1)
VBoxDrv.sys Tue May 22 08:25:38 2012 (4FBB85C2)
VBoxUSBMon.sys Tue May 22 08:25:39 2012 (4FBB85C3)
HECIx64.sys Mon Jul 2 18:14:58 2012 (4FF21D62)
eudskacs.sys Fri Aug 3 11:34:10 2012 (501BEF72)
eubakup.sys Fri Aug 3 11:34:14 2012 (501BEF76)
EuFdDisk.sys Fri Aug 3 11:34:39 2012 (501BEF8F)
e1c62x64.sys Fri Aug 10 18:44:15 2012 (50258EBF)
EUBKMON.sys Mon Aug 20 03:55:45 2012 (5031ED81)
MpFilter.sys Wed Oct 31 18:43:06 2012 (5091A97A)
igdkmd64.sys Wed Dec 12 19:42:26 2012 (50C92472)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
- Thread Author
- #13
Hi usasma
Removing Virtual PC didn't make a difference but as you had pinpointed the network driver
I decided to have a look at the network adapter settings and noticed there was a setting for
Oracle Virtualbox (installed this ages ago to test Ubuntu Linux and had forgotten about it) so I unchecked it and I haven't had a BSOD for the last few days. Seems other folk have had rhe same issue with Virtualbox. So many thanks for your help in tracking this issue down!
Olefin
Removing Virtual PC didn't make a difference but as you had pinpointed the network driver
I decided to have a look at the network adapter settings and noticed there was a setting for
Oracle Virtualbox (installed this ages ago to test Ubuntu Linux and had forgotten about it) so I unchecked it and I haven't had a BSOD for the last few days. Seems other folk have had rhe same issue with Virtualbox. So many thanks for your help in tracking this issue down!
Olefin
Similar threads
- Article
- Replies
- 0
- Views
- 866
- Article
- Replies
- 0
- Views
- 1K
- Solved
- Replies
- 1
- Views
- 4K
- Replies
- 0
- Views
- 410
- Article
- Replies
- 0
- Views
- 742