random rebooting

ja5on

ja5on

ja5on

Associate
Joined
27 Mar 2006
Posts
50
Location
Weston-super-Mare
right this is driving me nuts now :mad:

pc:
amd 64 3200+ (socket939)
asus A8V-X mobo
1 gb Ram
1 IDE 80gb HD
Radeon 9600pro
XP SP2 all updated blah blah

for a long time now, if i boot up the pc from a cold boot (after being left for a few hours) the pc once loaded onto the desktop will randomly restart, not always imediatley, sometimes straight away, sometimes after 5-10 mins, its not a case of if but when. However once the pc has done its reboot and is back to the desktop i get the usual 'windows critical error' message pop up but after that the pc is fine and will remain crash-free until the next cold boot.
I've tried doing a format which at the start seemed to work yet after a while the problem was back within an hour of formatting.
Today i have just noticed that when running registry mechanic, during the scan it restarts. Does this mean something is foobar'd with the registry or am i looking at some hardware fault or prehaps a mobo safety feature?
I have run out of things to check now and I'm considering changing the mobo as i bought it in error thinking it was PCI-E one but was in fact PCI-E+ or something - the slot is tiny so won't accept any decent GFX cards anyway

sooooo does anyone have any ideas - i really have no idea :confused:
 
What PSU do you have?

Mine was doing the same thing, found out my Tagen PSU was on it's last legs.
 
Couple of suggestions

Is your PC overclocked at all, if so reset it back to stock settings
Is the airflow from fans on the PC obstructed in anyway causing the inside of the PC to heat up.
Dodgy connections on you PSU plug.
Also I had a strange one once, when I had a USB mouse that also had a regular connector as well. The USB was plugged in and the regualr connector sometimes touched the back of the case, and this caused the PC to reset.

Also take all your components out of the motherboard and reseat them just in case one is slightly loose, this also can be affected by heat inside the case.

Hope that helps in a little way.

Taff
 
Possibly a memory issue, try it with some different ram, or if you have two stick, try swapping between them. I found my issues with Vista were not caused by the motherboard, but a stick of dodgy ram.
 
thanks guys, these are all new things to try....... :)
lets just hope one of them works
 
well its still here but i've got some minidumps now
so, can anyone work out what all this means? :confused:

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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Feb 21 22:29:38.406 2007 (GMT+0)
System Uptime: 0 days 0:00:54.980
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8062bfbf, bac91988, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for netbt.sys
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
Probably caused by : netbt.sys ( netbt+21d00 )

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

kd> !analyze –v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8062bfbf, bac91988, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : netbt.sys ( netbt+21d00 )

Followup: MachineOwner


much appreciated if anyone can
 
You must log in or register to reply here.
Back
Top Bottom