trying to figure this one out for a while not getting to much useable info on a google if this minidump means more to you then me then plz respond.
here is the output for windbg
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini062705-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\Symbols*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 Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Jun 27 11:48:59.171 2005 (GMT-7)
System Uptime: 0 days 0:05:03.734
Loading Kernel Symbols
.....................................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {0, 2, 1, 8051e106}
Probably caused by : HTTP.sys ( HTTP!UlIsLowNPPCondition+2e )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8051e106, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+68
8051e106 ff08 dec dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 805421bf to 8051e106
STACK_TEXT:
b7e49c04 805421bf 00000000 8055a6c0 8055a6c0 nt!MiRemovePageByColor+0x68
b7e49c48 8054418b 00000000 c07f6750 00000000 nt!MiAllocatePoolPages+0x3b9
b7e49cb0 8053277e 00000000 00020000 42416c55 nt!ExAllocatePoolWithTag+0x10b
b7e49ccc b7d06444 00000000 00020000 42416c55 nt!ExAllocatePoolWithTagPriority+0x58
b7e49d50 b7d0a5c4 b7d14ba0 ffae5a70 00000000 HTTP!UlIsLowNPPCondition+0x2e
b7e49d88 b7d2b889 b7d2b6ba b7d16c20 00000000 HTTP!UlpTimeoutCheckExpiry+0x48
b7e49d8c b7d2b6ba b7d16c20 00000000 ff4d0020 HTTP!UlpTimeoutMonitorWorker+0x5
b7e49dac 805c4a06 00000001 00000000 00000000 HTTP!UlpThreadPoolWorker+0x1c0
b7e49ddc 80540fa2 b7d2b4fa ffae5a70 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
HTTP!UlIsLowNPPCondition+2e
b7d06444 85c0 test eax,eax
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: HTTP!UlIsLowNPPCondition+2e
MODULE_NAME: HTTP
IMAGE_NAME: HTTP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41672744
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xA_W_HTTP!UlIsLowNPPCondition+2e
BUCKET_ID: 0xA_W_HTTP!UlIsLowNPPCondition+2e
Followup: MachineOwner
---------
I am assuming http.sys relates to hyper text transfer protocol ie connecting to the internet and in fact it often seems to happen online but not always.
Have long suspected my msn software but nothing I been able to put my finger on.
thx dan
here is the output for windbg
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini062705-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\Symbols*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 Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Jun 27 11:48:59.171 2005 (GMT-7)
System Uptime: 0 days 0:05:03.734
Loading Kernel Symbols
.....................................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {0, 2, 1, 8051e106}
Probably caused by : HTTP.sys ( HTTP!UlIsLowNPPCondition+2e )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8051e106, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+68
8051e106 ff08 dec dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 805421bf to 8051e106
STACK_TEXT:
b7e49c04 805421bf 00000000 8055a6c0 8055a6c0 nt!MiRemovePageByColor+0x68
b7e49c48 8054418b 00000000 c07f6750 00000000 nt!MiAllocatePoolPages+0x3b9
b7e49cb0 8053277e 00000000 00020000 42416c55 nt!ExAllocatePoolWithTag+0x10b
b7e49ccc b7d06444 00000000 00020000 42416c55 nt!ExAllocatePoolWithTagPriority+0x58
b7e49d50 b7d0a5c4 b7d14ba0 ffae5a70 00000000 HTTP!UlIsLowNPPCondition+0x2e
b7e49d88 b7d2b889 b7d2b6ba b7d16c20 00000000 HTTP!UlpTimeoutCheckExpiry+0x48
b7e49d8c b7d2b6ba b7d16c20 00000000 ff4d0020 HTTP!UlpTimeoutMonitorWorker+0x5
b7e49dac 805c4a06 00000001 00000000 00000000 HTTP!UlpThreadPoolWorker+0x1c0
b7e49ddc 80540fa2 b7d2b4fa ffae5a70 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
HTTP!UlIsLowNPPCondition+2e
b7d06444 85c0 test eax,eax
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: HTTP!UlIsLowNPPCondition+2e
MODULE_NAME: HTTP
IMAGE_NAME: HTTP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41672744
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xA_W_HTTP!UlIsLowNPPCondition+2e
BUCKET_ID: 0xA_W_HTTP!UlIsLowNPPCondition+2e
Followup: MachineOwner
---------
I am assuming http.sys relates to hyper text transfer protocol ie connecting to the internet and in fact it often seems to happen online but not always.
Have long suspected my msn software but nothing I been able to put my finger on.
thx dan