Windows XP Pro restarts during system start up for no good reason

[libroos]

Hi all,

I've an Windows XP Pro system and it keeps getting restarted abruptly in the midst of work, sometimes during starting up. I suspect it could be due to the ADSL Modem.Anyone encounter this before?

My ADSL modem is Efficient SpeedStream 4060.

Attached below is the dumpchk article found from MS KB and I had run and the details are below.

1.

http://support.microsoft.com/default.aspx?kbid=315263

2.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;315271

Pls advise. Thk you.

Rgds
libroos


[Event Log - System]
Source: System Error
Event ID: 1003
-----------------------------------------
Error code 000000b8, parameter1 00000000, parameter2 00000000, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

-----------------------------------------

0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 62 000000b
0020: 38 20 20 50 61 72 61 6d 8 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

-----------------------------------------

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81053000
PsLoadedModuleList 8054a130
PsActiveProcessHead 8054c178
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 000000b8
BugCheckParameter1 00000000
BugCheckParameter2 00000000
BugCheckParameter3 00000000
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 8053a2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 000006c0
DriverListOffset 000032c8
DriverCount 00000095
StringPoolOffset 00005f08
StringPoolSize 00001488
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack 8053e040
DebuggerDataOffset 00003038
DebuggerDataSize 00000290
DataBlocksOffset 00007390
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 1) MP (2 procs) Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054a130
Debug session time: Thu Sep 23 22:43:11 2004
System Uptime: 0 days 0:02:04
start end module name
804d4000 806b9000 nt Checksum: 001D3970 Timestamp: Thu Aug 29 16:04:44 2002 (3D6DD59C)

Unloaded modules:
f77ef000 f77f8000 en4060ld.sys Timestamp: unavailable (00000000)
f792f000 f7934000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7af3000 f7af6000 Sfloppy.SYS Timestamp: unavailable (00000000)
-----------------------------------------

Finished dump check

 

[Jump1ng]

I would check your hard drive for errors either schedule a checksk or download a tool from the makers of your drive to check the hard drive.

Also check you RAM for errors a good free tool can be found on this link

http://www.memtest86.org

---
Make the best use of what is in your power, and take the rest as it happens.

 

[bcastner]

Look closely for an issue with any parallel port or USB connected device. For example, parallel port Zip drives can do this. USB devices such as scanners can do this if they are not on!

This error is nearly always a device driver issue with a parallel port or USB device.

Do the steps discussed in this MS KB:

http://support.microsoft.com/default.aspx?scid=kb;en-us;308514&sd=tech

 

[Friedy]

It sounds like Windows is having problems entering graphic mode, because video drivers are unable to start properly. Commonly this is a video driver issue, or a hardware conflict with the video card. Reboot in Safe Mode (which uses a default VGA driver) and see if this resolves the problem. If so, try to correct the problem by disabling, removing, or rolling back the video driver. If this don't work then try reloading latest service pack.

 

[libroos]

Hi Jump1ng,

My hard drive was 'checked' for errors automatically, after the abrupt restart. grrr...

System just upgraded to p4 2.8C HT. Last time used AMD processor also encountered the same thing. Thought was the processor issue, then went for upgrade, in the end still the same.

RAM had changed. Had used back the same hard drive.

I would suspect it's the ADSL modem, becos' everytime prior to the system abrupt restart during startup, i noticed that the USB Efficient Speedstream 4060 was on syncing.

Anyone has links to the latest drivers?

Thk you everyone for your super fast reply.

Rgds
libroos

 

[bcastner]

Friedy,

Where in the dump log do you see indications of a video driver issue?

 

[libroos]

Hi bcastner,

Could Friedy be referring to the last three lines?

Unloaded modules:
f77ef000 f77f8000 en4060ld.sys Timestamp: unavailable (00000000)
f792f000 f7934000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7af3000 f7af6000 Sfloppy.SYS Timestamp: unavailable (00000000)

 

[bcastner]

It is not unusual to see at startup not-loaded or unloaded drivers.

But none of these are video related.

It is just that an 0x8b stop error really has nothing to do with the video subsystem.

 

[libroos]

Hi bcastner,

Then what does 0x8b error usually indicates?

Rgds
libroos

 

[yalamo]

I can only tell you how I took care of a similar problem.

I have a cable modem (Daewoo Cruiser) that was connected to a USB2 port (Win XP). Intermittently, once or twice a day, it would decide to reboot. Very, very, annoying! Error messages were similar to yours.

I finally tracked it down to the cable modem (if I disconnected it, it wouldn't reboot).

So I installed a network card, connected the modem through the Ethernet port, and I haven't had any problems since.

 

[bcastner]

USB or Parallel port device driver or device hard error. This is typical:

http://support.microsoft.com/default.aspx?scid=kb;en-us;281428

From Technet:
ATTEMPTED_SWITCH_FROM_DPC (0xB8)

A wait operation, attach process, or yield was attempted from a DPC routine.
This is not a legal operation and the stack track will lead to the offending code and original DPC routine.

As you can see, it is a bad device driver code situation. A longer explanation:

http://www.sysinternals.com/ntw2k/info/dpc.shtml

 

[libroos]

Hi bcastner,

Do you suggest that I have bad usb software driver for my Efficient 4060 usb modem?

 

[bcastner]

A quick look on the web suggets this is a possibility:

http://forums.whirlpool.net.au/forum-replies.cfm?t=67928