Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD: HP Pavilion dv6500 Notebook PC


01 Nov 2010   #1

Windows 7 32 bit Professional
 
 
BSOD: HP Pavilion dv6500 Notebook PC

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!

My System SpecsSystem Spec
.

01 Nov 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by crucifixio View Post
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.
My System SpecsSystem Spec
01 Nov 2010   #3

Windows 7 Ultimate 32 bit
 
 

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,
My System SpecsSystem Spec
.


01 Nov 2010   #4

Windows 7 32 bit Professional
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by crucifixio View Post
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.
My System SpecsSystem Spec
01 Nov 2010   #5

Windows 7 Ultimate 32 bit
 
 

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...en-forums.html
My System SpecsSystem Spec
04 Nov 2010   #6

Windows 7 32 bit Professional
 
 
Minidump Files

Hi all,

Here are the minidump files.

Thanks for all the help.
My System SpecsSystem Spec
04 Nov 2010   #7

Windows 7 Ultimate 32 bit
 
 

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.
Quote:
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.
Code:
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
---------
My System SpecsSystem Spec
05 Nov 2010   #8

Windows 7 32 bit Professional
 
 

Thanks again for the help. Will try this tomorrow and let you know how it goes.
My System SpecsSystem Spec
05 Nov 2010   #9

Windows 7 Ultimate 32 bit
 
 

Yo are welcome. Looking forward to your reporting back with good news.
My System SpecsSystem Spec
12 Nov 2010   #10

Windows 7 32 bit Professional
 
 

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
My System SpecsSystem Spec
Reply

 BSOD: HP Pavilion dv6500 Notebook PC




Thread Tools



Similar help and support threads for2: BSOD: HP Pavilion dv6500 Notebook PC
Thread Forum
BSOD ntoskrnl.exe error with HP Pavilion g6 Notebook PC BSOD Help and Support
Solved (BSOD)HP pavilion g6 notebook PC BSOD Help and Support
Solved Printer not functioning correctly on new HP Pavilion g7 Notebook. Hardware & Devices
Win7x64 Home Premium on an HP Pavilion DV7-4177nr notebook General Discussion
Teamviewer does not run with my Hp pavilion g7-1167dx Notebook Software
HP Pavilion tx1120us Notebook PC Hardware & Devices
BSoD Notebook HP Pavilion dv7 1130ew BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 05:49 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33