Sign in with
Sign up | Sign in
Your question

Random BSOD Wmiacpi.sys error

Last response: in Windows XP
Share
June 28, 2009 3:14:53 PM

Ok I hope somebody can help me out. I have the Pavilion dv9005US laptop which has been giving me BSOD screens quite randomly lately. It seems to always happen when I am on the internet (usually when I am using a usb device as well) where the thing will completely lock up and will then crash. When I ran "verifier" it located "wmiacpi.sys" as the culprit with the error (Error 20e wmiacpi.sys+152f at B9C5752f). I dumped a file and from there I am completely lost. I see what is causing the problem but I am stuck as to where to begin to fix it. This was the memory dump below:

------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini062809-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jun 28 07:34:10.515 2009 (GMT-4)
System Uptime: 0 days 0:01:22.207
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
..........
*** WARNING: Unable to verify timestamp for wmiacpi.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {20e, ba92e52f, 86866f48, 0}

*** WARNING: Unable to verify timestamp for WMILIB.SYS
*** ERROR: Module load completed but symbols could not be loaded for WMILIB.SYS
Probably caused by : wmiacpi.sys ( wmiacpi!WmiAcpiFunctionControl+4f )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000020e, A PNP IRP has an invalid status. Any PNP IRP must have its status initialized
to STATUS_NOT_SUPPORTED.
Arg2: ba92e52f, The address in the driver's code where the error was detected.
Arg3: 86866f48, IRP address.
Arg4: 00000000

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


BUGCHECK_STR: 0xc9_20e

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 20e

FAULTING_IP:
wmiacpi!WmiAcpiFunctionControl+4f
ba92e52f 8bd8 mov ebx,eax

FOLLOWUP_IP:
wmiacpi!WmiAcpiFunctionControl+4f
ba92e52f 8bd8 mov ebx,eax

IRP_ADDRESS: 86866f48

DEVICE_OBJECT: 00000000

CUSTOMER_CRASH_COUNT: 8

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: wmiprvse.exe

LAST_CONTROL_TRANSFER: from ba92e52f to 804f9f43

STACK_TEXT:
a3f05710 ba92e52f 86866f48 85e60d78 86866fdc nt!_woutput+0x414
a3f05740 ba92e52f 85057e60 86866f48 85a509a8 wmiacpi!WmiAcpiFunctionControl+0x4f
a3f05764 ba92e52f 85e60d78 806e6428 85e60d00 wmiacpi!WmiAcpiFunctionControl+0x4f
a3f05790 ba92e52f 00000000 85e60d01 86866fdc wmiacpi!WmiAcpiFunctionControl+0x4f
a3f057b4 80658116 00a509a8 85e60e64 86866f48 wmiacpi!WmiAcpiFunctionControl+0x4f
a3f057dc ba92d836 86598fc4 85e60e30 00000000 nt!HvRefreshHive+0x4be
a3f057f4 ba92e52f 85e60e30 8604f3f8 ba92e4e0 wmiacpi!WmiAcpiGetAcpiInterfaces+0x8e
a3f05810 f79899a3 85e60d78 867fee48 00000001 wmiacpi!WmiAcpiFunctionControl+0x4f
WARNING: Stack unwind information not available. Following frames may be wrong.
a3f05880 ba92dfae 00000001 85e60d78 867fee48 WMILIB+0x9a3
a3f058a4 804ef19f 00000000 867fee48 806e6428 wmiacpi!WmiAcpiSystemControlDispatch+0x20
a3f058d8 80604ad0 a3f05958 867fee48 a3f05a9c nt!MiFlushSectionInternal+0x256
a3f05904 80604b99 867fee48 c3086804 85e60d03 nt!WmipQueryLogger+0x261
a3f05930 8060209e c3086804 85e60d78 a3f05ab4 nt!WmipQueryLogger+0x31d
a3f05960 806022ac c3086804 e1818a2c a3f05a9c nt!SepAccessCheckAndAuditAlarm+0x73b
a3f05ae0 806023ed c3086804 e184346c 00000001 nt!NtOpenObjectAuditAlarm+0x33b
a3f05b0c 8060263c e184346c 00000004 e1843400 nt!NtCloseObjectAuditAlarm+0xf8
a3f05b3c 8060647e e1843400 00224140 85cd5528 nt!SeObjectReferenceAuditAlarm+0x59
a3f05b64 806054eb 00224140 00000001 00000000 nt!WmipQueryWmiDataBlock+0x46
a3f05c1c 804ef19f 86013d48 87022e70 806e6428 nt!WmipTranslateFileHandle+0x1be
a3f05c50 8057f982 87022fdc 850e5898 87022e70 nt!MiFlushSectionInternal+0x256
a3f05c64 805807f7 86013d48 87022e70 850e5898 nt!ObQueryNameString+0x5ab
a3f05d00 80579274 0000020c 00000210 00000000 nt!NtSetInformationThread+0x125
a3f05d34 8054162c 0000020c 00000210 00000000 nt!SepOpenTokenOfThread+0x87
a3f05d64 7c90e514 badb0d00 00c6f0e8 00000000 nt!RtlIpv4StringToAddressExW+0xad
a3f05d78 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: wmiacpi!WmiAcpiFunctionControl+4f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wmiacpi

IMAGE_NAME: wmiacpi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 480252b5

FAILURE_BUCKET_ID: 0xc9_20e_wmiacpi!WmiAcpiFunctionControl+4f

BUCKET_ID: 0xc9_20e_wmiacpi!WmiAcpiFunctionControl+4f

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

0: kd> lmvm wmiacpi
start end module name
ba92d000 ba92f280 wmiacpi M (pdb symbols) c:\windows\symbols\sys\wmiacpi.pdb
Loaded symbol image file: wmiacpi.sys
Image path: wmiacpi.sys
Image name: wmiacpi.sys
Timestamp: Sun Apr 13 14:36:37 2008 (480252B5)
CheckSum: 00010888
ImageSize: 00002280
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !devobj 0 f
Device object 0 f not found
June 29, 2009 4:48:26 PM

Hello There,

After take look you have Error wmiacpsi.sys = 152f at B9BAB852F

That file help manage the ACPI settings in your system.

here more information:

The name of the file is Wmiacpi.sys and it is a .sys file. The file size in total is 10.752 bytes. The latest file version for Wmiacpi.sys is 5.2.3790.0 (srv03_rtm.030324-2048). The company/persons responsible for Wmiacpi.sys are: Microsoft Corporation. The company owners have attached the following description for the file: Windows Management Interface for ACPI.

Best Way to Fix that This use Registry Cleaner, Try any Registry Cleaner That Works for you, find one that find and detect the error and fix this.




xpcustom said:
Ok I hope somebody can help me out. I have the Pavilion dv9005US laptop which has been giving me BSOD screens quite randomly lately. It seems to always happen when I am on the internet (usually when I am using a usb device as well) where the thing will completely lock up and will then crash. When I ran "verifier" it located "wmiacpi.sys" as the culprit with the error (Error 20e wmiacpi.sys+152f at B9C5752f). I dumped a file and from there I am completely lost. I see what is causing the problem but I am stuck as to where to begin to fix it. This was the memory dump below:

------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini062809-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jun 28 07:34:10.515 2009 (GMT-4)
System Uptime: 0 days 0:01:22.207
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
..........
*** WARNING: Unable to verify timestamp for wmiacpi.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {20e, ba92e52f, 86866f48, 0}

*** WARNING: Unable to verify timestamp for WMILIB.SYS
*** ERROR: Module load completed but symbols could not be loaded for WMILIB.SYS
Probably caused by : wmiacpi.sys ( wmiacpi!WmiAcpiFunctionControl+4f )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000020e, A PNP IRP has an invalid status. Any PNP IRP must have its status initialized
to STATUS_NOT_SUPPORTED.
Arg2: ba92e52f, The address in the driver's code where the error was detected.
Arg3: 86866f48, IRP address.
Arg4: 00000000

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


BUGCHECK_STR: 0xc9_20e

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 20e

FAULTING_IP:
wmiacpi!WmiAcpiFunctionControl+4f
ba92e52f 8bd8 mov ebx,eax

FOLLOWUP_IP:
wmiacpi!WmiAcpiFunctionControl+4f
ba92e52f 8bd8 mov ebx,eax

IRP_ADDRESS: 86866f48

DEVICE_OBJECT: 00000000

CUSTOMER_CRASH_COUNT: 8

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: wmiprvse.exe

LAST_CONTROL_TRANSFER: from ba92e52f to 804f9f43

STACK_TEXT:
a3f05710 ba92e52f 86866f48 85e60d78 86866fdc nt!_woutput+0x414
a3f05740 ba92e52f 85057e60 86866f48 85a509a8 wmiacpi!WmiAcpiFunctionControl+0x4f
a3f05764 ba92e52f 85e60d78 806e6428 85e60d00 wmiacpi!WmiAcpiFunctionControl+0x4f
a3f05790 ba92e52f 00000000 85e60d01 86866fdc wmiacpi!WmiAcpiFunctionControl+0x4f
a3f057b4 80658116 00a509a8 85e60e64 86866f48 wmiacpi!WmiAcpiFunctionControl+0x4f
a3f057dc ba92d836 86598fc4 85e60e30 00000000 nt!HvRefreshHive+0x4be
a3f057f4 ba92e52f 85e60e30 8604f3f8 ba92e4e0 wmiacpi!WmiAcpiGetAcpiInterfaces+0x8e
a3f05810 f79899a3 85e60d78 867fee48 00000001 wmiacpi!WmiAcpiFunctionControl+0x4f
WARNING: Stack unwind information not available. Following frames may be wrong.
a3f05880 ba92dfae 00000001 85e60d78 867fee48 WMILIB+0x9a3
a3f058a4 804ef19f 00000000 867fee48 806e6428 wmiacpi!WmiAcpiSystemControlDispatch+0x20
a3f058d8 80604ad0 a3f05958 867fee48 a3f05a9c nt!MiFlushSectionInternal+0x256
a3f05904 80604b99 867fee48 c3086804 85e60d03 nt!WmipQueryLogger+0x261
a3f05930 8060209e c3086804 85e60d78 a3f05ab4 nt!WmipQueryLogger+0x31d
a3f05960 806022ac c3086804 e1818a2c a3f05a9c nt!SepAccessCheckAndAuditAlarm+0x73b
a3f05ae0 806023ed c3086804 e184346c 00000001 nt!NtOpenObjectAuditAlarm+0x33b
a3f05b0c 8060263c e184346c 00000004 e1843400 nt!NtCloseObjectAuditAlarm+0xf8
a3f05b3c 8060647e e1843400 00224140 85cd5528 nt!SeObjectReferenceAuditAlarm+0x59
a3f05b64 806054eb 00224140 00000001 00000000 nt!WmipQueryWmiDataBlock+0x46
a3f05c1c 804ef19f 86013d48 87022e70 806e6428 nt!WmipTranslateFileHandle+0x1be
a3f05c50 8057f982 87022fdc 850e5898 87022e70 nt!MiFlushSectionInternal+0x256
a3f05c64 805807f7 86013d48 87022e70 850e5898 nt!ObQueryNameString+0x5ab
a3f05d00 80579274 0000020c 00000210 00000000 nt!NtSetInformationThread+0x125
a3f05d34 8054162c 0000020c 00000210 00000000 nt!SepOpenTokenOfThread+0x87
a3f05d64 7c90e514 badb0d00 00c6f0e8 00000000 nt!RtlIpv4StringToAddressExW+0xad
a3f05d78 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: wmiacpi!WmiAcpiFunctionControl+4f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wmiacpi

IMAGE_NAME: wmiacpi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 480252b5

FAILURE_BUCKET_ID: 0xc9_20e_wmiacpi!WmiAcpiFunctionControl+4f

BUCKET_ID: 0xc9_20e_wmiacpi!WmiAcpiFunctionControl+4f

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

0: kd> lmvm wmiacpi
start end module name
ba92d000 ba92f280 wmiacpi M (pdb symbols) c:\windows\symbols\sys\wmiacpi.pdb
Loaded symbol image file: wmiacpi.sys
Image path: wmiacpi.sys
Image name: wmiacpi.sys
Timestamp: Sun Apr 13 14:36:37 2008 (480252B5)
CheckSum: 00010888
ImageSize: 00002280
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !devobj 0 f
Device object 0 f not found

June 30, 2009 4:40:21 AM

Unfortunately the registry programs Ccleaner and JV16 Power Tools did not seem to fix the issue. I did go ahead and try to test the ram using Memtest and it came out clean after almost 2 hours of running. So far all I can say is that it only freezes up when browsing the internet using a USB device like a mouse. Nobody else seems to have this particular issue either because I googled it with no clear results.
Related resources
July 6, 2009 2:20:50 PM

OK this is getting to be ridiculous now. I completely wiped my hard drive now and reinstalled the OS and it still is screwing up. And to top it off now it's throwing a totally different error code. Still only messing up when I use Firefox with something in a USB port, but the issue is now 0x0000007F (0x0000000D) HIDCLASS.SYS when a BSOD comes up!!! I am baffled as to how two totally different things can screw up over one issue. However I did manage to create a dump log:
-------------------------------------------------------------------------------------------------------------------------------------------------------------

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini070509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jul 5 18:37:10.531 2009 (GMT-4)
System Uptime: 0 days 7:39:42.223
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...............................
Unable to load image ftdisk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ftdisk.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : ftdisk.sys ( ftdisk!FtpSetGptAttributes+44c )

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

0: 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: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 04000000 to f71fe000

STACK_TEXT:
f78dea18 04000000 f78dea00 85f8bab8 f78dedcc ftdisk!FtpSetGptAttributes+0x44c
WARNING: Frame IP not in any known module. Following frames may be wrong.
f78dea24 f78dedcc f78dea68 804ef19f 85f8ee08 0x4000000
f78dea28 f78dea68 804ef19f 85f8ee08 850fc7a0 0xf78dedcc
f78dedcc 80539ac0 804da890 00000000 00000000 0xf78dea68
f78dedf0 00000000 00000000 00000000 00000000 nt!MiAgePagesAndEstimateClaims+0xab


STACK_COMMAND: kb

FOLLOWUP_IP:
ftdisk!FtpSetGptAttributes+44c
f71fe000 caffff retf 0FFFFh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ftdisk!FtpSetGptAttributes+44c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ftdisk

IMAGE_NAME: ftdisk.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d8419

FAILURE_BUCKET_ID: 0x7f_d_ftdisk!FtpSetGptAttributes+44c

BUCKET_ID: 0x7f_d_ftdisk!FtpSetGptAttributes+44c

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

0: kd> lmvm ftdisk
start end module name
f71f2000 f7210880 ftdisk M (pdb symbols) c:\windows\symbols\sys\ftdisk.pdb
Loaded symbol image file: ftdisk.sys
Image path: ftdisk.sys
Image name: ftdisk.sys
Timestamp: Fri Aug 17 16:52:41 2001 (3B7D8419)
CheckSum: 00021032
ImageSize: 0001E880
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
-------------------------------------------------------------------------------------------------------------------------------------------------
Does anyone possibly understand this?
July 6, 2009 3:55:19 PM

And now another error. This time it's completely different from the last two. Windows Error Reporter stated it might be a Hard Disk error. This is the newest dump I received:
-----------------------------------------------------------------------------------------------------------------------------------------------------------

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini070609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Jul 6 11:43:36.640 2009 (GMT-4)
System Uptime: 0 days 3:31:33.357
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {c0000185, c0000185, 0, 374000}

Probably caused by : ntoskrnl.exe ( nt!_woutput+414 )

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

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

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: c0000185, status code
Arg2: c0000185, i/o status code
Arg3: 00000000, page file number
Arg4: 00374000, offset into page file

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x77_c0000185

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 00000000 to 804f9f43

STACK_TEXT:
f790acdc 00000000 00000077 c0000185 c0000185 nt!_woutput+0x414


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!_woutput+414
804f9f43 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!_woutput+414

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

FAILURE_BUCKET_ID: 0x77_c0000185_nt!_woutput+414

BUCKET_ID: 0x77_c0000185_nt!_woutput+414

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

0: kd> lmvm nt
start end module name
804d7000 806e4000 nt M (pdb symbols) c:\windows\symbols\exe\ntoskrnl.pdb
Loaded symbol image file: ntoskrnl.exe
Image path: ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Fri Feb 06 05:32:51 2009 (498C11D3)
CheckSum: 001F9D43
ImageSize: 0020D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
July 7, 2009 2:35:32 AM

Ok I went ahead and reseated all of the hardware able to be handled, and scanned my entire hard drive for errors. Also just for kicks I scanned my RAM again. And just as I had guessed there is no issue with my hardware at all. I've also had two more errors within one day, both being completly different from the previous ones. Check Disk, Hirens, and various other hard drive tools were of no help. Any guesses???
July 23, 2009 3:41:47 AM

FINALLY!!! I found out what the issue was. Although I'm not happy about it. I got fed up with HP giving me the run around so I decided to crack open the laptop. I went over the laptop for a looong time till... I came upon a big crack in the board. Right across where the network chip and the USB controllers intersect. I knew it couldn't have been software due to the errors but hardware tests failed to show any issues either. I guess sometimes you gotta get your hands dirty. Now I gotta fork over $400 to HP if I want the thing fixed. Probably gonna just use it till it explodes or something then just get a new one.
!