Windows 7 Again on BSOD when waking up from sleep and sleep-hybernate enabled

Blutarsky

Extraordinary Member
Good morning people,
I'm experiencing lately this problem: when turning on the computer from sleep, a BSOD will occur, not with the same error code.
I have performed a memory test with Microsoft diagnostics tool but no error was issued.
The computer is a Dell Vostro 1500, originally shipped with Vista 32 Ultimate, upgraded to Windows 7 Ultimate 32.
I have attached the minidumps.
I hope someone can help!

Little sysinfo, possible to attach more if needed.

Code:
[B]System Vendor[/B]
ManufacturerDell Inc.Serial Number94QB23JModel 

[B]BIOS Information[/B]
VendorDell Inc.VersionA05Board Product ID0WY040
[B]Processor Information[/B]
Summary1 Physical Processors / 2 Cores / 2 Logical Processors / 64 bitsNameIntel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHzVendorGenuineIntelOriginal System Clock200 MHz
[B]Storage Device Information[/B]
Disk 0160.0 GBST9160823ASSeagateDVD Writer 0 HL-DT-ST DVD+-RW GSA-T11N ATA Device (HL-DT-ST DVD+/-RW GSA-T11N)LG Electronics
[B]Memory Information[/B]
    Slot 1    DDR2 (PC2-5300)    2048 MBytes    Hyundai Electronics    Slot 2    DDR2 (PC2-5300)    2048 MBytes    Hyundai Electronics
[B]Display Adapter Information[/B]
NVIDIA GeForce 8600M GT256 MBytes DDR2
[B]Sound Adapter Information[/B]
SigmaTel High Definition Audio CODECSigmaTel
[B]Network Adapter Information[/B]
Intel(R) Wireless WiFi Link 4965AGNWIRELESS LANDisconnected  [100 Mbps]Broadcom 440x 10/100 Integrated ControllerWIREDConnected  [100 Mbps]
[B]Operating System[/B]
TypeWindows 7 Ultimate
 

Attachments

  • minidumps.zip
    102.4 KB · Views: 324
Hey...

Wow, your machine is in absolute shambles there. I highly recommend a clean install of Windows 7 while formatting, unless you plan to follow each and every advice below:

Update your Ricoh card reader drivers from your motherboard's site at the manufacturer (Dell):

rimmptsk rimmptsk.sys Wed Nov 15 03:16:23 2006
rimsptsk rimsptsk.sys Tue Nov 14 22:42:45 2006
rixdptsk rixdptsk.sys Tue Nov 14 20:35:19 2006

---------

Update your wireless adapter driver from the manufacturer's site:

netw5v32 netw5v32.sys Thu Mar 26 12:10:37 2009

----------

Navigate to C:\Windows\System32\drivers and delete these old, problematic drivers:

StarOpen StarOpen.SYS Tue Jun 27 15:15:56 2006
pfc pfc.sys Fri Sep 19 19:47:22 2003
OEM02Vfx OEM02Vfx.sys Mon Mar 05 05:45:03 2007
OEM02Dev OEM02Dev.sys Wed Oct 10 22:29:05 2007
PxHelp20 PxHelp20.sys Wed Jun 20 18:26:00 2007

Reboot.

---------

Update your old Bluetooth driver from Dell's site:

btusbflt btusbflt.sys Fri Oct 13 16:45:27 2006
btwavdt btwavdt.sys Thu Nov 02 18:53:30 2006

-------

Update the modem drivers from Dell:

xaudio xaudio.sys Fri Aug 04 20:39:09 2006
HSX_DPV HSX_DPV.sys Thu Nov 02 22:43:26 2006
HSX_CNXT HSX_CNXT.sys Thu Nov 02 22:42:05 2006

--------

Uninstall your Portrait Displays software, to rid the system of this very old driver:

pdihwctl pdihwctl.sys Tue Dec 10 00:26:44 2002

--------

Update your video card driver:

nvlddmkm nvlddmkm.sys Tue Mar 16 22:45:14 2010

Link Removed - Invalid URL

---------

Update this old audio driver, probably from Dell but I dunno:

stwrt stwrt.sys Thu Sep 13 11:29:43 2007

---------

Update your iTunes software to update this old driver:

GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 13:11:27 2006


------

Update your ethernet lan driver from Dell:

bcm4sbxp bcm4sbxp.sys Tue Nov 21 07:25:43 2006

-----

Uninstall Acronis True Image as it is way too old for Windows 7:

tifsfilt tifsfilt.sys Wed Aug 29 08:37:17 2007
snapman snapman.sys Thu Nov 22 03:19:58 2007
timntr timntr.sys Wed Aug 29 08:13:12 2007

-------

Update your Intel Matrix Storage driver which is very old, from Dell:

iaStor iaStor.sys Wed Apr 25 14:27:47 2007
 
One question.... how did you spot those "old" drivers? Just looking at the date stamp or?
BTW, I recall there aren't so many updatetd drivers from DELL's site... you know how they do it... once a new machine has "stable" drivers, they stop upgrading it....
I will have a go anyway, and thanks for helping
 
Just used Dell's update tool but it states there are no updates for the current computer/os combo..... shall'I try to download the drivers from the manufacturers site?(Ricoh, Nvidia etc)... risky?
 
You can update the software manually, and yes you can try searching manufacturers' for the drivers - just make sure you get the right type for you, mobile versions if yours is a Dell note.
 
One question.... how did you spot those "old" drivers? Just looking at the date stamp or?
BTW, I recall there aren't so many updatetd drivers from DELL's site... you know how they do it... once a new machine has "stable" drivers, they stop upgrading it....
I will have a go anyway, and thanks for helping

I'm certainly no Dell fanboi but on this particular point I happen to agree with them.

I've had many experiences which demonstrate that "newer is not always better" with stunning clarity. Once a system is in a stable state, you can rely on that old adage "If it ain't broke... don't fix it!"

Nvidia provides a very good example of this. They use a "unified driver". In case the others here haven't noticed you can go to their site, and no matter what video card you select, you always get the same download. (The only exception I'm aware of is the ION driver). As new models come out this unfied driver is updated and modified to work with the new hardware. Older models will still run with the new drivers but optimizations now favor the newer chips. Thus the best version driver for any given Nvidia video chipset is going to be the last version issued while the given chipset was current.

And, since I know this will be controversial, YES, I have seen plenty of evidence of this in machines I take care of. My own machine has an 8400 video card in it and it absolutely does work better with the older version drivers. I went all the way back to 1.96.21, the last version while this card was current, to get this system stabilized.

Another good example is SoundBlaster. When still running XP there was this beyond stupid switch over to the Microsoft GS Wavetable Synthesizer, abandoning their own very well developed wavetable system. The new drivers totally sucked and the midi sound was utterly intollerable. So, time to get busy and hunt down some older version drivers, which I found on an old CD that came with a PCI128 card I purchased years before. A little hacking in the .INF file and voila! far better sound on mp3, breath taking midi and no more system glitches.

Yes, driver updates are generally a good thing but it is not always helpful to just blindly install the newest versions of everything, especially on older version devices, and especially when the system is stable and running well.
 
I've had many experiences which demonstrate that "newer is not always better" with stunning clarity.

You're right, but it's not only that. Quite often mobile drivers from the manufacturers do not even install on branded notebooks. That's why it is not easy to update notes, hopefully Dell support can help in this case.
 
I've had many experiences which demonstrate that "newer is not always better" with stunning clarity. Once a system is in a stable state, you can rely on that old adage "If it ain't broke... don't fix it!"

And can you please tell us how much experience you have with analyzing and repairing bsod stops? If the answer is 0, this statement is completely irrelevant.

Actually, it's plain out incorrect. ESPECIALLY in this case.

You will not find any reputable bsod analyst in all the land to disagree.

Please don't think I'm singling anything out here. (I gave helpful post rating only yesterday.) :)

People are p.m.ing me for help instead of posting on the forum, partially because of things like this.
 
Last edited:
Just used Dell's update tool but it states there are no updates for the current computer/os combo..... shall'I try to download the drivers from the manufacturers site?(Ricoh, Nvidia etc)... risky?

Yes, do everything you possibly can to update everything mentioned to the newest possible.
 
You're right, but it's not only that. Quite often mobile drivers from the manufacturers do not even install on branded notebooks. That's why it is not easy to update notes, hopefully Dell support can help in this case.

I've seen that one too. Acer is bad for that... had a bunch of Aspire Ones with WiFi problems and the only available answer was to find older Acer drivers and install them. The new ones from Atheros simply would not activate on the version of the A1 I had. I do understand this issue has been fixed on newer machines.

In a 35 year career in electronics (10 as service manager for a major corporation) you can bet I've seen a lot of stuff. I've even seen situations where drivers and programs have accidentally conflicted with one another. Either through overlaps in registry keys or name collisions on dll files... now you want to see a system messed up in a real hurry, that will do it.

I always used to councel my techs to stop, ask for help or take a different approach when they could not pinpoint the exact cause of a problem. Especially with office equipment where they are out there on their own with no "in shop" backup. I was constantly telling them to swap war stories and help eachother learn from experience... You'd be amazed how many people can't do that.

But I've never understood this constant need to mess with things that aren't broken. It's "tube jockey" level troublshooting to just update everything without actually diagnosing the problem... You stand as much chance of introducing instabilities as you do of correcting them.
("Well, we got my video problem solved, now the modem's stopped working"...)

I guess that's why it may appear that I am occasionally engaging in excessive conversation with some people. I'm trying to glean bits of extra information to actually diagnose the problem instead of just handing them a list of stuff to try in the hope some part of it might actually happen to fix the problem. Experience teaches there is no such thing as a "one answer diagnosis"... Every situation is different and has to be weighed on it's own merrits.



("Tube Jockeys" is a derogatory term that was applied to low level technicians in the Vaccuum Tube days. There were a whole bunch of people working in the industry who couldn't fix a darned thing except for swapping out tubes, hoping the thing came back to life.)
 
Last edited:
Ok, some drivers were updated using Dell's Vista 32 version (newer than the installed one), some from the manufacturer site, but I couldn't make it to upgrade all the drivers in the list....
I hope it will help.... will let you know. Thanks for helping
 
Back to school guys, I have ended downloading drivermax to update all the available drivers.

Probabily it wasn't a perfect move, it will make difficult to spot problems....

Now what:
- resuming from sleep hangs the computer on a black screen, absolutely no disk activity (happened once)
- got a ice BSOD!

I'm attaching the minidump again, hoping someone can help!
 

Attachments

  • 101210-44756-01.zip
    32.9 KB · Views: 313
Yep, you guessed well. Driver download utilities are terrible and cause so many problems, many unrecoverable without a very high degree of knowledge and OS intricacies.

In your case here, the Intel Matrix Storage driver is causing the bsods, likely from the Drivermax program. And you also have many other problems now on the machine from it, like many 2007 drivers. Not good at all.

You'll want to visit Intel's or your motherboard website to install the latest driver mentioned above, from either of those places.

You'll also want to completely uninstall all Acronis software to remove the multiple 2007 drivers on the machine.

Also update your very old 2007 mouse driver, from the manufacturer's site:

pelmouse pelmouse.sys Thu Jun 07 04:37:22 2007
pelps2m pelps2m.sys Mon Jul 23 04:57:51 2007

Also, you'll have to update the Video Capture and TV Adapter drivers from the manufacturer's site:

OEM02Dev OEM02Dev.sys Wed Oct 10 22:29:05 2007
OEM02Vfx OEM02Vfx.sys Mon Mar 05 05:45:03 2007

Also, now you'll have to update the Logitech camera drivers from Logitech's website:

LVUSBSta LVUSBSta.sys Sat Jul 26 10:59:36 2008

Also, now you'll have to update modem drivers from manufacturer's website:

HSXHWAZL HSXHWAZL.sys Fri Feb 13 15:58:15 2009
HSX_DPV HSX_DPV.sys Fri Feb 13 16:00:17 2009
mdmxsdk mdmxsdk.sys Mon Jun 19 17:26:59 2006

Also, now you'll have to update your audio driver from the motherboard website:

stwrt stwrt.sys Fri Feb 15 17:36:49 2008

Also now, you'll have to find a way to get rid of this old driver:

fssfltr fssfltr.sys Thu Aug 06 01:47:44 2009

And this one is too old too:

skbdrv skbdrv.sys Tue May 26 01:17:14 2009

This too:

Lbd Lbd.sys Fri Apr 17 07:51:35 2009

------------

Suggest clean install with a format instead and don't use DriverMax or any others any longer.
 
Last edited:
The installed drivers are the latest available, with the exception of thos installed by third party utilities like True Image.

Strange here, although I have installed Windows 7 ontop a previous Vista Install, I had no BSOD for the first couple months... True image installed and working.....then little by little, BSOD started appearing....
 
All I can say further is that any driver from before July 2009 has extremely high chances of causing bsods on Windows 7.

This leaves you with only the following choices, honestly:

1) Use Vista or XP instead by clean installing.

2) Find a way to update all those drivers mentioned. Remove the ones you can't update by manually deleting them and hope for the best. It all comes down to the fact that bsods will continue with pre-July 2009 drivers on the system. Since it's your machine, you'll have to be the one to decide what to do in this scenario.

Good luck with your desired choice. :)
 
@TorrenTg, one question: how can I uninstall bulky drivers, if they don't show in the driver list into the device manager?

For example, pelmouse.sys doesn't appear in the drivers used by the available mouses/pads...and there's no "Primax" device or software into the program options in the control panel....apparently no device using such a driver....

Another strange thing: I have upgraded Acronis true image to version 2011 but the latest dump (I'm attaching here), still shows an old driver by Acronis dated 2007....I'm suspecting there's some unused software or device that left over those old drivers... I would like to find a safe way to wipe them out without having to reinstall Windows 7 from scratch...
 

Attachments

  • 101710-42947-01.zip
    33.1 KB · Views: 300
Last edited:
how can I uninstall bulky drivers, if they don't show in the driver list into the device manager?

You should see them in Device manager and in Control Panel -> Programs and components.


101710-42947-01.dmp
BugCheck 1000007E, {c0000005, 94da209c, 807c1bc8, 807c17a0}
Probably caused by : memory_corruption (MEMORY_CORRUPTION_STRIDE)
Stack: nt! nt! nt! USBPORT! USBPORT! USBPORT! USBPORT!


1. Uninstall Lavasoft Ad-Aware:

Lbd.sys Fri Apr 17 14:51:35 2009

FAQs | Lavasoft

Replace it with Malware bytes if necessary:

Malwarebytes



2. Update your old drivers:

bcm4sbxp.sys Tue Nov 21 14:25:43 2006
Broadcom 440x 10/100 Integrated Controller

tifsfilt.sys Wed Aug 29 15:37:17 2007
Acronis True Image

OEM02Dev.sys Thu Oct 11 05:29:05 2007
Creative Video Capture

DefragFS.SYS Wed Aug 19 20:31:36 2009
PerfectDisk Raxco Software, Inc.

pelmouse.sys Thu Jun 07 11:37:22 2007
Primax Mouse

stwrt.sys Sat Feb 16 00:36:49 2008
IDT PC Audio

VSTAZL3.SYS Thu Oct 16 03:30:03 2008
Conexant 56k Modem - update or disable this divice

LVUSBSta.sys Sat Jul 26 17:59:36 2008
Logitech quickcam - update or disable this divice

iaStor.sys Thu Dec 17 20:23:09 2009
Intel Matrix Storage

SynTP.sys Fri Aug 28 04:59:32 2009
Synaptics Touchpad




3. Run memtest overnight:


RAM - Test with Memtest86+ - Windows 7 Forums






Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\a\Minidump\D M P\101710-42947-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e18000 PsLoadedModuleList = 0x82f60810
Debug session time: Sat Oct 16 22:39:45.757 2010 (UTC - 5:00)
System Uptime: 0 days 2:20:56.496
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 94da209c, 807c1bc8, 807c17a0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 94da209c, The address that the exception occurred at
Arg3: 807c1bc8, Exception Record Address
Arg4: 807c17a0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
USBPORT!USBPORT_TurnUsbControllerOff+2a
94da209c 83781c00        cmp     dword ptr [eax+1Ch],0

EXCEPTION_RECORD:  807c1bc8 -- (.exr 0xffffffff807c1bc8)
ExceptionAddress: 94da209c (USBPORT!USBPORT_TurnUsbControllerOff+0x0000002a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 01000022
Attempt to read from address 01000022

CONTEXT:  807c17a0 -- (.cxr 0xffffffff807c17a0)
eax=01000006 ebx=88bd5028 ecx=88bd5300 edx=00000000 esi=88bd50e0 edi=a825ca10
eip=94da209c esp=807c1c90 ebp=807c1c98 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
USBPORT!USBPORT_TurnUsbControllerOff+0x2a:
94da209c 83781c00        cmp     dword ptr [eax+1Ch],0 ds:0023:01000022=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  01000022

READ_ADDRESS: GetPointerFromAddress: unable to read from 82f80718
Unable to read MiSystemVaType memory at 82f60160
 01000022 

FOLLOWUP_IP: 
USBPORT!USBPORT_TurnUsbControllerOff+2a
94da209c 83781c00        cmp     dword ptr [eax+1Ch],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 94d9b29e to 94da209c

STACK_TEXT:  
807c1c98 94d9b29e 88bd5028 a825cac8 a825ca10 USBPORT!USBPORT_TurnUsbControllerOff+0x2a
807c1cb4 94d9a715 88bd5028 a825ca10 a825ca10 USBPORT!USBPORT_FdoDevicePowerState+0x85
807c1cd0 94d837b5 88bd50f0 88bd50e0 86059fe0 USBPORT!USBPORT_FdoPowerIrp+0x132
807c1cf8 82e23823 88bd5028 88bd52cc 00000000 USBPORT!USBPORT_Dispatch+0x17a
807c1d50 830266d3 00000000 af74d541 00000000 nt!PopIrpWorker+0x351
807c1d90 82ed80f9 82e234d2 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


CHKIMG_EXTENSION: !chkimg -lo 50 -db !USBPORT
4 errors : !USBPORT (94da209a-94da20a3)
94da2090  00  00  02  0f  85  ba  00  00  00  8b *47 *00  83  78  1c  00 ..........G..x..
94da20a0  57  74 *00 *12  78  10  8b  cf  ff  15  b4  81  da  94  8b  4f Wt..x..........O

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xffffffff807c17a0 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 94da209c, The address that the exception occurred at
Arg3: 807c1bc8, Exception Record Address
Arg4: 807c17a0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
USBPORT!USBPORT_TurnUsbControllerOff+2a
94da209c 83781c00        cmp     dword ptr [eax+1Ch],0

EXCEPTION_RECORD:  807c1bc8 -- (.exr 0xffffffff807c1bc8)
ExceptionAddress: 94da209c (USBPORT!USBPORT_TurnUsbControllerOff+0x0000002a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 01000022
Attempt to read from address 01000022

CONTEXT:  807c17a0 -- (.cxr 0xffffffff807c17a0)
eax=01000006 ebx=88bd5028 ecx=88bd5300 edx=00000000 esi=88bd50e0 edi=a825ca10
eip=94da209c esp=807c1c90 ebp=807c1c98 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
USBPORT!USBPORT_TurnUsbControllerOff+0x2a:
94da209c 83781c00        cmp     dword ptr [eax+1Ch],0 ds:0023:01000022=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  01000022

READ_ADDRESS: GetPointerFromAddress: unable to read from 82f80718
Unable to read MiSystemVaType memory at 82f60160
 01000022 

FOLLOWUP_IP: 
USBPORT!USBPORT_TurnUsbControllerOff+2a
94da209c 83781c00        cmp     dword ptr [eax+1Ch],0

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 94d9b29e to 94da209c

STACK_TEXT:  
807c1c98 94d9b29e 88bd5028 a825cac8 a825ca10 USBPORT!USBPORT_TurnUsbControllerOff+0x2a
807c1cb4 94d9a715 88bd5028 a825ca10 a825ca10 USBPORT!USBPORT_FdoDevicePowerState+0x85
807c1cd0 94d837b5 88bd50f0 88bd50e0 86059fe0 USBPORT!USBPORT_FdoPowerIrp+0x132
807c1cf8 82e23823 88bd5028 88bd52cc 00000000 USBPORT!USBPORT_Dispatch+0x17a
807c1d50 830266d3 00000000 af74d541 00000000 nt!PopIrpWorker+0x351
807c1d90 82ed80f9 82e234d2 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


CHKIMG_EXTENSION: !chkimg -lo 50 -db !USBPORT
4 errors : !USBPORT (94da209a-94da20a3)
94da2090  00  00  02  0f  85  ba  00  00  00  8b *47 *00  83  78  1c  00 ..........G..x..
94da20a0  57  74 *00 *12  78  10  8b  cf  ff  15  b4  81  da  94  8b  4f Wt..x..........O

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xffffffff807c17a0 ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption


80bc4000 80bcc000   kdcom    kdcom.dll    Tue Jul 14 04:08:58 2009 (4A5BDAAA)
81e8c000 81e97000   hidusb   hidusb.sys   Tue Jul 14 02:51:04 2009 (4A5BC868)
81e97000 81eaa000   HIDCLASS HIDCLASS.SYS Tue Jul 14 02:51:01 2009 (4A5BC865)
81eaa000 81eb0480   HIDPARSE HIDPARSE.SYS Tue Jul 14 02:50:59 2009 (4A5BC863)
81ebd000 81ec8000   mouhid   mouhid.sys   Tue Jul 14 02:45:08 2009 (4A5BC704)
81ec8000 81ed0800   point32  point32.sys  Tue Jun 29 11:54:24 2010 (4C29B4C0)
81f2f000 81f39000   Dxapi    Dxapi.sys    Tue Jul 14 02:25:25 2009 (4A5BC265)
81f44000 81f5f000   luafv    luafv.sys    Tue Jul 14 02:15:44 2009 (4A5BC020)
81f5f000 81f6f780   pxrts    pxrts.sys    Fri Oct 08 18:06:44 2010 (4CAF3384)
81f70000 81f79340   tifsfilt tifsfilt.sys Wed Aug 29 15:37:17 2007 (46D5687D)
81f7a000 81f94000   WudfPf   WudfPf.sys   Tue Jul 14 02:50:13 2009 (4A5BC835)
81f94000 81fa9000   DefragFS DefragFS.SYS Wed Aug 19 20:31:36 2009 (4A8C36F8)
81fa9000 81fb4e00   fssfltr  fssfltr.sys  Thu Aug 06 08:47:44 2009 (4A7A6E80)
81fb5000 81fc5000   lltdio   lltdio.sys   Tue Jul 14 02:53:18 2009 (4A5BC8EE)
81fc5000 81fd5000   ndisuio  ndisuio.sys  Tue Jul 14 02:53:51 2009 (4A5BC90F)
81fd5000 81fe8000   rspndr   rspndr.sys   Tue Jul 14 02:53:20 2009 (4A5BC8F0)
82600000 8261e000   cdd      cdd.dll      Tue Jul 14 04:04:18 2009 (4A5BD992)
82620000 8266d000   ATMFD    ATMFD.DLL    Thu May 27 06:49:36 2010 (4BFDEBD0)
82770000 829bb000   win32k   win32k.sys   Wed Sep 01 05:34:29 2010 (4C7DBBB5)
829d0000 829d9000   TSDDD    TSDDD.dll    Tue Jul 14 03:01:40 2009 (4A5BCAE4)
82e18000 83228000   nt       ntkrpamp.exe Sat Jun 19 06:55:24 2010 (4C1C3FAC)
83228000 8325f000   hal      halmacpi.dll Tue Jul 14 02:11:03 2009 (4A5BBF07)
8c604000 8c67c000   mcupdate mcupdate.dll Tue Jul 14 04:06:41 2009 (4A5BDA21)
8c67c000 8c68d000   PSHED    PSHED.dll    Tue Jul 14 04:09:36 2009 (4A5BDAD0)
8c68d000 8c695000   BOOTVID  BOOTVID.dll  Tue Jul 14 04:04:34 2009 (4A5BD9A2)
8c695000 8c6d7000   CLFS     CLFS.SYS     Tue Jul 14 02:11:10 2009 (4A5BBF0E)
8c6d7000 8c782000   CI       CI.dll       Tue Jul 14 04:09:28 2009 (4A5BDAC8)
8c782000 8c7f3000   Wdf01000 Wdf01000.sys Tue Jul 14 02:11:36 2009 (4A5BBF28)
8c800000 8c826000   SCSIPORT SCSIPORT.SYS Tue Jul 14 02:45:55 2009 (4A5BC733)
8c826000 8c836000   volmgr   volmgr.sys   Tue Jul 14 02:11:25 2009 (4A5BBF1D)
8c83d000 8c84b000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:11:25 2009 (4A5BBF1D)
8c84b000 8c893000   ACPI     ACPI.sys     Tue Jul 14 02:11:11 2009 (4A5BBF0F)
8c893000 8c89c000   WMILIB   WMILIB.SYS   Tue Jul 14 02:11:22 2009 (4A5BBF1A)
8c89c000 8c8a4000   msisadrv msisadrv.sys Tue Jul 14 02:11:09 2009 (4A5BBF0D)
8c8a4000 8c8af000   vdrvroot vdrvroot.sys Tue Jul 14 02:46:19 2009 (4A5BC74B)
8c8af000 8c8d9000   pci      pci.sys      Tue Jul 14 02:11:16 2009 (4A5BBF14)
8c8d9000 8c8ea000   partmgr  partmgr.sys  Tue Jul 14 02:11:35 2009 (4A5BBF27)
8c8ea000 8c90d000   MpFilter MpFilter.sys Sat Mar 20 06:03:26 2010 (4BA4490E)
8c90d000 8c92e000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:25:49 2009 (4A5BC27D)
8c92e000 8c93b000   watchdog watchdog.sys Tue Jul 14 02:24:10 2009 (4A5BC21A)
8c93b000 8c946000   Msfs     Msfs.SYS     Tue Jul 14 02:11:26 2009 (4A5BBF1E)
8c946000 8c954000   Npfs     Npfs.SYS     Tue Jul 14 02:11:31 2009 (4A5BBF23)
8c954000 8c96b000   tdx      tdx.sys      Tue Jul 14 02:12:10 2009 (4A5BBF4A)
8c96b000 8c976000   TDI      TDI.SYS      Tue Jul 14 02:12:12 2009 (4A5BBF4C)
8c976000 8c9d0000   afd      afd.sys      Tue Jul 14 02:12:34 2009 (4A5BBF62)
8ca00000 8ca25000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:04:22 2009 (4B21C4C6)
8ca25000 8ca2d000   rdprefmp rdprefmp.sys Tue Jul 14 03:01:41 2009 (4A5BCAE5)
8ca30000 8ca7b000   volmgrx  volmgrx.sys  Tue Jul 14 02:11:41 2009 (4A5BBF2D)
8ca7b000 8ca82000   intelide intelide.sys Tue Jul 14 02:11:19 2009 (4A5BBF17)
8ca82000 8ca90000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:11:15 2009 (4A5BBF13)
8ca90000 8ca98000   compbatt compbatt.sys Tue Jul 14 02:19:18 2009 (4A5BC0F6)
8ca98000 8caa3000   BATTC    BATTC.SYS    Tue Jul 14 02:19:15 2009 (4A5BC0F3)
8caa3000 8cab9000   mountmgr mountmgr.sys Tue Jul 14 02:11:27 2009 (4A5BBF1F)
8cab9000 8cabeb80   pxscan   pxscan.sys   Fri Oct 08 18:06:43 2010 (4CAF3383)
8cabf000 8caf3000   fltmgr   fltmgr.sys   Tue Jul 14 02:11:13 2009 (4A5BBF11)
8caf3000 8cb01080   Lbd      Lbd.sys      Fri Apr 17 14:51:35 2009 (49E86D47)
8cb02000 8cbb9000   ndis     ndis.sys     Tue Jul 14 02:12:24 2009 (4A5BBF58)
8cbb9000 8cbf7000   NETIO    NETIO.SYS    Tue Jul 14 02:12:35 2009 (4A5BBF63)
8cc01000 8cdb4000   iaStor   iaStor.sys   Thu Dec 17 20:23:09 2009 (4B2A770D)
8cdb4000 8cdbd000   atapi    atapi.sys    Tue Jul 14 02:11:15 2009 (4A5BBF13)
8cdbd000 8cde0000   ataport  ataport.SYS  Tue Jul 14 02:11:18 2009 (4A5BBF16)
8cde0000 8cde9000   amdxata  amdxata.sys  Tue May 19 20:57:35 2009 (4A12F30F)
8cde9000 8cdfa000   fileinfo fileinfo.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
8ce00000 8ce08000   rdpencdd rdpencdd.sys Tue Jul 14 03:01:39 2009 (4A5BCAE3)
8ce08000 8cf37000   Ntfs     Ntfs.sys     Tue Jul 14 02:12:05 2009 (4A5BBF45)
8cf37000 8cf62000   msrpc    msrpc.sys    Tue Jul 14 02:11:59 2009 (4A5BBF3F)
8cf62000 8cf75000   ksecdd   ksecdd.sys   Tue Jul 14 02:11:56 2009 (4A5BBF3C)
8cf75000 8cfd2000   cng      cng.sys      Tue Jul 14 02:32:55 2009 (4A5BC427)
8cfd2000 8cfe0000   pcw      pcw.sys      Tue Jul 14 02:11:10 2009 (4A5BBF0E)
8cfe0000 8cfe9000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:11:14 2009 (4A5BBF12)
8cfe9000 8cff5000   vga      vga.sys      Tue Jul 14 02:25:50 2009 (4A5BC27E)
8cff5000 8cffd000   RDPCDD   RDPCDD.sys   Tue Jul 14 03:01:40 2009 (4A5BCAE4)
8d000000 8d01f000   cdrom    cdrom.sys    Tue Jul 14 02:11:24 2009 (4A5BBF1C)
8d023000 8d16c000   tcpip    tcpip.sys    Mon Jun 14 06:36:59 2010 (4C15A3DB)
8d16c000 8d19d000   fwpkclnt fwpkclnt.sys Tue Jul 14 02:12:03 2009 (4A5BBF43)
8d19d000 8d1a5000   hwpolicy hwpolicy.sys Tue Jul 14 02:11:01 2009 (4A5BBF05)
8d1a5000 8d1d7000   fvevol   fvevol.sys   Sat Sep 26 05:24:21 2009 (4ABD7B55)
8d1d7000 8d1e8000   disk     disk.sys     Tue Jul 14 02:11:28 2009 (4A5BBF20)
8d1e8000 8d1ef000   Beep     Beep.SYS     Tue Jul 14 02:45:00 2009 (4A5BC6FC)
8d1ef000 8d1f9000   pelmouse pelmouse.sys Thu Jun 07 11:37:22 2007 (4667C3C2)
8d200000 8d22d000   rdyboost rdyboost.sys Tue Jul 14 02:22:02 2009 (4A5BC19A)
8d230000 8d2c1100   timntr   timntr.sys   Wed Jun 02 15:57:37 2010 (4C065541)
8d2c2000 8d2ca380   vmstorfl vmstorfl.sys Tue Jul 14 02:28:44 2009 (4A5BC32C)
8d2cb000 8d30a000   volsnap  volsnap.sys  Tue Jul 14 02:11:34 2009 (4A5BBF26)
8d30a000 8d3bffa0   tdrpm273 tdrpm273.sys Tue Aug 10 12:56:21 2010 (4C612245)
8d3c0000 8d3c8000   spldr    spldr.sys    Mon May 11 19:13:47 2009 (4A084EBB)
8d3c8000 8d3eff80   snapman  snapman.sys  Tue Aug 10 13:15:28 2010 (4C6126C0)
8d3f0000 8d400000   mup      mup.sys      Tue Jul 14 02:14:14 2009 (4A5BBFC6)
8d400000 8d407000   Null     Null.SYS     Tue Jul 14 02:11:12 2009 (4A5BBF10)
8d407000 8d42c000   CLASSPNP CLASSPNP.SYS Tue Jul 14 02:11:20 2009 (4A5BBF18)
8d42c000 8d5df000   dump_iaStor dump_iaStor.sys Thu Dec 17 20:23:09 2009 (4B2A770D)
92a00000 92a34000   ks       ks.sys       Thu Mar 04 05:57:52 2010 (4B8F2FC0)
92a38000 92a6a000   netbt    netbt.sys    Tue Jul 14 02:12:18 2009 (4A5BBF52)
92a6a000 92a71000   wfplwf   wfplwf.sys   Tue Jul 14 02:53:51 2009 (4A5BC90F)
92a71000 92a90000   pacer    pacer.sys    Tue Jul 14 02:53:58 2009 (4A5BC916)
92a90000 92a9e000   netbios  netbios.sys  Tue Jul 14 02:53:54 2009 (4A5BC912)
92a9e000 92ab1000   wanarp   wanarp.sys   Tue Jul 14 02:55:02 2009 (4A5BC956)
92ab1000 92ac1000   termdd   termdd.sys   Tue Jul 14 03:01:35 2009 (4A5BCADF)
92ac1000 92b02000   rdbss    rdbss.sys    Tue Jul 14 02:14:26 2009 (4A5BBFD2)
92b02000 92b0c000   nsiproxy nsiproxy.sys Tue Jul 14 02:12:08 2009 (4A5BBF48)
92b0c000 92b16000   mssmbios mssmbios.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD)
92b16000 92b22000   discache discache.sys Tue Jul 14 02:24:04 2009 (4A5BC214)
92b22000 92b3a000   dfsc     dfsc.sys     Tue Jul 14 02:14:16 2009 (4A5BBFC8)
92b3a000 92b48000   blbdrive blbdrive.sys Tue Jul 14 02:23:04 2009 (4A5BC1D8)
92b48000 92b69000   tunnel   tunnel.sys   Tue Jul 14 02:54:03 2009 (4A5BC91B)
92b69000 92b7b000   intelppm intelppm.sys Tue Jul 14 02:11:03 2009 (4A5BBF07)
92b7b000 92b9d000   ndiswan  ndiswan.sys  Tue Jul 14 02:54:34 2009 (4A5BC93A)
92b9d000 92bb5000   raspppoe raspppoe.sys Tue Jul 14 02:54:53 2009 (4A5BC94D)
92bb5000 92bcc000   raspptp  raspptp.sys  Tue Jul 14 02:54:47 2009 (4A5BC947)
92bcc000 92be3000   rassstp  rassstp.sys  Tue Jul 14 02:54:57 2009 (4A5BC951)
92be3000 92bf1000   umbus    umbus.sys    Tue Jul 14 02:51:38 2009 (4A5BC88A)
93400000 93418000   rasl2tp  rasl2tp.sys  Tue Jul 14 02:54:33 2009 (4A5BC939)
93418000 93423000   ndistapi ndistapi.sys Tue Jul 14 02:54:24 2009 (4A5BC930)
93423000 9342d000   rdpbus   rdpbus.sys   Tue Jul 14 03:02:40 2009 (4A5BCB20)
9342d000 9342e380   swenum   swenum.sys   Tue Jul 14 02:45:08 2009 (4A5BC704)
9342f000 93a8e000   NETwLv32 NETwLv32.sys Mon Aug 16 17:26:04 2010 (4C694A7C)
93a8e000 93a9f000   bcm4sbxp bcm4sbxp.sys Tue Nov 21 14:25:43 2006 (4562F047)
93a9f000 93acb000   1394ohci 1394ohci.sys Tue Jul 14 02:51:59 2009 (4A5BC89F)
93acb000 93ae4000   sdbus    sdbus.sys    Sat Oct 10 05:31:24 2009 (4ACFF1FC)
93ae4000 93af5000   rimmptsk rimmptsk.sys Thu Jun 25 10:58:09 2009 (4A432E11)
93af5000 93b09000   rimsptsk rimsptsk.sys Thu Jun 25 10:10:46 2009 (4A4322F6)
93b09000 93b5b000   rixdptsk rixdptsk.sys Thu Jun 25 10:25:57 2009 (4A432685)
93b5b000 93b73000   i8042prt i8042prt.sys Tue Jul 14 02:11:23 2009 (4A5BBF1B)
93b73000 93ba9380   SynTP    SynTP.sys    Fri Aug 28 04:59:32 2009 (4A973A04)
93baa000 93bab700   USBD     USBD.SYS     Tue Jul 14 02:51:05 2009 (4A5BC869)
93bac000 93bb9000   mouclass mouclass.sys Tue Jul 14 02:11:15 2009 (4A5BBF13)
93bb9000 93bbd480   pxkbf    pxkbf.sys    Fri Oct 08 18:06:41 2010 (4CAF3381)
93bbe000 93bcb000   kbdclass kbdclass.sys Tue Jul 14 02:11:15 2009 (4A5BBF13)
93bcb000 93bce700   CmBatt   CmBatt.sys   Tue Jul 14 02:19:18 2009 (4A5BC0F6)
93bcf000 93bd8000   wmiacpi  wmiacpi.sys  Tue Jul 14 02:19:16 2009 (4A5BC0F4)
93bd8000 93be5000   CompositeBus CompositeBus.sys Tue Jul 14 02:45:26 2009 (4A5BC716)
93be5000 93bf7000   AgileVpn AgileVpn.sys Tue Jul 14 02:55:00 2009 (4A5BC954)
93c25000 93c69000   usbhub   usbhub.sys   Tue Jul 14 02:52:06 2009 (4A5BC8A6)
93c69000 93c7a000   NDProxy  NDProxy.SYS  Tue Jul 14 02:54:27 2009 (4A5BC933)
93c83000 93cd8000   stwrt    stwrt.sys    Sat Feb 16 00:36:49 2008 (47B61401)
93cd8000 93d07000   portcls  portcls.sys  Tue Jul 14 02:51:00 2009 (4A5BC864)
93d07000 93d20000   drmk     drmk.sys     Tue Jul 14 03:36:05 2009 (4A5BD2F5)
93d20000 93d5d000   VSTAZL3  VSTAZL3.SYS  Thu Oct 16 03:30:03 2008 (48F68B0B)
93d5d000 93d96880   OEM02Dev OEM02Dev.sys Thu Oct 11 05:29:05 2007 (470D8A71)
93d97000 93da8000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:12:47 2009 (4A5BBF6F)
93dba000 93e00000   nwifi    nwifi.sys    Tue Jul 14 02:51:59 2009 (4A5BC89F)
94205000 94c82dc0   nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:14 2010 (4C379162)
94c83000 94c84040   nvBridge nvBridge.kmd Sat Jul 10 00:10:11 2010 (4C379033)
94c85000 94d3c000   dxgkrnl  dxgkrnl.sys  Fri Oct 02 03:48:33 2009 (4AC54DE1)
94d3c000 94d75000   dxgmms1  dxgmms1.sys  Tue Jul 14 02:25:25 2009 (4A5BC265)
94d75000 94d80000   usbuhci  usbuhci.sys  Tue Jul 14 02:51:10 2009 (4A5BC86E)
94d80000 94dcb000   USBPORT  USBPORT.SYS  Tue Jul 14 02:51:13 2009 (4A5BC871)
94dcb000 94dda000   usbehci  usbehci.sys  Tue Jul 14 02:51:14 2009 (4A5BC872)
94dda000 94df9000   HDAudBus HDAudBus.sys Tue Jul 14 02:50:55 2009 (4A5BC85F)
95200000 95217000   usbccgp  usbccgp.sys  Tue Jul 14 02:51:31 2009 (4A5BC883)
95217000 9521f900   LVUSBSta LVUSBSta.sys Sat Jul 26 17:59:36 2008 (488B3BD8)
95220000 95221d00   OEM02Vfx OEM02Vfx.sys Mon Mar 05 12:45:03 2007 (45EBF4AF)
95227000 95329000   VSTDPV3  VSTDPV3.SYS  Thu Oct 16 03:32:04 2008 (48F68B84)
95329000 953de000   VSTCNXT3 VSTCNXT3.SYS Thu Oct 16 03:29:13 2008 (48F68AD9)
953de000 953eb000   modem    modem.sys    Tue Jul 14 02:55:24 2009 (4A5BC96C)
953eb000 953f8000   crashdmp crashdmp.sys Tue Jul 14 02:45:50 2009 (4A5BC72E)
9fe0a000 9fe8f000   HTTP     HTTP.sys     Tue Jul 14 02:12:53 2009 (4A5BBF75)
9fe8f000 9fea8000   bowser   bowser.sys   Tue Jul 14 02:14:21 2009 (4A5BBFCD)
9fea8000 9feba000   mpsdrv   mpsdrv.sys   Tue Jul 14 02:52:52 2009 (4A5BC8D4)
9feba000 9fedd000   mrxsmb   mrxsmb.sys   Sat Feb 27 09:32:02 2010 (4B88CA72)
9fedd000 9ff18000   mrxsmb10 mrxsmb10.sys Sat Feb 27 09:32:21 2010 (4B88CA85)
9ff18000 9ff33000   mrxsmb20 mrxsmb20.sys Sat Feb 27 09:32:11 2010 (4B88CA7B)
9ff4b000 9ff75000   fastfat  fastfat.SYS  Tue Jul 14 02:14:01 2009 (4A5BBFB9)
9ff75000 9ff7de00   MpNWMon  MpNWMon.sys  Sat Mar 20 06:03:24 2010 (4BA4490C)
a5e27000 a5ebe000   peauth   peauth.sys   Tue Jul 14 03:35:44 2009 (4A5BD2E0)
a5ebe000 a5edc000   SbieDrv  SbieDrv.sys  Wed Feb 03 12:38:44 2010 (4B695234)
a5edc000 a5efd000   srvnet   srvnet.sys   Fri Aug 27 06:30:39 2010 (4C77315F)
a5efd000 a5f0a000   tcpipreg tcpipreg.sys Tue Jul 14 02:54:14 2009 (4A5BC926)
a5f0a000 a5f59000   srv2     srv2.sys     Fri Aug 27 06:30:45 2010 (4C773165)
a5f59000 a5faa000   srv      srv.sys      Fri Aug 27 06:31:26 2010 (4C77318E)
a5faa000 a5fd0340   afcdp    afcdp.sys    Mon Aug 30 15:11:24 2010 (4C7B9FEC)
a5fd1000 a5fda000   asyncmac asyncmac.sys Tue Jul 14 02:54:46 2009 (4A5BC946)
b9a27000 b9bda000   hiber_iaStor hiber_iaStor.sys Thu Dec 17 20:23:09 2009 (4B2A770D)
b9bda000 b9beb000   hiber_dumpfve hiber_dumpfve.sys Tue Jul 14 02:12:47 2009 (4A5BBF6F)
c7200000 c7264000   bthport  bthport.sys  Tue Jul 14 02:51:30 2009 (4A5BC882)
c7264000 c7288000   rfcomm   rfcomm.sys   Tue Jul 14 02:51:41 2009 (4A5BC88D)
c7288000 c7295000   BthEnum  BthEnum.sys  Tue Jul 14 02:51:35 2009 (4A5BC887)
c7295000 c72b0000   bthpan   bthpan.sys   Tue Jul 14 02:51:43 2009 (4A5BC88F)
c72b0000 c72c2000   bthmodem bthmodem.sys Tue Jul 14 02:51:34 2009 (4A5BC886)
c72c2000 c72ce000   kbdhid   kbdhid.sys   Tue Jul 14 02:45:09 2009 (4A5BC705)
c73e5000 c73f7000   BTHUSB   BTHUSB.sys   Tue Jul 14 02:51:36 2009 (4A5BC888)

Unloaded modules:
c73da000 c73e5000   monitor.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
9ff7e000 9ffe8000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0006A000
81ef5000 81f02000   BthEnum.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
81e28000 81e8c000   bthport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00064000
93da8000 93dba000   BTHUSB.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00012000
81ed1000 81ef5000   rfcomm.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00024000
81f02000 81f1d000   bthpan.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0001B000
81eb1000 81ebd000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
81f1d000 81f2f000   bthmodem.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00012000
c7216000 c73c9000   hiber_iaStor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  001B3000
c73c9000 c73da000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
81f39000 81f44000   monitor.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
9ff33000 9ff4b000   parport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00018000
8d42c000 8d439000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
8d439000 8d5ec000   dump_iaStor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  001B3000
8d5ec000 8d5fd000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
93c7a000 93c83000   LVUSBSta.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
8c8ea000 8c9ea000   sptd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00100000
 
You should see them in Device manager and in Control Panel -> Programs and components.

I'm in there!


1. Uninstall Lavasoft Ad-Aware:

I did

http://www.lavasoft.com/mylavasoft/support/faqs
bcm4sbxp.sys Tue Nov 21 14:25:43 2006
Broadcom 440x 10/100 Integrated Controller

Device manager shows a driver with "13/10/2008" timestamp, how is that? Broadcom itself has no other drivers newer than this...



tifsfilt.sys Wed Aug 29 15:37:17 2007
Acronis True Image

I have installed a few days ago the latest version of True Image 2011.....




DefragFS.SYS Wed Aug 19 20:31:36 2009
PerfectDisk Raxco Software, Inc.

This version is the latest in the 10 series. BTW it shows a "Windows 7 compatible" logo...



pelmouse.sys Thu Jun 07 11:37:22 2007
Primax Mouse

This driver apparently is not used (I have also listed the hidden devices)... where can I spot this "intruder"?



iaStor.sys Thu Dec 17 20:23:09 2009
Intel Matrix Storage

Should be the latest available. Will check again.



Did run the memtest, but will go for the overnight option...
 
Back
Top