Serious error

[Josh]

Hi guys,
The new rig is performing wonderfully..except every now and then..maybe once a day or less it restarts at a random time not when im doing a perticular thing..no BSOD just a complete restart and then when it boots back up I get greeted with a 'Your system had a serious error' message..bellow is a screeny of the error and the report to see if you guys could enlighten me on what's causing these errors please?
http://i7.photobucket.com/albums/y266/Josh_Hill/wtf.jpg
Josh

[kurabii]

to be honest is your bios updated?
alot of random reboots are because your system feels it needs to reboot. possibly the proc is too hot, power supply isnt juicey enough thus boot looping, the power supply is missing a -+5 -+12 (pc experiences), one time when i tried to tv capture in with my rig, with my ATI it would reboot. just automatically reboot and come up with serious error. so i figured out it was the bios.
try that.

please tell me if it keeps happening.
can u detail spec your pc pretty please.
how old are the components, have you tested out what you bought, is it water or air cooled, etc. just so i can troubleshoot it.

thank you in advanced.
ESA

[Josh]

Ok stupid n00by question..what's the best way to find the exact spec of components..is there a proggy that will analyse and tell all?

See the PC was given to me by a good friend it had not been used for a few months..could sitting idle for that much time cause it?

The cpu is hitting about 45*C-50*C in games and now at idle its 40* It happened a few times during gaming too..the game would stutter and then just reboot but after 2 hours solid gaming the gpu was up to only 39*C which is low right?

It's air cooled with 4 8cm coolermaster fans.

I have had the comp since Sunday and have noticed these reboots getting less frequent no whereas it was twice a day at first, it now went 2 days with nothing then happened again this afternoon 10 mins before my 600meg d/l was due to finish :( ..confudling lol

I will let you know when it next does it dude :)

Thanks alot

[furious trout]

Josh any chance you can resize that image to 640x480 it's huge! (i've changed it to a link in the meantime :thumb:

On to the problem, tbh that screen doesn't give us a lot to go on. Have to checked the event logs (Start|Run|eventvwr)It might be able to shed a bit more light on what it is that's causing the reboots (look for big red crosses in the system log and check out the error)

If you post anything you find in there that'll help.

[fillip]

SiSoft Sandra will tell you anything you need to know about hardware version, model numbers, BIOS versions etc etc. :thumb:

[Josh]

Ok looked throught the logs you pointed me to Trout and i found 2 types of error..the one about network is repeatedly(sp) there and the other only once in the series of errors aroudn the time of reboot.

Sorry about the image size I will crop it just to show the log then repost :)
here's the errors
http://i7.photobucket.com/albums/y266/Josh_Hill/untitled-1.jpg
http://i7.photobucket.com/albums/y266/Josh_Hill/untitled2.jpg

Fillip I will download SiSoft now *thumbs up*

[kurabii]

im an aida32 fan :)
fillip's choice is better tho.

well if it just stutters while playing games that could be your video card or like my friends northbridge completely hickups his computer forcing him to reboot.

so he just rebuilt an x2 3800+

do you have a psu tester? or Digital Voltage meter? test components.
how about a post tester? if your friend is reachable and built it himself he would know the detailed specs like he knows his own name.

is that hex problems?
memory bad? ---> run memtest if its ddr memory pc 2100 100 3200 2700. i havent found a memory tester for ddr2 sticks yet.
as for Fozzie it its a kernel error do a FULLL format completely 1's and 0'z the drive first. i kept gettting kernel error after OS install on a dell that i was fixing and couldnt be explained and ythe hdd tested good.
so i completely 0'd the drive and it was "good to go" lol. tacobell
ESA

[FoZZiE]

That sounds like a BSOD but there is an option in windows somewhere to restart the pc instead of just sitting there.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

[Josh]

Ok well I'm guessing as this was a backup machine and hasn't been used properly for quite some time the drivers will be quite out of date yes?

I will speak to him and ask about specs and also when drivers were last installed.

Thanks very much your help is reall appreciated!
Josh

[Da_Rude_Baboon]

Yeah i agree. In the system properties>advanced tab you will have a check box to set weather the computer reboots automatically on a BSOD. The link below might help.

http://support.microsoft.com/?kbid=330187

[Josh]

Ok specs are as follows :)
ASUSTek A7V333 Motherboard (would the system bios code/number help identify if it needs updating?) ahh the SiSoftware is saying the BIOS is old ans should be updated?
AMD Athlon XP 64 2700+
Maxtor 6Y120L0 HDD
Gainward 5700fx
Il update Windoze too then :)

[furious trout]

I'd update everything, it's more than likely a driver somewhere that's causing the error.

[CandyKid]

Interesting... assuming that it ran just peachy-keen before you were given the machine, then it is most likely a driver/software issue.

However, I'd suggest that you run Windows Update and make sure you've done a full install of SP1 and SP2 on Windows XP along with a BIOS update.

FWIW, I've had 3 A7V333 motherboards die on me through regular usage, so if all else fails... start looking at it real careful like. ;-)

PLUR
CK

[Fibbles]

Interesting... assuming that it ran just peachy-keen before you were given the machine, then it is most likely a driver/software issue.

However, I'd suggest that you run Windows Update and make sure you've done a full install of SP1 and SP2 on Windows XP along with a BIOS update.

FWIW, I've had 3 A7V333 motherboards die on me through regular usage, so if all else fails... start looking at it real careful like. ;-)

PLUR
CK

I get those messages occasionally too. Sometimes they come up after I turn my comp on, but there were no problems when I turned it off.

It usually turns out to be my ATi drivers not playing nice's all :angry:

[Josh]

aye could be the old Nvidia drivers playing up then?

The bios has been passworded so I can't go mess anything up as the CPU etc is OC'd just right so I will speak to my mate and ask if he'l update the BIOS for me and get him to do all the driver updates as I'm no good at that sorta stuff lol.

Thanks guys :D
Josh

[CandyKid]

I would highly reccommend you do not overclock on the A7V333 motherboard. But that's just me. Have him remove the OC and then see if the errors continue.

Also, run the memory 1:1 with your CPU, that is, run the memory at DDR333 even if they happen to be DDR400 modules.

PLUR
CK

[Fibbles]

So he gave you this computer, but won't let you mess with it?

The overclock might be what is causing the issue :huh:

[kurabii]

... take out the cmos chip and go to defaults. could be unstable and not OC'd just right lol...

i says start fresh. u have the hardware and windows key.
reinstall->everything and reset the cmos.

thats my take. that pc is like sloppy seconds.
u dont know who shes been with, what shes done, anything about her history.
make your history with her with a fresh HARD format and reinstall of the relationship.

keepin it real since 87'
ESA