BSOD: HP Pavilion dv6500 Notebook PC

[crucifixio]

Windows 7 is
- x86 (32-bit)
- Not the original installed OS on the system - it came with Vista 32 bit
- Full Retail = you purchased it from retailer

- System is 3 years old.
- OS is 2 weeks old.

I keep getting BSOD. Tried to format PC 2 weeks ago and install new partition of windows 7. Still getting problems.

Thank you for your time in advance!

 

[zigzag3143]

Windows 7 is
- x86 (32-bit)
- Not the original installed OS on the system - it came with Vista 32 bit
- Full Retail = you purchased it from retailer

- System is 3 years old.
- OS is 2 weeks old.

I keep getting BSOD. Tried to format PC 2 weeks ago and install new partition of windows 7. Still getting problems.

Thank you for your time in advance!

No DMP file included in upload try this method either you renamed *.dmp something else like *.dmp.txt or you didnt run Jgriffs app as admin


If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the appropriate section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

 

[CarlTR6]

Welcome to the forum; I am sorry you are having problems. I will take a look.

ZigZag got it. He types faster than I do anyway,

 

[crucifixio]

Windows 7 is
- x86 (32-bit)
- Not the original installed OS on the system - it came with Vista 32 bit
- Full Retail = you purchased it from retailer

- System is 3 years old.
- OS is 2 weeks old.

I keep getting BSOD. Tried to format PC 2 weeks ago and install new partition of windows 7. Still getting problems.

Thank you for your time in advance!

No DMP file included in upload try this method


If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the appropriate section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Ah sorry for this... I have been experimenting trying to solve the problem before getting here and one of the things I read online and tried was deleting the sysdata files and adjusting Memory settings to not create new ones... I will have to revert to defaults in order to get minidump files right? Will do that tomorrow (don't have my laptop here with me now). Thank you both, CarlTR6 & zigzag3143, so much for the quick reply.

 

[CarlTR6]

You are welcome. Always keep your computer set to store mini dumps. The last part of the first post in this tutorial will show you how to do that: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[crucifixio]

Minidump Files

Hi all,

Here are the minidump files.

Thanks for all the help.

 

[CarlTR6]

You are welcome. I looked at all four dumps. The dumps blame a Wi-Fi driver, a video driver, a network driver and Direct X. More than likely none of these are the real causes. The dumps indicate memory corruption and driver problems.

For troubleshooting purposes, I recommend that you uninstall Avast. Avast generally runs well with Win 7; but it has been know to cause crashes on some Win 7 systems. You can try it again once you get your system stable. Download and install Microsoft Security Essentials in it's place.

I also recommend that you uninstall Super Anti Spyware while you are troubleshooting. My suggestion is that, if you wish, when your system is stable, reinstall Avast and run your computer for a week or two. If your system is still stable, then you can try Super Anti Spyware again.

You have a couple of out of date drivers loading on on your system. The one red font is really outdated. Outdated drivers can and do cause memory corruption and BSOD's. Update these drivers.

cpqbttn.sys Mon Apr 20 10:38:52 2009 - HP Tablet PC Key Button HID Driver - HP Quick Launch ButtonsHP® - Laptops, Desktop, Printers, Servers, and more

rimmptsk.sys Thu Jun 25 03:58:09 2009 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com

rimsptsk.sys Thu Jun 25 03:10:46 2009 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com

rixdptsk.sys Thu Jun 25 03:25:57 2009 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com

RTKVHDA.sys Tue Jan 15 06:18:36 2008 - Realtek HD Audio Codec Driver Realtek

I don't think you are going to find updates for the card reader. These may work as they are Vista drivers. You can try leaving them alone and see; but you may have to uninstall the card reader. The Realtek driver definitely needs updating.

Update the Realtek driver, uninstall Avast and Super AntiSpyware and let's see how your system does. If you get another BSOD, upload the dump and we will go from there.

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 = 0x82a07000 PsLoadedModuleList = 0x82b4f810
Debug session time: Tue Nov  2 23:02:38.331 2010 (GMT-4)
System Uptime: 0 days 0:00:09.406
Loading Kernel Symbols
...............................................................
............................
Loading User Symbols
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8e1b2017, 8ab1b41c, 8ab1b000}

Probably caused by : nvlddmkm.sys ( nvlddmkm+1a1017 )

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

1: 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: 8e1b2017, The address that the exception occurred at
Arg3: 8ab1b41c, Exception Record Address
Arg4: 8ab1b000, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nvlddmkm+1a1017
8e1b2017 003b            add     byte ptr [ebx],bh

EXCEPTION_RECORD:  8ab1b41c -- (.exr 0xffffffff8ab1b41c)
ExceptionAddress: 8e1b2017 (nvlddmkm+0x001a1017)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 00000000
Attempt to write to address 00000000

CONTEXT:  8ab1b000 -- (.cxr 0xffffffff8ab1b000)
eax=85720000 ebx=00000000 ecx=00000001 edx=00000020 esi=85720000 edi=00000000
eip=8e1b2017 esp=8ab1b4e4 ebp=8ab1b4fc iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
nvlddmkm+0x1a1017:
8e1b2017 003b            add     byte ptr [ebx],bh          ds:0023:00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  00000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b6f718
Unable to read MiSystemVaType memory at 82b4f160
 00000000 

FOLLOWUP_IP: 
nvlddmkm+1a1017
8e1b2017 003b            add     byte ptr [ebx],bh

BUGCHECK_STR:  0x7E

LOCK_ADDRESS:  82b6cf60 -- (!locks 82b6cf60)

Resource @ nt!PiEngineLock (0x82b6cf60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x82b6cf60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8e1454ee to 8e1b2017

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8ab1b4fc 8e1454ee 8e1466e1 85720000 8ab1b688 nvlddmkm+0x1a1017
8ab1b50c 8e140c0f 858da488 82a2bd28 8e02481d nvlddmkm+0x1344ee
8ab1b688 82baa740 858cb230 8588d000 c000035f nvlddmkm+0x12fc0f
8ab1b86c 82bb1fff 00000000 00000000 8ab1b894 nt!IopLoadDriver+0x7ed
8ab1b918 82bf6ea4 8a9fd358 00000001 8a9fd344 nt!PipCallDriverAddDeviceQueryRoutine+0x34b
8ab1b950 82bff0f8 00000001 8ab1ba1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8ab1b9bc 82baf120 40000000 80000114 8ab1ba38 nt!RtlQueryRegistryValues+0x31d
8ab1ba98 82bae88e 8488d9a8 8ab1bcc8 00000000 nt!PipCallDriverAddDevice+0x383
8ab1bc94 82b92a42 848ce370 857e4db0 8ab1bcc8 nt!PipProcessDevNodeTree+0x15d
8ab1bcd4 82a1af9c 857e4db0 82b6ae80 848d8020 nt!PiProcessStartSystemDevices+0x6d
8ab1bd00 82a74f3b 00000000 00000000 848d8020 nt!PnpDeviceActionWorker+0x241
8ab1bd50 82c156d3 00000001 96f20eba 00000000 nt!ExpWorkerThread+0x10d
8ab1bd90 82ac70f9 82a74e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+1a1017

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c379162

STACK_COMMAND:  .cxr 0xffffffff8ab1b000 ; kb

FAILURE_BUCKET_ID:  0x7E_nvlddmkm+1a1017

BUCKET_ID:  0x7E_nvlddmkm+1a1017

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 0, 8fd57012}

Probably caused by : netw5v32.sys ( netw5v32+13f012 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8fd57012, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82bae718
Unable to read MiSystemVaType memory at 82b8e160
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
netw5v32+13f012
8fd57012 3300            xor     eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 8fd59770 to 8fd57012

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
807e6c50 8fd59770 85fd9528 00000003 867fb328 netw5v32+0x13f012
807e6cdc 8fce5a5a 00000000 00000000 860887b0 netw5v32+0x141770
807e6d00 8fce6d5d 867fb328 860887b0 00000000 netw5v32+0xcda5a
807e6d1c 8fc281e0 867fb328 860887b0 8608afd8 netw5v32+0xced5d
807e6d4c 8fc29075 860887b0 8608aff8 860887b0 netw5v32+0x101e0
807e6d64 8fc25ec9 860887b0 8608afd8 0000000c netw5v32+0x11075
807e6d80 8fce1f9c 85bb0080 00000174 00000000 netw5v32+0xdec9
807e6da8 8fc4d0db 85fd9528 86314004 86684bf4 netw5v32+0xc9f9c
807e6dd8 8fc4e4c4 86314004 00000000 807e6e24 netw5v32+0x350db
807e6de8 8fc4a2ca 865f3848 86314004 00000000 netw5v32+0x364c4
807e6e24 8fc4a51e 85bb8e68 85bb6238 86314000 netw5v32+0x322ca
807e6e88 8fc4491f 0000000d 85bb6238 000000ff netw5v32+0x3251e
807e6ec4 8fc421dc 85bb6001 85bb6238 807e6ee0 netw5v32+0x2c91f
807e6ed4 8fea2785 85bb6238 807e6f20 88c6f301 netw5v32+0x2a1dc
807e6ee0 88c6f301 85b48848 00000000 00000000 netw5v32+0x28a785
807e6f20 88c1a9f4 86711f84 00711e70 00000000 ndis!ndisMiniportDpc+0xda
807e6f48 82aae3b5 86711f84 86711e70 00000000 ndis!ndisInterruptDpc+0xaf
807e6fa4 82aae218 807c6120 848da798 00000000 nt!KiExecuteAllDpcs+0xf9
807e6ff4 82aad9dc 8ab272f4 00000000 00000000 nt!KiRetireDpcList+0xd5
807e6ff8 8ab272f4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82aad9dc 00000000 0000001a 00d6850f bb830000 0x8ab272f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netw5v32+13f012
8fd57012 3300            xor     eax,dword ptr [eax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  netw5v32+13f012

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netw5v32

IMAGE_NAME:  netw5v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df4ff

FAILURE_BUCKET_ID:  0xD1_netw5v32+13f012

BUCKET_ID:  0xD1_netw5v32+13f012

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 8e0dc017, 9aacfac8, 0}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+c2017 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c000001d, The exception code that was not handled
Arg2: 8e0dc017, The address that the exception occurred at
Arg3: 9aacfac8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nvlddmkm+c2017
8e0dc017 8c39            mov     word ptr [ecx],st(-1)

TRAP_FRAME:  9aacfac8 -- (.trap 0xffffffff9aacfac8)
ErrCode = 00000000
eax=87403b9d ebx=00000000 ecx=00000000 edx=00000000 esi=85a18081 edi=8700a000
eip=8e0dc017 esp=9aacfb3c ebp=9aacfbcc iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nvlddmkm+0xc2017:
8e0dc017 8c39            mov     word ptr [ecx],st(-1) ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  WLIDSVCM.EXE

CURRENT_IRQL:  4

LAST_CONTROL_TRANSFER:  from 8e0dd65e to 8e0dc017

FAILED_INSTRUCTION_ADDRESS: 
nvlddmkm+c2017
8e0dc017 8c39            mov     word ptr [ecx],st(-1)

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
9aacfbcc 8e0dd65e 8700a000 00000000 00000000 nvlddmkm+0xc2017
9aacfbe4 8e09bfa2 000000d8 00000000 00000000 nvlddmkm+0xc365e
9aacfc34 8e09c22c 8ea4e698 8599c000 00000000 nvlddmkm+0x81fa2
9aacfc60 8ea9b8ec 8e02d274 00000000 9aacfc84 nvlddmkm+0x8222c
9aacfc70 8eaacc72 86bfa000 857ea020 00000000 dxgkrnl+0x18ec
9aacfc84 82a7855c 86bfa000 857ea020 000001be dxgkrnl+0x12c72
9aacfcb0 82a784a9 0014ec00 00000051 9aacfd34 nt!KiChainedDispatch2ndLvl+0x60
9aacfcb0 82a7c3b1 0014ec00 00000051 9aacfd34 nt!KiChainedDispatch+0x29
9aacfd34 779964f4 badb0d00 0014ee78 00000000 nt!KiFastCallEntry+0x91
9aacfd38 badb0d00 0014ee78 00000000 00000000 0x779964f4
9aacfd3c 0014ee78 00000000 00000000 00000000 0xbadb0d00
9aacfd40 00000000 00000000 00000000 00000000 0x14ee78


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+c2017
8e0dc017 8c39            mov     word ptr [ecx],st(-1)

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+c2017

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c379162

FAILURE_BUCKET_ID:  0x8E_BAD_IP_nvlddmkm+c2017

BUCKET_ID:  0x8E_BAD_IP_nvlddmkm+c2017

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 8e0dc017, 9aacfac8, 0}

*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+c2017 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c000001d, The exception code that was not handled
Arg2: 8e0dc017, The address that the exception occurred at
Arg3: 9aacfac8, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nvlddmkm+c2017
8e0dc017 8c39            mov     word ptr [ecx],st(-1)

TRAP_FRAME:  9aacfac8 -- (.trap 0xffffffff9aacfac8)
ErrCode = 00000000
eax=87403b9d ebx=00000000 ecx=00000000 edx=00000000 esi=85a18081 edi=8700a000
eip=8e0dc017 esp=9aacfb3c ebp=9aacfbcc iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nvlddmkm+0xc2017:
8e0dc017 8c39            mov     word ptr [ecx],st(-1) ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  WLIDSVCM.EXE

CURRENT_IRQL:  4

LAST_CONTROL_TRANSFER:  from 8e0dd65e to 8e0dc017

FAILED_INSTRUCTION_ADDRESS: 
nvlddmkm+c2017
8e0dc017 8c39            mov     word ptr [ecx],st(-1)

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
9aacfbcc 8e0dd65e 8700a000 00000000 00000000 nvlddmkm+0xc2017
9aacfbe4 8e09bfa2 000000d8 00000000 00000000 nvlddmkm+0xc365e
9aacfc34 8e09c22c 8ea4e698 8599c000 00000000 nvlddmkm+0x81fa2
9aacfc60 8ea9b8ec 8e02d274 00000000 9aacfc84 nvlddmkm+0x8222c
9aacfc70 8eaacc72 86bfa000 857ea020 00000000 dxgkrnl+0x18ec
9aacfc84 82a7855c 86bfa000 857ea020 000001be dxgkrnl+0x12c72
9aacfcb0 82a784a9 0014ec00 00000051 9aacfd34 nt!KiChainedDispatch2ndLvl+0x60
9aacfcb0 82a7c3b1 0014ec00 00000051 9aacfd34 nt!KiChainedDispatch+0x29
9aacfd34 779964f4 badb0d00 0014ee78 00000000 nt!KiFastCallEntry+0x91
9aacfd38 badb0d00 0014ee78 00000000 00000000 0x779964f4
9aacfd3c 0014ee78 00000000 00000000 00000000 0xbadb0d00
9aacfd40 00000000 00000000 00000000 00000000 0x14ee78


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+c2017
8e0dc017 8c39            mov     word ptr [ecx],st(-1)

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+c2017

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c379162

FAILURE_BUCKET_ID:  0x8E_BAD_IP_nvlddmkm+c2017

BUCKET_ID:  0x8E_BAD_IP_nvlddmkm+c2017

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

 

[crucifixio]

Thanks again for the help. Will try this tomorrow and let you know how it goes.

 

[CarlTR6]

Yo are welcome. Looking forward to your reporting back with good news.

 

[crucifixio]

So I tried to remove RTKVHDA.sys Tue Jan 15 06:18:36 2008 - Realtek HD Audio Codec Driver Realtek

but it still self-installs (even after I install the latest one from Realtek).

I uninstalled Avast and Super Antispyware.

Here's the latest dump

 

[CarlTR6]

Install the latest update again. Do a search of your C: drive for RTKVHDA.sys. Make sure you have an updated version, that is, one with a date later than Jan 15, 2008. Next -

To remove any left over driver remnants, use driver sweeper Guru3D - Driver Sweeper. After you run Driver Sweeper , verify that there are no instances of the the 2008 driver lurking about by doing another search of C: drive. If you find a copy of the 2008 version, rename it from .sys to .bak.


Your latest dumps indicate memory corruption. Unfortunately, they blame Windows system drivers, which are highly unlikely to be the real cause. I see these out of date drivers loaded on your system; of source, you know about RTKVHDA.sys. I suggest you work on getting it updated and then run your system and see what happens before bothering with the 2009 drivers shown below. If you get another BSOD after updating the RTKVHDA.sys driver, uninstall your card reader.

cpqbttn.sys Mon Apr 20 10:38:52 2009 - HP Tablet PC Key Button HID Driver - HP Quick Launch ButtonsHP® - Laptops, Desktop, Printers, Servers, and more

rimmptsk.sys Thu Jun 25 03:58:09 2009 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com

rimsptsk.sys Thu Jun 25 03:10:46 2009 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com

rixdptsk.sys Thu Jun 25 03:25:57 2009 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com

RTKVHDA.sys Tue Jan 15 06:18:36 2008 - Realtek HD Audio Codec Driver Realtek

What firewall are you running?

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 = 0x82a40000 PsLoadedModuleList = 0x82b88810
Debug session time: Wed Nov 10 20:33:59.045 2010 (GMT-5)
System Uptime: 0 days 0:00:12.121
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Unable to load image netw5v32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v32.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v32.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8f23de85, 8ab2335c, 8ab22f40}

Probably caused by : netw5v32.sys ( netw5v32+11e85 )

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

1: 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: 8f23de85, The address that the exception occurred at
Arg3: 8ab2335c, Exception Record Address
Arg4: 8ab22f40, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
netw5v32+11e85
8f23de85 8b5104          mov     edx,dword ptr [ecx+4]

EXCEPTION_RECORD:  8ab2335c -- (.exr 0xffffffff8ab2335c)
ExceptionAddress: 8f23de85 (netw5v32+0x00011e85)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000085
Attempt to read from address 00000085

CONTEXT:  8ab22f40 -- (.cxr 0xffffffff8ab22f40)
eax=8f2a2114 ebx=00000000 ecx=00000081 edx=00000181 esi=00000181 edi=865ffb28
eip=8f23de85 esp=8ab23424 ebp=8ab23430 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210206
netw5v32+0x11e85:
8f23de85 8b5104          mov     edx,dword ptr [ecx+4] ds:0023:00000085=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000085

READ_ADDRESS: GetPointerFromAddress: unable to read from 82ba8718
Unable to read MiSystemVaType memory at 82b88160
 00000085 

FOLLOWUP_IP: 
netw5v32+11e85
8f23de85 8b5104          mov     edx,dword ptr [ecx+4]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LOCK_ADDRESS:  82ba5f60 -- (!locks 82ba5f60)

Resource @ nt!PiEngineLock (0x82ba5f60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x82ba5f60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8f239c3d to 8f23de85

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8ab23430 8f239c3d 865ffb28 00000181 00000004 netw5v32+0x11e85
8ab23448 8f28f027 867e0828 00000181 00000004 netw5v32+0xdc3d
8ab23480 8f23c1e0 866b6c10 860cbae0 860cdfe0 netw5v32+0x63027
8ab234b0 8f23d075 860cbae0 00000000 860cbae0 netw5v32+0x101e0
8ab234c8 8f239ec9 860cbae0 860cdfe0 00000000 netw5v32+0x11075
8ab234e4 8f268a51 85bfc280 00000004 00000001 netw5v32+0xdec9
8ab235b4 8f22dbc9 85bd0eb0 85bc97a8 85bc9d34 netw5v32+0x3ca51
8ab235e8 8f4b9593 00000000 85bc9d34 00000003 netw5v32+0x1bc9
8ab23618 88c84368 858820e0 8f85e990 8ab23670 netw5v32+0x28d593
8ab238e4 88c83aea 8587b240 858820e0 85829790 ndis!ndisMInitializeAdapter+0x76b
8ab2391c 88c83963 8587b240 85882028 8586a2e8 ndis!ndisInitializeAdapter+0x10a
8ab23944 88c80247 85882028 8595d490 8595d4b4 ndis!ndisPnPStartDevice+0x130
8ab23988 82a7c4bc 85882028 8595d3d8 8ab23a10 ndis!ndisPnPDispatch+0x62f
8ab239a0 82be8d78 00000000 848a3568 85b80408 nt!IofCallDriver+0x63
8ab239bc 82a54479 8ab239ec 82a53b67 85b80408 nt!PnpAsynchronousCall+0x92
8ab23a20 82beebf4 82a53b67 85b80408 848aa880 nt!PnpStartDevice+0xe1
8ab23a7c 82beeabd 85b80408 0000003e 00000000 nt!PnpStartDeviceNode+0x12c
8ab23a98 82be78b9 00000000 00000001 00000000 nt!PipProcessStartPhase1+0x62
8ab23c94 82bcba42 848ee370 8592e448 8ab23cc8 nt!PipProcessDevNodeTree+0x188
8ab23cd4 82a53f9c 8592e448 82ba3e80 848f8a70 nt!PiProcessStartSystemDevices+0x6d
8ab23d00 82aadf3b 00000000 00000000 848f8a70 nt!PnpDeviceActionWorker+0x241
8ab23d50 82c4e6d3 00000001 96817514 00000000 nt!ExpWorkerThread+0x10d
8ab23d90 82b000f9 82aade2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  netw5v32+11e85

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netw5v32

IMAGE_NAME:  netw5v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df4ff

STACK_COMMAND:  .cxr 0xffffffff8ab22f40 ; kb

FAILURE_BUCKET_ID:  0x7E_netw5v32+11e85

BUCKET_ID:  0x7E_netw5v32+11e85

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

Debug session time: Wed Nov 10 20:03:37.487 2010 (GMT-5)
System Uptime: 0 days 0:00:48.562
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {4ffd74, 1, 82abae03, 8}


Could not read faulting driver name
Probably caused by : ntkrpamp.exe ( nt!NtWaitForWorkViaWorkerFactory+29e )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 004ffd74, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 82abae03, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000008, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82bb1718
Unable to read MiSystemVaType memory at 82b91160
 004ffd74 

FAULTING_IP: 
nt!NtWaitForWorkViaWorkerFactory+29e
82abae03 a5              movs    dword ptr es:[edi],dword ptr [esi]

MM_INTERNAL_CODE:  8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  lsm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82a8c44a to 82abae03

STACK_TEXT:  
8d1c5d24 82a8c44a 00000000 004ffd74 004ffe20 nt!NtWaitForWorkViaWorkerFactory+0x29e
8d1c5d24 777b64f4 00000000 004ffd74 004ffe20 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
004ffe20 00000000 00000000 00000000 00000000 0x777b64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!NtWaitForWorkViaWorkerFactory+29e
82abae03 a5              movs    dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!NtWaitForWorkViaWorkerFactory+29e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

FAILURE_BUCKET_ID:  0x50_nt!NtWaitForWorkViaWorkerFactory+29e

BUCKET_ID:  0x50_nt!NtWaitForWorkViaWorkerFactory+29e

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

System Uptime: 0 days 0:00:48.640
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

Probably caused by : memory_corruption

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 00000000 to 8b56ec92

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffff94ea5cdc

STACK_COMMAND:  dds 94EA5CDC-0x20 ; kb

STACK_TEXT:  
94ea5cbc  94ea5ccc
94ea5cc0  82a514ae nt!IofCallDriver+0x55
94ea5cc4  85927e00
94ea5cc8  86db1098
94ea5ccc  94ea5cd4
94ea5cd0  82a23049 nt!IoCallDriver+0x10
94ea5cd4  94ea5cf8
94ea5cd8  822a9b48 portcls!DispatchPower+0x2e2
94ea5cdc  86db1098
94ea5ce0  85927d50
94ea5ce4  85cd1638
94ea5ce8  82b55f40 nt!PopIrpWorkerMutex
94ea5cec  85927d50
94ea5cf0  00000004
94ea5cf4  1c3d737c
94ea5cf8  94ea5d50
94ea5cfc  82a20823 nt!PopIrpWorker+0x351
94ea5d00  86bac5f0
94ea5d04  85cd16f0
94ea5d08  00000000
94ea5d0c  87508ab8
94ea5d10  00000000
94ea5d14  00000000
94ea5d18  00000030
94ea5d1c  94ea5d20
94ea5d20  fa0a1f00
94ea5d24  ffffffff
94ea5d28  848ef008
94ea5d2c  00000000
94ea5d30  82b56488 nt!PopIrpLock
94ea5d34  00000000
94ea5d38  94e9dd38


CHKIMG_EXTENSION: !chkimg -lo 50 -d !portcls
    82294013 - portcls!DevicePowerIrpCompletionRoutine+6d
    [ d2:00 ]
1 error : !portcls (82294013)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BYTE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BYTE

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

1: kd> lmtsmn
start    end        module name
948c4000 948f0000   1394ohci 1394ohci.sys Mon Jul 13 19:51:59 2009 (4A5BC89F)
888bc000 88904000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
8d8f3000 8d94d000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
8cd61000 8cd73000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
8882d000 88836000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
889f4000 889fd000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
88800000 88823000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
88963000 8896e000   BATTC    BATTC.SYS    Mon Jul 13 19:19:15 2009 (4A5BC0F3)
8d85f000 8d866000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
8cd13000 8cd21000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
8869e000 886a6000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
98492000 984ab000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
8d0c3000 8d0d0000   BthEnum  BthEnum.sys  Mon Jul 13 19:51:35 2009 (4A5BC887)
8d0d0000 8d0eb000   bthpan   bthpan.sys   Mon Jul 13 19:51:43 2009 (4A5BC88F)
8d03b000 8d09f000   bthport  bthport.sys  Mon Jul 13 19:51:30 2009 (4A5BC882)
88ddf000 88df1000   BTHUSB   BTHUSB.sys   Mon Jul 13 19:51:36 2009 (4A5BC888)
8cc18000 8cc21880   btusbflt btusbflt.sys Thu Apr 08 21:11:21 2010 (4BBE7EB9)
95b50000 95b6e000   cdd      cdd.dll      Mon Jul 13 21:04:18 2009 (4A5BD992)
887d8000 887f7000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
886e8000 88793000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
88d8b000 88db0000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
886a6000 886e8000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
8cd42000 8cd45700   CmBatt   CmBatt.sys   Mon Jul 13 19:19:18 2009 (4A5BC0F6)
88b81000 88bde000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
8895b000 88963000   compbatt compbatt.sys Mon Jul 13 19:19:18 2009 (4A5BC0F6)
9420d000 9421a000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
94980000 94982480   cpqbttn  cpqbttn.sys  Mon Apr 20 10:38:52 2009 (49EC88FC)
8220a000 82217000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
8ccaf000 8cd13000   csc      csc.sys      Mon Jul 13 19:15:08 2009 (4A5BBFFC)
8cc9b000 8ccaf000   ctxusbm  ctxusbm.sys  Mon Sep 07 13:59:10 2009 (4AA549EE)
8cc83000 8cc9b000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
8cc77000 8cc83000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
88e00000 88e11000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
822be000 822d7000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
8d9d6000 8d9e7000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
82222000 8222c000   dump_msahci dump_msahci.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
82217000 82222000   dump_pciidex dump_pciidex.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
82200000 8220a000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
93eb5000 93f6c000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 20:48:33 2009 (4AC54DE1)
93f6c000 93fa5000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:25:25 2009 (4A5BC265)
887c7000 887d8000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
88793000 887c7000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
88bec000 88bf5000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
88d59000 88d8b000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
88f63000 88f94000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
82e25000 82e5c000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
9340f000 9342e000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
94983000 94996000   HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865)
94996000 9499c480   HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863)
9840d000 98492000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
88ff4000 88ffc000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
9499d000 949b5000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
889c9000 889d0000   intelide intelide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17)
8cd4f000 8cd61000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
949b5000 949c2000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
82272000 8227e000   kbdhid   kbdhid.sys   Mon Jul 13 19:45:09 2009 (4A5BC705)
80bcc000 80bd4000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
8d800000 8d834000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
88b6e000 88b81000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
88d07000 88d2c000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
8d120000 8d130000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
8d0eb000 8d106000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
88615000 8868d000   mcupdate mcupdate.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
823e3000 823f0000   modem    modem.sys    Mon Jul 13 19:55:24 2009 (4A5BC96C)
823f0000 823fa000   MODEMCSA MODEMCSA.sys Mon Jul 13 19:55:25 2009 (4A5BC96D)
88dd4000 88ddf000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
94200000 9420d000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
889de000 889f4000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
8d835000 8d858000   MpFilter MpFilter.sys Sat Mar 20 00:03:26 2010 (4BA4490E)
984ab000 984bd000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
984bd000 984e0000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
984e0000 9851b000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
9851b000 98536000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
88823000 8882d000   msahci   msahci.sys   Mon Jul 13 19:45:50 2009 (4A5BC72E)
8d8b8000 8d8c3000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
8890d000 88915000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
88b43000 88b6e000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
8cc6d000 8cc77000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
88fe4000 88ff4000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
88c12000 88cc9000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
8cd8b000 8cd96000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
8d176000 8d186000   ndisuio  ndisuio.sys  Mon Jul 13 19:53:51 2009 (4A5BC90F)
8cd96000 8cdb8000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
8227e000 8228f000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
8d9a5000 8d9b3000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
8d94d000 8d97f000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
88cc9000 88d07000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
94223000 9487f000   netw5v32 netw5v32.sys Wed Jan 13 11:29:51 2010 (4B4DF4FF)
8d8c3000 8d8d1000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
8cc63000 8cc6d000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
82a15000 82e25000   nt       ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC)
88a14000 88b43000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
8d858000 8d85f000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
93eb3000 93eb4040   nvBridge nvBridge.kmd Fri Jul 09 17:10:11 2010 (4C379033)
93435000 93eb2dc0   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:14 2010 (4C379162)
8d130000 8d176000   nwifi    nwifi.sys    Mon Jul 13 19:51:59 2009 (4A5BC89F)
8d986000 8d9a5000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
8894a000 8895b000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
88915000 8893f000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
889d0000 889de000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
88bde000 88bec000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
9854e000 985e5000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
8228f000 822be000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
8868d000 8869e000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
8cd73000 8cd8b000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
8cdb8000 8cdd0000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
8cdd0000 8cde7000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
8cde7000 8cdfe000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
8cc22000 8cc63000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
8cc00000 8cc0a000   rdpbus   rdpbus.sys   Mon Jul 13 20:02:40 2009 (4A5BCB20)
8d8a0000 8d8a8000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8d8a8000 8d8b0000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
8d8b0000 8d8b8000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
88d2c000 88d59000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
8d09f000 8d0c3000   rfcomm   rfcomm.sys   Mon Jul 13 19:51:41 2009 (4A5BC88D)
94909000 9491a000   rimmptsk rimmptsk.sys Thu Jun 25 03:58:09 2009 (4A432E11)
9491a000 9492e000   rimsptsk rimsptsk.sys Thu Jun 25 03:10:46 2009 (4A4322F6)
9492e000 94980000   rixdptsk rixdptsk.sys Thu Jun 25 03:25:57 2009 (4A432685)
8d186000 8d199000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
9487f000 948c4000   Rt86win7 Rt86win7.sys Wed Jun 23 05:10:23 2010 (4C21CF7F)
82405000 825f7940   RTKVHDA  RTKVHDA.sys  Tue Jan 15 06:18:36 2008 (478C968C)
948f0000 94909000   sdbus    sdbus.sys    Fri Oct 09 22:31:24 2009 (4ACFF1FC)
985e5000 985ef000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
822d7000 823e2900   smserial smserial.sys Mon Oct 26 11:08:57 2009 (4AE5BB89)
88fdc000 88fe4000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
98e84000 98ed5000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
98e35000 98e84000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
8d199000 8d1ba000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
9421a000 9421b380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
949c2000 949fc680   SynTP    SynTP.sys    Thu May 27 17:40:25 2010 (4BFEE6C9)
88e1a000 88f63000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
985ef000 985fc000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
8d8e8000 8d8f3000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
8d8d1000 8d8e8000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
8d9c6000 8d9d6000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
95b20000 95b29000   TSDDD    TSDDD.dll    Mon Jul 13 20:01:40 2009 (4A5BCAE4)
8cd21000 8cd42000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
8cc0a000 8cc18000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
8d9e7000 8d9fe000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883)
949fd000 949fe700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
93400000 9340f000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
8222e000 82272000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
93fb0000 93ffb000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
93fa5000 93fb0000   usbuhci  usbuhci.sys  Mon Jul 13 19:51:10 2009 (4A5BC86E)
88db0000 88dd3b80   usbvideo usbvideo.sys Wed Mar 03 23:04:40 2010 (4B8F3158)
8893f000 8894a000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
8d866000 8d872000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
8d872000 8d893000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
88f94000 88f9c380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
8896e000 8897e000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8897e000 889c9000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
88f9d000 88fdc000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
8d9b3000 8d9c6000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
8d893000 8d8a0000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
8883d000 888ae000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
888ae000 888bc000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
8d97f000 8d986000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
958c0000 95b0b000   win32k   win32k.sys   Tue Aug 31 22:34:29 2010 (4C7DBBB5)
8cd46000 8cd4f000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:19:16 2009 (4A5BC0F4)
88904000 8890d000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
8d106000 8d120000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)

Unloaded modules:
98536000 9854e000   parport.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
88db0000 88dbd000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
88dbd000 88dc8000   dump_pciidex
    Timestamp: unavailable (00000000)
    Checksum:  00000000
88dc8000 88dd2000   dump_msahci.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
88dd2000 88de3000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000