System reboots intermittently - WinXP SP2

G

Guest

My system reboots itself every so often for seemingly no reason. I ran the
debugger and have attached the results below. It appears my problem is with
the PCI2 slot and a soundblaster sound card, if I'm reading it correctly.
Problem is I don't even have that sound card installed anymore. How can I
fix this???

Thanks! Robert


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


Loading Dump File [I:\WINDOWS\Minidump\Mini020506-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
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sun Feb 5 13:06:22.531 2006 (GMT-5)
System Uptime: 0 days 4:22:26.136
Loading Kernel Symbols
..............................................................................................................................................
Loading unloaded module list
...............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {5dc, 2, 0, 805001ad}

Probably caused by : ntkrnlpa.exe ( nt!KiUnlinkThread+7 )

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: 000005dc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 805001ad, address which referenced memory

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


READ_ADDRESS: 000005dc

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiUnlinkThread+7
805001ad 8b10 mov edx,[eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80500214 to 805001ad

STACK_TEXT:
80548cb4 80500214 ff302278 ff302280 00000002 nt!KiUnlinkThread+0x7
80548cc8 8050040b 00000000 80548ce4 00000000 nt!KiUnwaitThread+0x12
80548cf4 804ff18c a96dd5c9 00000088 80548e1c nt!KiWaitTest+0xab
80548e00 804ff34b 80551b80 80551920 ffdff000 nt!KiTimerListExpire+0x7a
80548e2c 80540d5d 80551f80 00000000 000f6088 nt!KiTimerExpiration+0xaf
80548e40 80551920 ffdffc50 00000000 00000000 nt!KiRetireDpcList+0x46
ffdff980 00000000 f7bf0000 003770b9 00000000 nt!KiIdleThread0


FOLLOWUP_IP:
nt!KiUnlinkThread+7
805001ad 8b10 mov edx,[eax]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiUnlinkThread+7

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xA_nt!KiUnlinkThread+7

BUCKET_ID: 0xA_nt!KiUnlinkThread+7

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

Gerry Cornell

RJ

Have you run a full anti-virus with updated definitions in Safe Mode?


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

RJ said:
My system reboots itself every so often for seemingly no reason. I ran
the
debugger and have attached the results below. It appears my problem is
with
the PCI2 slot and a soundblaster sound card, if I'm reading it correctly.
Problem is I don't even have that sound card installed anymore. How can
I
fix this???

Thanks! Robert


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


Loading Dump File [I:\WINDOWS\Minidump\Mini020506-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
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sun Feb 5 13:06:22.531 2006 (GMT-5)
System Uptime: 0 days 4:22:26.136
Loading Kernel Symbols
............................................................................................................................................
Loading unloaded module list
..............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {5dc, 2, 0, 805001ad}

Probably caused by : ntkrnlpa.exe ( nt!KiUnlinkThread+7 )

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: 000005dc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 805001ad, address which referenced memory

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


READ_ADDRESS: 000005dc

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiUnlinkThread+7
805001ad 8b10 mov edx,[eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80500214 to 805001ad

STACK_TEXT:
80548cb4 80500214 ff302278 ff302280 00000002 nt!KiUnlinkThread+0x7
80548cc8 8050040b 00000000 80548ce4 00000000 nt!KiUnwaitThread+0x12
80548cf4 804ff18c a96dd5c9 00000088 80548e1c nt!KiWaitTest+0xab
80548e00 804ff34b 80551b80 80551920 ffdff000 nt!KiTimerListExpire+0x7a
80548e2c 80540d5d 80551f80 00000000 000f6088 nt!KiTimerExpiration+0xaf
80548e40 80551920 ffdffc50 00000000 00000000 nt!KiRetireDpcList+0x46
ffdff980 00000000 f7bf0000 003770b9 00000000 nt!KiIdleThread0


FOLLOWUP_IP:
nt!KiUnlinkThread+7
805001ad 8b10 mov edx,[eax]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiUnlinkThread+7

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xA_nt!KiUnlinkThread+7

BUCKET_ID: 0xA_nt!KiUnlinkThread+7

Followup: MachineOwner
Click to expand...
 
G

Guest

Yes, I have with two different antivirus programs and several spyware
programs in both safe mode and normal. I have also checked my registry as
best I could but couldn't seem to find anything relating.

RJ
 
G

Guest

http://help.lockergnome.com/lofiversion/index.php/t41360.html
If you are the same poster in the link above..? This seems to be a recurring
problem even after it
is fixed.. This leads me to believe it may be a hardware problem or is heat
related in some way..
Make sure your memory is installed properly (seated firmly in the right
slots) and is compatible/adhears to the mobo's requirements/specs..
Is the PSU old or new..?
Are you overclocking..? If so return to the default stock settings and mem
timings for your mobo..
Have you cleaned out all possible dust bunnies from case fans, CPU fan, etc..?
Replaced the CMOS battery latley..?
Updated video card drivers..?
Perhaps you may need to re-seat device cables, cards, memory sticks, CPU,
etc..
Is your computer home built or OEM retail...?
j;-j

RJ said:
My system reboots itself every so often for seemingly no reason. I ran the
debugger and have attached the results below. It appears my problem is with
the PCI2 slot and a soundblaster sound card, if I'm reading it correctly.
Problem is I don't even have that sound card installed anymore. How can I
fix this???

Thanks! Robert


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


Loading Dump File [I:\WINDOWS\Minidump\Mini020506-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
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sun Feb 5 13:06:22.531 2006 (GMT-5)
System Uptime: 0 days 4:22:26.136
Loading Kernel Symbols
............................................................................................................................................
Loading unloaded module list
..............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {5dc, 2, 0, 805001ad}

Probably caused by : ntkrnlpa.exe ( nt!KiUnlinkThread+7 )

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: 000005dc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 805001ad, address which referenced memory

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


READ_ADDRESS: 000005dc

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiUnlinkThread+7
805001ad 8b10 mov edx,[eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80500214 to 805001ad

STACK_TEXT:
80548cb4 80500214 ff302278 ff302280 00000002 nt!KiUnlinkThread+0x7
80548cc8 8050040b 00000000 80548ce4 00000000 nt!KiUnwaitThread+0x12
80548cf4 804ff18c a96dd5c9 00000088 80548e1c nt!KiWaitTest+0xab
80548e00 804ff34b 80551b80 80551920 ffdff000 nt!KiTimerListExpire+0x7a
80548e2c 80540d5d 80551f80 00000000 000f6088 nt!KiTimerExpiration+0xaf
80548e40 80551920 ffdffc50 00000000 00000000 nt!KiRetireDpcList+0x46
ffdff980 00000000 f7bf0000 003770b9 00000000 nt!KiIdleThread0


FOLLOWUP_IP:
nt!KiUnlinkThread+7
805001ad 8b10 mov edx,[eax]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiUnlinkThread+7

MODULE_NAME: nt

IMAGE_NAME: ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1d

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xA_nt!KiUnlinkThread+7

BUCKET_ID: 0xA_nt!KiUnlinkThread+7

Followup: MachineOwner
Click to expand...
 
G

Guest

Yes, that is me. I couldn't remember where I first posted this problem.
Everything is either connected or seated properly. The system is home
built. I have updated the drivers for all of the hardware I have installed.
Funny thing is that I have another WinXP option on boot up from having to
reinstall windows a couple of weeks ago. Powering up into the clean install
doesn't cause the system to reboot at odd times. It runs fine. Only problem
is that all of my software and the kids games are in the Winxp copy that
reboots all of the time. I would have to reinstall alot of stuff into the
clean install and was trying to avoid do that since some of my cds are very
scratched and may no longer work properly.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Random reboots 7
Blue Screen after latest Sec Patches 3
Bluescreen 3
Crash dump 6
server reboots periodically - BugCheck 50 3
Windows XP Help analysing dump data 5
wininit - how to restore - bcod 1
IRQL_NOT_LESS_OR_EQUAL when using AMD Athlon 64's Cool'n'Quiet inWindows XP Pro. SP2 2

Top