bugcheck reboot

Toggle sidebar Toggle sidebar
S

ssahl

Junior Member
Feb 2, 2008
6
0
0
I seen another post with the same stop code 0x0000024
as what I have, but I cant duplicate it, in fact probably the last 4 dumps have all gave a different stop code

but here is the latest, this is what dumpchk says

Loading dump file c:\windows\minidump\mini020208-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0a4803e0
PfnDataBase 81086000
PsLoadedModuleList 8055c700
PsActiveProcessHead 805627b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 00000024
BugCheckParameter1 00190292
BugCheckParameter2 aa798b04
BugCheckParameter3 aa798800
BugCheckParameter4 b9e0855e
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000a88
DriverListOffset 00003698
DriverCount 00000089
StringPoolOffset 00005f48
StringPoolSize 000012e8
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack aa798578
DebuggerDataOffset 00003408
DebuggerDataSize 00000290
DataBlocksOffset 00007230
DataBlocksCount 00000006


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Feb 02 04:11:06 2008
System Uptime: 0 days 7:06:18
start end module name
804d7000 806e2000 nt Checksum: 001F873F Timestamp: Wed Feb 28 00:
38:53 2007 (45E53F9D)

Unloaded modules:
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9f37000 a9f62000 kmixer.sys Timestamp: unavailable (00000000)
a9f37000 a9f62000 kmixer.sys Timestamp: unavailable (00000000)
ba3f8000 ba3ff000 USBSTOR.SYS Timestamp: unavailable (00000000)
a9f85000 a9fb0000 kmixer.sys Timestamp: unavailable (00000000)
ba468000 ba46d000 HidBatt.sys Timestamp: unavailable (00000000)
aa611000 aa63c000 kmixer.sys Timestamp: unavailable (00000000)
ba6b3000 ba6b4000 drmkaud.sys Timestamp: unavailable (00000000)
aa664000 aa687000 aec.sys Timestamp: unavailable (00000000)
ad028000 ad035000 DMusic.sys Timestamp: unavailable (00000000)
aa943000 aa951000 swmidi.sys Timestamp: unavailable (00000000)
ba654000 ba656000 splitter.sys Timestamp: unavailable (00000000)
b9a42000 b9a46000 kbdhid.sys Timestamp: unavailable (00000000)
ba420000 ba425000 Cdaudio.SYS Timestamp: unavailable (00000000)
b9a46000 b9a49000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check




bios reads power voltage like this

vcore 1.280V
3.3V 3.248V
5V 5.016V
12V 12.208V


I pretty sure I ruled out the drive(s)

still checking RAM



I'm pretty sure this is a hardware issue
(but I could be wrong)
I'm thinking

motherboard was my first thought

but has all the signs of power supply

I do plug in my tower through a APC battery backup


other specs

Asus P5E-VM DO motherboard
core2duo E6300
2gigs DDR2 800 ram
antec 500watt power supply
radeon x1950 pro vid card

as for the hard drives, well I'm getting consistently at least 1 reboot (bugcheck) every 3 days

this last one is from a winXP pro 32bit that was installed on a SATA 10,000rpm drive

but before this last I was getting them on same OS but it was on a RAID 0 setup


this was why I ruled out the hard drive, but I could use some input

 
D

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Originally posted by: ssahl
I seen another post with the same stop code 0x0000024
as what I have, but I cant duplicate it, in fact probably the last 4 dumps have all gave a different stop code

but here is the latest, this is what dumpchk says

Loading dump file c:\windows\minidump\mini020208-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0a4803e0
PfnDataBase 81086000
PsLoadedModuleList 8055c700
PsActiveProcessHead 805627b8
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 00000024
BugCheckParameter1 00190292
BugCheckParameter2 aa798b04
BugCheckParameter3 aa798800
BugCheckParameter4 b9e0855e
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000a88
DriverListOffset 00003698
DriverCount 00000089
StringPoolOffset 00005f48
StringPoolSize 000012e8
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack aa798578
DebuggerDataOffset 00003408
DebuggerDataSize 00000290
DataBlocksOffset 00007230
DataBlocksCount 00000006


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Feb 02 04:11:06 2008
System Uptime: 0 days 7:06:18
start end module name
804d7000 806e2000 nt Checksum: 001F873F Timestamp: Wed Feb 28 00:
38:53 2007 (45E53F9D)

Unloaded modules:
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9bb0000 a9bdb000 kmixer.sys Timestamp: unavailable (00000000)
a9f37000 a9f62000 kmixer.sys Timestamp: unavailable (00000000)
a9f37000 a9f62000 kmixer.sys Timestamp: unavailable (00000000)
ba3f8000 ba3ff000 USBSTOR.SYS Timestamp: unavailable (00000000)
a9f85000 a9fb0000 kmixer.sys Timestamp: unavailable (00000000)
ba468000 ba46d000 HidBatt.sys Timestamp: unavailable (00000000)
aa611000 aa63c000 kmixer.sys Timestamp: unavailable (00000000)
ba6b3000 ba6b4000 drmkaud.sys Timestamp: unavailable (00000000)
aa664000 aa687000 aec.sys Timestamp: unavailable (00000000)
ad028000 ad035000 DMusic.sys Timestamp: unavailable (00000000)
aa943000 aa951000 swmidi.sys Timestamp: unavailable (00000000)
ba654000 ba656000 splitter.sys Timestamp: unavailable (00000000)
b9a42000 b9a46000 kbdhid.sys Timestamp: unavailable (00000000)
ba420000 ba425000 Cdaudio.SYS Timestamp: unavailable (00000000)
b9a46000 b9a49000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check




bios reads power voltage like this

vcore 1.280V
3.3V 3.248V
5V 5.016V
12V 12.208V


I pretty sure I ruled out the drive(s)

still checking RAM



I'm pretty sure this is a hardware issue
(but I could be wrong)
I'm thinking

motherboard was my first thought

but has all the signs of power supply

I do plug in my tower through a APC battery backup


other specs

Asus P5E-VM DO motherboard
core2duo E6300
2gigs DDR2 800 ram
antec 500watt power supply
radeon x1950 pro vid card

as for the hard drives, well I'm getting consistently at least 1 reboot (bugcheck) every 3 days

this last one is from a winXP pro 32bit that was installed on a SATA 10,000rpm drive

but before this last I was getting them on same OS but it was on a RAID 0 setup


this was why I ruled out the hard drive, but I could use some input
Click to expand...

Use the debugger and debug the dumps you have (see my site / read my .sig). If you really are getting all different dumps, though, you have a hardware issue.
 
S

ssahl

Junior Member
Feb 2, 2008
6
0
0

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


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

Symbol search path is: srv*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Feb 2 04:11:06.468 2008 (GMT-8)
System Uptime: 0 days 7:06:18.035
Loading Kernel Symbols
........................................................................................................................................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {190292, aa798b04, aa798800, b9e0855e}

Unable to load image d346bus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for d346bus.sys
*** ERROR: Module load completed but symbols could not be loaded for d346bus.sys


Probably caused by : memory_corruption

Followup: memory_corruption


Does this for sure mean it was from the RAM?

one thing I did do was go into the bios and manually set the memory timings
they were set to auto, but when I set to manual the last timing was at 15, I changed to 18 as the RAM specs said it should be
no reboots yet but before I say the problem was as easy as that, I'll wait at least another 10 days and see if I get any more

 
S

ssahl

Junior Member
Feb 2, 2008
6
0
0
I cant remember right off hand, as they happened on the other hard drive (raid 0)
I think one of them was 0x000008e
I didnt run the windbg on any of those just the dumpchk

the above stop code is probably the only one that came up more then once (2 possibly 3)

if you think the info is worth getting and would let me pinpoint the exact problem I'll unhook this drive and connect the other 2 drives and boot from the raid 0

if nothing else this gave me a good chance to see which was faster
2 7200rpm drives on a raid 0

or 1 10,000rpm drive


even though windows installed faster on the raid, I think the 10,000rpm drive is a little faster
very close though
 
S

ssahl

Junior Member
Feb 2, 2008
6
0
0
Another thing, not sure if has anything to do with my problem.
This motherboard uses a 'physical address extension'
meaning that I only get 1.96GB of the 4 x 512 sticks that are installed
even when it posts it uses that much for bios, or raid software or something
I never did care for that to much.
 
D

dclive

Elite Member
Oct 23, 2003
5,626
2
81
/PAE has nothing to do with 1.96GB of 2.0GB of RAM installed; to me that sounds perfectly normal perhaps your video card uses a little?

I suggest getting the dumpfiles and debugging them, but based on what you've said (that they're different) it sounds like you've got a hardware issue.
 
S

ssahl

Junior Member
Feb 2, 2008
6
0
0
ok, here is 3 more dump files (still no reboots since changing memory timing in bios)

one or more of these listed below may very well be from a sepearate issue
running among other things bittorrent
(bittorrent was once a great thing, now it reminds me to much of kazza or limewire, I'm about ready to stop using it for good)


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


Loading Dump File [J:\Mini011908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Jan 19 06:37:28.593 2008 (GMT-8)
System Uptime: 0 days 7:33:46.284
Loading Kernel Symbols
..................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8060bfe1, a1db6ad0, 0}



Probably caused by : ntkrpamp.exe ( nt!ExpAllocateHandleTableEntry+165 )

Followup: MachineOwner



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


Loading Dump File [J:\Mini012908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Jan 29 08:01:20.125 2008 (GMT-8)
System Uptime: 1 days 16:02:51.819
Loading Kernel Symbols
.................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {0, 2, 1, 805219c4}



Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )

Followup: MachineOwner



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


Loading Dump File [J:\Mini013108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Jan 31 05:50:33.109 2008 (GMT-8)
System Uptime: 0 days 7:25:59.796
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}



Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
 
S

ssahl

Junior Member
Feb 2, 2008
6
0
0
sure enough, I ran a memory test and everything passed great till the 3rd slot, then major errors
so I pulled that one out, that should end my bugchecks
thanks for the help, I actually learned some new things that I'm sure will help me in the future
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom