Jump to content
Posted 04 July 2009 - 05:25 PM
Posted 04 July 2009 - 05:40 PM
Edited by MilesAhead, 04 July 2009 - 05:41 PM.
"I don't want to belong to any club that would have me as a member."
- Groucho Marx
Posted 04 July 2009 - 05:43 PM
Hmm, when i checked with the sis sandra software, it did say that my bios may be inaccurate, What I don't understand is the guy that put in the power supply said that it ran for them when they checked it again and it didn't reboot on them. That's why I am so confused. I did have some errors when I checked the system log but I don't understand them. Should I post them?
Find a tutorial how to check error logs in XP. See if you get any clues. If the system doesn't hard lock, but just reboots, chances are something is causing an error(on non-recoverable error the system will reboot automatically.) I would also do some memory diagnostics. You may have errors that won't hard lock the machine, but if the memory is erratic then it may trigger some checksum to tell the machine data is hosed so it reboots(some parity error or some crap.)
Chances are if the dudes doing the work on the machine put in a defective part, you would hard lock. But it's tough to say. Maybe they messed up some BIOS setting or something.
Posted 04 July 2009 - 07:28 PM
Posted 04 July 2009 - 09:22 PM
TCP/IP has reached the security limit imposed on the number of concurrent (incomplete) TCP connect attempts.
Well...I would not consider SSS as a reliable diagnostic tool, since many of the situations they report to users...are predicated on some mythical average of the systems which have previously used SSS.
A working BIOS is a good BIOS .
The errors (not informational items, not warnings) that exist on the System tab of Event Viewer...can you post all details of the last 3?
You can double-click on the line item to see the detail for any line item in EV.
How To Use Event Viewer - http://www.bleepingcomputer.com/forums/t/40108/how-to-use-event-viewer/
Posted 05 July 2009 - 10:38 AM
0 members, 0 guests, 0 anonymous users