Suggestions for troubleshooting

[STL3200AMD]

My PC is in a restart loop.

Last night it rebooted randomly, and would boot to the desktop then restart again.

Today it restarts during the XP load screen before it even gets to the desktop.

I have set the BIOS settings back to default. It stays up if I boot into safe mode.

I updated the video driver in safe mode and checked the event logs, nothing stands out to me.

Any ideas for further troubleshooting?

 

[DeaconFrost]

It shouldn't even need to be asked anymore, but do you have automatic reboots disabled in the System Properties?

 

[STL3200AMD]

Yes

 

[DeaconFrost]

You could always try a repair install, if you can't pin it down to a driver.

 

[STL3200AMD]

I was able to read the minidump on my laptop, but not exactly sure what to do next...

Could someone tell me what this means?


Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Sun Mar 9 19:14:24.484 2008 (GMT-5)
System Uptime: 0 days 0:00:44.050
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
Unable to load image P17.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for P17.sys
*** ERROR: Module load completed but symbols could not be loaded for P17.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {28, 8, 0, f579a28d}

*** WARNING: Unable to verify timestamp for portcls.sys


Probably caused by : P17.sys ( P17+2028d )

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