tongue_of_colicab
Veteran
Hi,
Since a couple of days my little htpc keeps rebooting out of nowhere. If I check the event logs I get some info but its not clear to me exactly where the problem lies.
I did not change anything to the hard or software before the problems nor do I think there is anything wrong with the hardware itself because last night for example I could watch a whole movie without any problems. Crashes seem to mostly be when idle.
These are the last 3 dump files Windows created. I got like 15 more but I suppose its not much use posting them all.
What I am seeing is either a driver fault or a program fault (mediaportal.exe, amdpwrmon.exe, though they are in different ones). I tried getting a check on the drivers by running the verifier command but that doesnt seem to be working. If I manually select drivers (all the non windows ones) I just get the same kind of dumps and if I select all it wont boot into windows anymore.
Memory isnt the problem either, memtest x86 didnt find any errors.
Anybody got a clue what could be the problem and how to fix it?
Since a couple of days my little htpc keeps rebooting out of nowhere. If I check the event logs I get some info but its not clear to me exactly where the problem lies.
I did not change anything to the hard or software before the problems nor do I think there is anything wrong with the hardware itself because last night for example I could watch a whole movie without any problems. Crashes seem to mostly be when idle.
These are the last 3 dump files Windows created. I got like 15 more but I suppose its not much use posting them all.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032609-02.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: Thu Mar 26 09:06:39.218 2009 (GMT+1)
System Uptime: 0 days 7:52:51.015
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 44, {88b8c458, 23e, 0, 0}
Probably caused by : ntoskrnl.exe ( nt!_woutput+414 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 88b8c458, Address of the IRP
Arg2: 0000023e
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
IRP_ADDRESS: 88b8c458
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from 00000000 to 804f9f43
STACK_TEXT:
805515c4 00000000 00000000 00000000 00000000 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: 48a3fbd9
FAILURE_BUCKET_ID: 0x44_nt!_woutput+414
BUCKET_ID: 0x44_nt!_woutput+414
Followup: MachineOwner
---------
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032609-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: Thu Mar 26 01:13:14.031 2009 (GMT+1)
System Uptime: 0 days 6:13:02.830
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 tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {0, 2, 0, b35b0765}
Probably caused by : tcpip.sys ( tcpip!ProcessSend+72 )
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: b35b0765, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!ProcessSend+72
b35b0765 833800 cmp dword ptr [eax],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from b35b0a33 to b35b0765
STACK_TEXT:
ba4d3c14 b35b0a33 893df270 88a4a088 ba4d3c60 tcpip!ProcessSend+0x72
ba4d3c74 b35b0923 a6fc4122 00000002 b35e90c0 tcpip!TCPSend+0x43a
ba4d3c98 b35a97e4 00000002 00000002 00000000 tcpip!ProcessPerCpuTCBDelayQ+0x98
ba4d3d18 b35a93ec b35f2038 00000000 ba338980 tcpip!TCBTimeout+0xbf9
ba4d3d28 80545e7f b35f2048 b35f2038 a7a1cdb4 tcpip!TCBTimeoutdpc+0xf
ba4d3d3c 8055c0c0 ba33ae20 ba338c50 00000000 nt!ExSetResourceOwnerPointer+0x7c
ba4d3d40 ba33ae20 ba338c50 00000000 ba33ae20 nt!MiPageFileTraces+0xe40
WARNING: Frame IP not in any known module. Following frames may be wrong.
ba4d3d44 ba338c50 00000000 ba33ae20 80545d64 0xba33ae20
ba4d3d48 00000000 ba33ae20 80545d64 00000000 0xba338c50
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!ProcessSend+72
b35b0765 833800 cmp dword ptr [eax],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: tcpip!ProcessSend+72
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 485b99ad
FAILURE_BUCKET_ID: 0xD1_tcpip!ProcessSend+72
BUCKET_ID: 0xD1_tcpip!ProcessSend+72
Followup: MachineOwner
---------
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini032509-05.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: Wed Mar 25 18:59:37.375 2009 (GMT+1)
System Uptime: 0 days 0:23:18.172
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 ipnat.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ipnat.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {e9766544, 2, 8, e9766544}
*** WARNING: Unable to verify timestamp for tcpip.sys
*** WARNING: Unable to verify timestamp for hal.dll
Probably caused by : ipnat.sys ( ipnat!NatMappingDetachEditor+24 )
Followup: MachineOwner
---------
0: 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: e9766544, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: e9766544, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: e9766544
CURRENT_IRQL: 2
FAULTING_IP:
+1240
e9766544 ?? ???
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from b355c81a to e9766544
FAILED_INSTRUCTION_ADDRESS:
+1240
e9766544 ?? ???
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
80551138 b355c81a 8a35dd88 88fa5630 00000000 0xe9766544
80551154 b3561a71 8a08085c 88fa5630 0006960a ipnat!NatMappingDetachEditor+0x24
80551174 b3562358 88fa5630 0006f707 805511a4 ipnat!NatCleanupMapping+0x75
80551184 b3562a55 88fa5630 89fe0888 8a22d888 ipnat!NatDeleteMapping+0x13a
805511a4 8053722f 00000000 805511e0 02000001 ipnat!NatTcpCallbackFunction+0x85
805511cc b35adcc2 02fe0880 805511e0 00000001 nt!MmPerfUnusedSegmentsEnumerate+0x77
805511f0 b35b445e 00000003 00000001 891a5acc tcpip!TcpInvokeCcb+0x32
80551204 806e78ff 00000004 891a5ac0 8055123c tcpip!TCPDisconnect+0x16
80551214 b35b435a 891a5ac0 00000002 00000000 hal!HalpCopyBufferMap+0xdb
8055123c b35b3491 021a5ac0 02000002 00000000 tcpip!TdiDisconnect+0x103
80551258 b35b980b 891a5ac0 00000002 b35a93dd tcpip!DerefTCB+0x63
805512d0 b35a93ec b35f1fe0 00000000 805513fc tcpip!NotifyOfDisc+0x52
805512e0 8050220f b35f1ff0 b35f1fe0 764382f0 tcpip!TCBTimeoutdpc+0xf
805513fc 8050232b 8055c0c0 ffdff9c0 ffdff000 nt!CcSetDirtyPinnedData+0x12a
80551428 80545e7f 8055c4c0 00000000 00015d8a nt!KiFindFirstSetRight+0x9b
8055142c 8055c4c0 00000000 00015d8a 00000000 nt!ExSetResourceOwnerPointer+0x7c
80551430 00000000 00015d8a 00000000 8055c0c0 nt!MiPageFileTraces+0x1240
STACK_COMMAND: kb
FOLLOWUP_IP:
ipnat!NatMappingDetachEditor+24
b355c81a ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: ipnat!NatMappingDetachEditor+24
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ipnat
IMAGE_NAME: ipnat.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025786
FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_ipnat!NatMappingDetachEditor+24
BUCKET_ID: 0xD1_CODE_AV_BAD_IP_ipnat!NatMappingDetachEditor+24
Followup: MachineOwner
---------What I am seeing is either a driver fault or a program fault (mediaportal.exe, amdpwrmon.exe, though they are in different ones). I tried getting a check on the drivers by running the verifier command but that doesnt seem to be working. If I manually select drivers (all the non windows ones) I just get the same kind of dumps and if I select all it wont boot into windows anymore.
Memory isnt the problem either, memtest x86 didnt find any errors.
Anybody got a clue what could be the problem and how to fix it?