crash debug

[Guest]

Windows XP pro system blue screens periodically.
I ran a memory dump thru the debugger with these results:

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

Loading Dump File [C:\Documents and Settings\xxxx\Desktop\test1\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Mon Aug 6 15:55:25.431 2007 (GMT-4)
System Uptime: 2 days 3:25:46.379
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols

Loading unloaded module list
.....................................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 805c607b, f898393c, f8983638}

*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660
Probably caused by : hardware ( nt!PipCallDriverAddDevice+277 )

Followup: MachineOwner

Anyone have any idea on where to go next to figure out what is causing these
stops
"probably caused by: hardware" doesn't give me much of a clue to go on.
"***no owner thread found for resource 8055866" means what?
How can i determine what resource 8055866 is?
What does this refer to: ( nt!PipCallDriverAddDevice+277 ) ??

Any insights appreaciated.....

thanks!

 

[Guest]

Have you set Dr. Watson as the default debugger?
You can do this by clicking on Start and then Run. Type "drwtsn32 -i"
(without quotas) in the run dialog box.

Oh! Just read MORE of the post - me and my useless brain!

This looks like you recently installed Hardware and/or it is failing or
causing a problem with Windows.

"probably caused by: hardware" doesn't give me much of a clue to go on.

Did you receive error messages such as "General Protection Fault" ??
Did you install hardware or software recently?
Was the hardware/software signed by the manafacturer?

You may be installing some virus or trojan and not noticing it (NOT saying
your ignorant or anything like that).
In my opinion, your hardware is failing, a system file is corrupt or your
system's memory is corrupt.

Anyway, any answers to the three questions above?
---
Microdumb - The REAL Microsoft!

Windows XP pro system blue screens periodically.
I ran a memory dump thru the debugger with these results:

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

Loading Dump File [C:\Documents and Settings\xxxx\Desktop\test1\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Mon Aug 6 15:55:25.431 2007 (GMT-4)
System Uptime: 2 days 3:25:46.379
Loading Kernel Symbols
......................................................................................................................................
Loading User Symbols

Loading unloaded module list
....................................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 805c607b, f898393c, f8983638}

*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660
Probably caused by : hardware ( nt!PipCallDriverAddDevice+277 )

Followup: MachineOwner

Anyone have any idea on where to go next to figure out what is causing these
stops
"probably caused by: hardware" doesn't give me much of a clue to go on.
"***no owner thread found for resource 8055866" means what?
How can i determine what resource 8055866 is?
What does this refer to: ( nt!PipCallDriverAddDevice+277 ) ??

Any insights appreaciated.....

thanks!