Any ideas how to troubleshoot STOP 0x1000007e ?

Status
Not open for further replies.
I am getting daily (sometimes 2 or 3 times daily) random reboots on my
system and it is getting really frustrating.

The DumpSave report each time says something like:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 21/03/2008
Time: 15:14:45
User: N/A
Computer: LAIRDSWOOD
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xc0000005, 0xb92a9a1a, 0xbad0f528, 0xbad0f224). A dump was saved in: C:\WINDOWS\Minidump\Mini032108-01.dmp.

I used DUMPCHK.EXE to expand the minidump file produced but can't work out
how to stop the problem. I have reproduced the output below.

The things I have tried so far are:

* Looked up the STOP code on MSKB and there are two entries both related to
resuming from hibernation. I do not use hibernation so that can't be the
problem.

* The output below suggests that the sound system may be involved in the
problem as KMIXER, DRMKAUD, SPLITTER and DMUSIC are all part of the MS
Kernel for the audio system. I have uninstalled all my audio drivers and
reinstalled from scratch - they are Audigy ZS2 Platinum Pro drivers. I also
have a Hauppauge TV tuner installed which has audio drivers. Finally I have
SoundTaxi which converts ausdio files (but uses some driver technology to do
its job).

* Unlocker is part of a utility that allows files in use to be unlocked when
required (it is a user action so no automated unlocking of files). I have
uninstalled this and left it off my system for a while but it didn't make
any difference so I have now reinstalled it as i find it very useful.

* I have uninstalled and reinstalled all my motherboard and graphics card
drivers.

* I have removed a second USB disc drive (mentioned in another thread) and
that has removed the probelms with drive page errors appearing in my system
logs.

* I have run stress tests on my system which worked flawlessly for hours at
a time (I used nVidia's system stability test and while it was running I
used 4 different AV packages to play DVDs, Video and multiple audio files,
surfed the internet, scanned, printed images etc)

* I have run DOS based utilites to test memory and other onboard hardwear -
no problems were shown up.

Note apart from the SaveDump entry and other entires during recovery from
the STOP condition there are no other errors appearing my system logs. All
my hardware/software seems to work normally and 95% of the time I can do
anything I want with the system without problems.

Any help would be really appreciated

TIA

Carol Haynes

DumpChk output follows:

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0b410020
PfnDataBase 82000000
PsLoadedModuleList 8055c700
PsActiveProcessHead 80562818
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000007e
BugCheckParameter1 c0000005
BugCheckParameter2 b92a9a1a
BugCheckParameter3 bad0f528
BugCheckParameter4 bad0f224
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 00000a74
DriverListOffset 00003688
DriverCount 000000b6
StringPoolOffset 00006c90
StringPoolSize 000019b0
BrokenDriverOffset 00000000
TriageOptions 00000141
TopOfStack bad0f58c
DebuggerDataOffset 000033f8
DebuggerDataSize 00000290
DataBlocksOffset 00008640
DataBlocksCount 00000006


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Mar 21 15:13:23 2008
System Uptime: 0 days 5:49:26
start end module name
804d7000 806e2000 nt Checksum: 001FB950 Timestamp: Wed Feb 28
09:15:54 2007 (45E5484A)

Unloaded modules:
a90d6000 a9101000 kmixer.sys Timestamp: unavailable (00000000)
a90d6000 a9101000 kmixer.sys Timestamp: unavailable (00000000)
bac60000 bac66000 UnlockerDriv Timestamp: unavailable (00000000)
a91a1000 a91cc000 kmixer.sys Timestamp: unavailable (00000000)
a92e1000 a930c000 kmixer.sys Timestamp: unavailable (00000000)
a934c000 a9352000 UnlockerDriv Timestamp: unavailable (00000000)
ad71f000 ad74a000 kmixer.sys Timestamp: unavailable (00000000)
b066c000 b0697000 kmixer.sys Timestamp: unavailable (00000000)
b06bf000 b06ea000 kmixer.sys Timestamp: unavailable (00000000)
b25ce000 b25f9000 kmixer.sys Timestamp: unavailable (00000000)
baf3b000 baf3c000 drmkaud.sys Timestamp: unavailable (00000000)
b2699000 b26bc000 aec.sys Timestamp: unavailable (00000000)
ba0f5000 ba102000 DMusic.sys Timestamp: unavailable (00000000)
b2f5f000 b2f6d000 swmidi.sys Timestamp: unavailable (00000000)
bae24000 bae26000 splitter.sys Timestamp: unavailable (00000000)
baae8000 baaf1000 processr.sys Timestamp: unavailable (00000000)
b91c7000 b91cb000 kbdhid.sys Timestamp: unavailable (00000000)
bac08000 bac0d000 Cdaudio.SYS Timestamp: unavailable (00000000)
b91cb000 b91ce000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check
 
Your mini dump analysis shows you have a bad component... but sometimes this is caused by an infestation. Just about any component can be the cause.
We usually check memory first, then replace all drivers. Since this is difficult and time consuming, keep a running list of everything you try and every component you test.
Where are you getting your drivers? Try another source... such as the manufacturer of the component.
Sometimes it is helpful to go back to an earlier driver from the same source, or try a different source. Some driver sources can be found with a Google search.
Sometimes it is necessary to download the drivers to a site where you can find them, then remove or disable the existing driver.
Install the new drives in SAFE MODE if it will do that.
Usually this is a driver problem or a defective video graphics, sound, or modem card, or a memory failure. But can sometimes be the electrical interference of a bad cpu fan or power supply. It can also be a defective hard drive at times. Thus, you can have a long period of detection... as you obviously already know.
The first thing I would do, if it will stay on, is run MemTest86 for four hours or 7 passes... on each module, one at a time.
Then change out the video graphic card, then the sound card, one at a time...

Do you get the problem when you remove the sound card altogether?
I am sure other people on this forum will have good suggestions.
 
Thanks - I ran memtest+ from a floppy (latest version) overnight and it didn't generate any errors at all. I know Memtest isn't perfect so I also tried MS's own memory tester.

All the drivers on the system come from the manufacturer's web sites for those components except for the mobo and graphics. For those I downloaded directly from Nvidia's website (since they are where the graphics drivers come from anyway).

It seems purley random when the errors are generated - they can be everything from 1 to 2 hours after the last one to a day or two, they can be when the system has been left alone doing nothing or when it is doing a lot of work.

There just isn't any pattern. It really doesn't help that Microsoft are absolutely terrible at documenting errors.

I have just uninstalled SoundTaxi and Unlocker from my system and the drivers are no longer present in Device Manager and yet I have also got another restart with the following dump:

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0b410020
PfnDataBase 82000000
PsLoadedModuleList 8055c700
PsActiveProcessHead 80562818
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000007e
BugCheckParameter1 c0000005
BugCheckParameter2 b937ca1a
BugCheckParameter3 bad07528
BugCheckParameter4 bad07224
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 00000a74
DriverListOffset 00003688
DriverCount 000000b5
StringPoolOffset 00006c48
StringPoolSize 00001978
BrokenDriverOffset 00000000
TriageOptions 00000141
TopOfStack bad0758c
DebuggerDataOffset 000033f8
DebuggerDataSize 00000290
DataBlocksOffset 000085c0
DataBlocksCount 00000006


Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Mar 21 18:06:06 2008
System Uptime: 0 days 1:17:38
start end module name
804d7000 806e2000 nt Checksum: 001FB950 Timestamp: Wed Feb 28 09:15:54 2007 (45E5484A)

Unloaded modules:
b2907000 b2932000 kmixer.sys Timestamp: unavailable (00000000)
bae8e000 bae8f000 drmkaud.sys Timestamp: unavailable (00000000)
b30de000 b30eb000 DMusic.sys Timestamp: unavailable (00000000)
b29d2000 b29f5000 aec.sys Timestamp: unavailable (00000000)
b30fe000 b310c000 swmidi.sys Timestamp: unavailable (00000000)
badc0000 badc2000 splitter.sys Timestamp: unavailable (00000000)
ba9e8000 ba9f1000 processr.sys Timestamp: unavailable (00000000)
ba3c2000 ba3c6000 kbdhid.sys Timestamp: unavailable (00000000)
bac50000 bac55000 Cdaudio.SYS Timestamp: unavailable (00000000)
ba3c6000 ba3c9000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

I'll try ripping out the sound card and using onboard sound instead, and also rip out the TV card.
 
I suspect you will eventually find it, and it will be a hardware problem...
The next time it occurs, pull the case cover to see if you detect the odor of hot metal or feel any board that has a temperature.
 
Status
Not open for further replies.
Back