We help IT Professionals succeed at work.

Random Reboots

netsmithcentral
on
1,475 Views
Last Modified: 2012-06-27
I have one Windows XP Pro SP2 computer that is rebooting at random times.  After the reboot, this error is logged in the event log:
Event ID: 1003           Event Source: System Error
Error code 1000007e, parameter1 c0000005, parameter2 b686dccf, parameter3 f89b1bb4, parameter4 f89b18b0.



Here's a copy of my two most recent Minidump's (these are small dump files (64K), I've reset the system to do Kernel dumps in case it happens again).
01/19/07
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion        0000000f
MinorVersion        00000a28
DirectoryTableBase  00039000
PfnDataBase         81c91000
PsLoadedModuleList  8055a420
PsActiveProcessHead 805604d8
MachineImageType    0000014c
NumberProcessors    00000001
BugCheckCode        1000007e
BugCheckParameter1  c0000005
BugCheckParameter2  b683eccf
BugCheckParameter3  b5597bb4
BugCheckParameter4  b55978b0
PaeEnabled          00000000
KdDebuggerDataBlock 8054c060
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       000003e8
DriverListOffset      00002ff8
DriverCount           0000008b
StringPoolOffset      00005940
StringPoolSize        00001358
BrokenDriverOffset    00000000
TriageOptions         00000041
TopOfStack            b5597c18
DebuggerDataOffset    00002d68
DebuggerDataSize      00000290
DataBlocksOffset      00006c98
DataBlocksCount       00000004


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri Jan 19 14:46:30 2007
System Uptime: 11 days 1:21:03
start    end        module name
804d7000 806eb100   nt             Checksum: 002198AF  Timestamp: Tue Mar 01 16:59:37 2005 (42250FF9)

Unloaded modules:
b5569000 b5594000   kmixer.sys    Timestamp: unavailable (00000000)
b55e1000 b560c000   kmixer.sys    Timestamp: unavailable (00000000)
b5681000 b56ac000   kmixer.sys    Timestamp: unavailable (00000000)
b56a9000 b56d4000   kmixer.sys    Timestamp: unavailable (00000000)
b5771000 b579c000   kmixer.sys    Timestamp: unavailable (00000000)
b5d28000 b5d3a000   naveng.sys    Timestamp: unavailable (00000000)
b5d3a000 b5e04000   navex15.sys    Timestamp: unavailable (00000000)
b58c5000 b58f0000   kmixer.sys    Timestamp: unavailable (00000000)
b593d000 b5968000   kmixer.sys    Timestamp: unavailable (00000000)
b59dd000 b5a08000   kmixer.sys    Timestamp: unavailable (00000000)
b5a55000 b5a80000   kmixer.sys    Timestamp: unavailable (00000000)
b5a7d000 b5aa8000   kmixer.sys    Timestamp: unavailable (00000000)
b6668000 b6693000   kmixer.sys    Timestamp: unavailable (00000000)
f8c2f000 f8c30000   drmkaud.sys    Timestamp: unavailable (00000000)
b6693000 b66b6000   aec.sys     Timestamp: unavailable (00000000)
f17df000 f17ec000   DMusic.sys    Timestamp: unavailable (00000000)
f17ef000 f17fd000   swmidi.sys    Timestamp: unavailable (00000000)
f8a08000 f8a0a000   splitter.sys    Timestamp: unavailable (00000000)
b6e86000 b6e98000   naveng.sys    Timestamp: unavailable (00000000)
b6e98000 b6f62000   navex15.sys    Timestamp: unavailable (00000000)
f8606000 f860f000   processr.sys    Timestamp: unavailable (00000000)
f85f6000 f8601000   p3.sys      Timestamp: unavailable (00000000)
f3a93000 f3a97000   kbdhid.sys    Timestamp: unavailable (00000000)
f176e000 f1773000   Cdaudio.SYS    Timestamp: unavailable (00000000)
edb9f000 edba2000   Sfloppy.SYS    Timestamp: unavailable (00000000)



01/22/07
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion        0000000f
MinorVersion        00000a28
DirectoryTableBase  00039000
PfnDataBase         81c91000
PsLoadedModuleList  8055a420
PsActiveProcessHead 805604d8
MachineImageType    0000014c
NumberProcessors    00000001
BugCheckCode        1000007e
BugCheckParameter1  c0000005
BugCheckParameter2  b686dccf
BugCheckParameter3  f89b1bb4
BugCheckParameter4  f89b18b0
PaeEnabled          00000000
KdDebuggerDataBlock 8054c060
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       000003e8
DriverListOffset      00002ff8
DriverCount           0000008b
StringPoolOffset      00005940
StringPoolSize        00001358
BrokenDriverOffset    00000000
TriageOptions         00000041
TopOfStack            f89b1c18
DebuggerDataOffset    00002d68
DebuggerDataSize      00000290
DataBlocksOffset      00006c98
DataBlocksCount       00000004


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Mon Jan 22 17:42:01 2007
System Uptime: 0 days 4:19:07
start    end        module name
804d7000 806eb100   nt             Checksum: 002198AF  Timestamp: Tue Mar 01 16:59:37 2005 (42250FF9)

Unloaded modules:
b55f3000 b561e000   kmixer.sys    Timestamp: unavailable (00000000)
b614f000 b617a000   kmixer.sys    Timestamp: unavailable (00000000)
ef838000 ef839000   drmkaud.sys    Timestamp: unavailable (00000000)
b6212000 b621f000   DMusic.sys    Timestamp: unavailable (00000000)
b617a000 b619d000   aec.sys     Timestamp: unavailable (00000000)
b6222000 b6230000   swmidi.sys    Timestamp: unavailable (00000000)
f8ab0000 f8ab2000   splitter.sys    Timestamp: unavailable (00000000)
b6e81000 b6e93000   naveng.sys    Timestamp: unavailable (00000000)
b6e93000 b6f62000   navex15.sys    Timestamp: unavailable (00000000)
f8666000 f866f000   processr.sys    Timestamp: unavailable (00000000)
f8656000 f8661000   p3.sys      Timestamp: unavailable (00000000)
ef903000 ef907000   kbdhid.sys    Timestamp: unavailable (00000000)
efd2d000 efd32000   Cdaudio.SYS    Timestamp: unavailable (00000000)
ebbb8000 ebbbb000   Sfloppy.SYS    Timestamp: unavailable (00000000)
Comment
Watch Question

CERTIFIED EXPERT
Most Valuable Expert 2011
Top Expert 2011

Commented:
Can you please upload those 2 minidumps to http://www.ee-stuff.com? Thanks!!
CERTIFIED EXPERT
Most Valuable Expert 2011
Top Expert 2011
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
CERTIFIED EXPERT
Most Valuable Expert 2011
Top Expert 2011

Commented:
Diagnostic Interface Driver....

Also, in Device Manager>View>Show Hidden Devices if not shown, paste this into command prompt

set devmgr_show_nonpresent_devices=1

Under Non Plug and Play drivers, see if you see it listed there with a comment might make it easier to find....See if you can uninstall it/remove it....Might just uninstall the whole Modem, and any helper apps from the Control panel, and reinstall (just the device driver itself)

Device Manager does not display devices that are not connected to the Windows XP-based computer
http://support.microsoft.com/kb/315539

Author

Commented:
This box is a COM server with two external USB modems attatched to it.  They're both Diamond SupraMax 56K USB modems.  There is not currently, and as far as I know, never was, any Conextant Modem connected to the computer.  Even with non present devices shown in DevMgr, I see no reference to a Conextant Modem.
CERTIFIED EXPERT
Most Valuable Expert 2011
Top Expert 2011

Commented:
Did you try searching the registry also? May be wrong about teh Conexant part of it...

That driver is definately where the Exception hit in both .dmp files. Directly above the Exception record, is a reference to
winacusb.sys
Not being able to load the symbols. Shouldnt be a problem normally, but I just thought it was odd...

Did find a reference to that .sys file though, definately from Conexant....Didnt the Diamond line use Conexant Chipsets in them?

Double check your modems in the driver details, and verify you dont see either of these 2 drivers......

Or....

Simply rename them to .old in c:\windows\system32\drivers and see if the modems still work.....

Author

Commented:
Sorry, I don't know too much about hardware troubleshooting.  I checked the modem properties, and both modems list the mdmxsdk.sys file.  Do you think I should just uninstall and reinstall these two modems?  Find a new copy of this file?

These are the driver files my two modems are reporting
================================
C:\WINDOWS\system32\DRIVERS\hxfsetup.exe
C:\WINDOWS\system32\DRIVERS\mdmxsdk.sys
C:\WINDOWS\system32\drivers\Modem.sys        <=== digitally signed by "Microsoft Windows Publisher"
C:\WINDOWS\system32\DRIVERS\winacusb.sys
C:\WINDOWS\system32\hsfinst.dll
C:\WINDOWS\system32\mdmxsdk.dll
C:\WINDOWS\system32\sup2920.cty
CERTIFIED EXPERT
Most Valuable Expert 2011
Top Expert 2011

Commented:
These are the driver files my two modems are reporting
================================
C:\WINDOWS\system32\DRIVERS\hxfsetup.exe
C:\WINDOWS\system32\DRIVERS\mdmxsdk.sys  <~~~~~This is the file that caused the Exception Error....
C:\WINDOWS\system32\drivers\Modem.sys        <=== digitally signed by "Microsoft Windows Publisher"
C:\WINDOWS\system32\DRIVERS\winacusb.sys  <~~~~~might have been called by this one.....or somehow related....
C:\WINDOWS\system32\hsfinst.dll
C:\WINDOWS\system32\mdmxsdk.dll
C:\WINDOWS\system32\sup2920.cty

Commented:
If your windows has the following software, it may cause blue screen problem of bugcheck code 7E.
Netlimiter
Visual Insight
Kaspery AntiVirus
zonealarm
Easy File and Folder Protector (FDCBNT.SYS)
sfmsrv.sys (Macintosh File Server)
snp2sxp.sys
ALCXSENS.SYS
SB sound card driver)

The crash may be caused by faulty ram or device driver error (ie video, sound card, modem and etc). The system event log and the minidump has the most useful diagnostic information. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump. Check system event 1001 and 1003 and it has the detail of the blue screen.

Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......

Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000

Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here

Zip 5 to 6 minidumps to a zip file and attach it at any webspace. I will study the dump and find out the culprit. If you can't provide the minidumps, run memtest to stress test the ram. Make sure that your windows is not infected with spyware, adware adn chkdsk /r.
http://www.memtest86.com/.

Get public webspace
Use a free service like rapidshare to attach the minidumps and post the url of the mimidumps at this thread.
http://www.rapidshare.de/

Author

Commented:
@cpc2004, the minidumps and event log have already been posted earlier in this question.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.