Something wrong with my XP computer

F

flazh

Weaksauce
Joined
Feb 19, 2007
Messages
123
I just build a new computer a couple months ago, and I installed XP and Vista (dual boot) just fine.

A week ago, I have a problem with XP, it just shut down and restart on me with out any BSOD msg. when it came back online, Microsoft reported that it is a driver issue. Doesn't tell which driver and I'm not sure myself. Before it shut down, the video I was watching went on a "loop mode" in less than 1 sec interval, so it making a weird sound. Anyways. It didn't happen before. I'm having a dual boot (Vista) and it never happen to Vista, but again I don't spent much time with my Vista, but I think it is OK ( I hope so).

This is my spec: mobo 680i SLI 122-CK-NF68 A1, E4300 (Overclocked to 2.3Ghz), Raptor X, 7600GT, crucial ballistix tracer PC-8500 2GB.

History of the intallation:
I installed XP and the XP chip set from the EVGA and it works just fine, but, when I installed Vista I also installed the vista chip set from the EVGA, somehow it made the Vista unstable (hiccups), so I reinstalled vista without using EVGA chipset, and it looks like vista recognized it just fine.

Any idea what might cause this? could it be the chip set? something that I do wrong on setting up the mobo maybe? HD issue? memory? I checked the HD and memory before and it's fine. Could be that it is my video card? I checked the device manager, there is nothing wrong. I hope this is the right place to ask.
 
E4300 at 2.3 GHz? Seems like an oddball overclock to me considering the "pad mod" would/should be easy and it'll push it to a solid 2.4 GHz natively. Interesting...

Obviously one would first suggest you put everything in the machine back to factory defaults, aka stop overclocking and see if the results and the BSODs keep happening. If so, then it's more than likely a software issue that's developed for whatever reason - driver corruption, Registry issues, etc. It could be a ton of different things that all combine to create the problem, or it could be one specific thing that does it all by itself.

Try setting everything back to defaults for a day or so and see what happens.
 
Yeah I did that on purpose, but I don't think it is the overclock that caused this, but either way I already set it up back to default, well at least that's what I can do for now, considering I'm not sure which component/device should be disabled/tested.

The thing is, this is happening randomly, I don't know what I did or the computer did to replicate the problem, it happened twice already. I remember the first occurrence was a day after I installed windows update (around 1 or 2 weeks ago), security updates.
 
There have been a lot of reports floating around of late that the last batch of Windows Updates "broke" something for a lot of people. I've had a bunch of people on IRC where I hang out in some XP support channels complain about recent rashes of BSOD activity and they all say it happened "after I hit Windows Update." It's not scientific when one or two people say something like that, but when 35 people in a single day give you that response, something's up.

I'm not sure what "broke" recently as I haven't had problems, but then again I don't hit Windows Update that often - with XP x64 the updates aren't nearly as frequent as with XP 32 bit are.

If I come across anything more useful I'll post it here.
 
That's good to know, well if this happen again I will revert back to my back up image from last month.
 
You may have already done this, but make sure you've unchecked "Automatically restart" under the "Startup and Recovery" tab on your System Properties. If this is checked, you may be missing a blue screen you would otherwise be getting.
 
You must log in or register to reply here.
Back
Top