[Cyph3r]

Well, I have a weird problem with my relatively new rig. Say my PC has been off all night, when I turn it back on it will be fine for a while but the programs will randomly start crashing and windows will say they need to be closed, and then eventually the PC will restart on its own, then when it turns on it will say "Windows has recovered from a serious error", heres a screenshot:-

Now, I reformatted my PC yesterday, and the problem hasn't happened yet although I had my PC running, although it wasn't doing anything, I then went downstairs for about 20 minutes, when I came back the PC was loading up from a reboot and it again displayed the same error message. What the hell is going on? Can someone please help me with this?

 

[BombF1rst]

It won't even let you send the error it just reboots on it's own?

I have had a similar "Serious error" although I did not figure out what it was. It hasn't bothered me but once. I have not seen it sense. This happen to my Sig rig a few weeks ago.

Nothing is seriously wrong with my rig, so that makes me think it was just a random error/crash from conflicting programs running together.

 

[Cyph3r]

Quote:

Originally Posted by BombF1rst It won't even let you send the error it just reboots on it's own?

huh? the error message appears AFTER its rebooted on its own. Also, after its rebooted on its own, and this error message is displayed, it will not happen again until i turn the PC off for a long time and use it again (i.e after its been off all night and i then use it in the morning) Which is really strange.

 

[grunion]

Need to know the specific error, I have a feeling it's related to your onboard sound.

 

[Cyph3r]

Next time it happens ill click the bit that shows more info about the error and then post a screenshot.

 

[Cyph3r]

new pic:

 

[hiKaRux3]

Have you tried reinstalling Windows?

 

[weltall]

Took me a while but after searching seems 1000008E is the same as 0X8E

I found this which you can check

http://msdn2.microsoft.com/en-us/library/ms794023.aspx

It seems you have the memory access violation C0000005. It could be anything that gives you the pain on the botox. Could be a game, some drivers or even hardware problem.

If the link above doesn't work then http://oca.microsoft.com/en/windiag.asp get this memory tester.

If this doesn't help too and that means it must be a software problem type verifier in Start - Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.

You will be creating a crash dump file in c:\\windows\\minidump every blue screen.

Then

If you have the XP SP2 Security Update CD

Install symbols from <CD Drive Letter>:\\SUPPORT\\SYMBOLS

Download
http://www.microsoft.com/whdc/devto...installx86.mspx

Load the crash dump file into windbg (File - Load Crash Dump and it's in c:\\windows\\minidump) and READ WHAT IT SAYS, then
Type
!Analyze -v
into Windbg's command line. This should tell you the faulty component. As it seems this way is the most successful one.

I hope any of these will help. Good luck.

 

[Cyph3r]

Quote:

Originally Posted by hiKaRux3 Have you tried reinstalling Windows?

Yes I have =]

And thanks Wetall, thanks for taking the time to write that up for me, next time i get this error i'll follow your steps =]

 

[Nevaziah]

try underclocking your ram to 750 MHZ. I had somewhat the same problem with my DDR2-800 gskill NQs and it would crash randomly until i underclocked by 50MHZ

 

[weltall]

Quote:

Originally Posted by Cyph3r Yes I have =] And thanks Wetall, thanks for taking the time to write that up for me, next time i get this error i'll follow your steps =]

Your welcome. Glad I could assist a bit.

Quote:

Originally Posted by Nevaziah try underclocking your ram to 750 MHZ. I had somewhat the same problem with my DDR2-800 gskill NQs and it would crash randomly until i underclocked by 50MHZ

Shouldn't Memtest86 show that errors? Had the same problem with my ram that I OCed to 933 but memtest always shown me the errors, but they were not random they were always the same.

 

[Cyph3r]

well my ram was running @ 4-4-4-12 800mhz on 1.92v, and its supposed to run at like 5-5-5-15 800mhz on 2.1v, so i've tried upping the voltage.

 

[ericeod]

I had the same problem with my PC. It would give errors then shut down, or I would walk away for an hour or two and come back to find it had shut down. I ran every test including memtest and the WD data lifeguard tool, all teats past with flying colors. I even RMAed the motherboard! Well the new one did the same thing. The problem turned out to be not enough vcore. I previously ran orthos for 18 hrs with my E6600 at 1.21v @3.24GHz so I didnt suspect it was CPU stability. But raising the vcore up just one notch made the problem go away! It has been running 100% for over a month now.

 

[Cyph3r]

Ran memtest86 for 33mins and i didnt get any errors. any idea what else could be wrong?

 

[Cyph3r]

bump =[

 

[LB11]

Is everything running at stock speeds?

Set everything at stock speeds and see if it happens.

If it does then something is faulty. If not you are pushing something to far.

33 minuts is not long enough in memtest anyways. Let it run overnight.

 

[I Know Nothing]

Did you figure anything out with this? I'm having the same problem. Started right after I installed my new Opty 170. It did it once with everything stock but then was fine for the next few days. I oc'd it yesterday but left my RAM timings and vdimm alone and just setup the divider to run it at 186mhz (200 stock). I can't get 2 instances of Prime 95 to run and every time I download OCCT it ends up corrupted so used Orthos blend test for 8 hours with no problems and then 3dMark06 a few times right afterwards and it was fine. I haven't run memtest yet because I need to pull a floppy drive from one of my other rigs.