Hi all
if you can fix this, you are GOOD. a lot of forums and computer shop people don't know what's wrong, but maybe you can help!

system: Windows XP 32-bit Pro (all updates till december 2008) (and dual boot with openSuse 11.0)
HDD: 320GB S-ATA samsung spinpoint
CPU: AMD Athlon x64 5200+
mobo: ASUS M2N (standard)
GPU: nvidia geforce 8500 GT
mem: 2+1 GB Apacer CL.5 DDR2 RAM

problem:[/b]
when using windows, my pc often freezes and requires reboot. It's very weird though: when a browser window is active, things like javascript countdown timers KEEP GOING and when i minimize an application, it WORKS or when i single click on a desktop icon it TURNS BLUE but when i try to open anything, click anything, maximize any window or do anything else, i get an hourglass mouse pointer and from that moment on i can do NOTHING but move my mouse. my pc is STUCK and i have to reboot.

That's not so bad when it happens once in a month, but this happens every day a few times now, somtimes even when only botting windows! (hangs during load screen. the progress bar keeps going but no progress is made).
another weird thing is that my little red light on my case that starts burning/flickering when you pc is 'working hard' goes completely black. normally it flickers at least every 2 or 3 seconds when my pc is idle, to burning for whole seconds when loading a big program. when my pc crashes in it's weird way, the light won't go on anymore.

Some people said it has to do something with my RAM. they told me to unplug the socket, press power button a few times, then replug the socket and boot. that worked the first TIME! i was able to continue for a few months, then BAM it hit me again. they then told me to also remove my RAM during the mentioned process, and that worked too, but again, after a month, it happened AGAIN. sad thing is, NOTHING works anymore, wether i remove the RAM or not.

Another strange thing: THIS DOESN'T HAPPEN ON LINUX! i have opensuse 11.0 and it never had any problems with it! so i thought "oh well a bad windows install" but NO: i installed 3 or 4 different xp versions now and none worked all gave me the same crash in the end.

FAILED solutions:
-memtest86+ to check RAM
-remove a RAM unit (i have 2 so i removed 1 and tested the other and vice versa, didnt make any difference)
-HDD check
-unplug socket and press power button etc.
-flash BIOS
-reïnstall windows
-reformat HDD
-update drivers
-... maybe some more i can't remember right now

PLEASE if you are able to help, do it, because i need it badly school year's end is near and if i don't have my pc available for my final tests... >.>

THANK YOU

Joris
Windows uses RAM differently from Linux, so I don't believe you have completely eliminated RAM issues. Is trying some other brand RAM an option?
Quote from: Dias de verano on May 10, 2009, 01:05:10 PM

Windows uses RAM differently from Linux, so I don't believe you have completely eliminated RAM issues. Is trying some other brand RAM an option?

Just noticed you've got 32 bit Windows on 64 bit hardware. Hardware driver issues could be a factor.

1. wouldn't driver issues cause constant trouble? (my system used to work fine for periods of like 3 months+)
2. im 99% sure my chipset driver cd includes 32-bit versions... or doesn't that matter?

I arranged some DDR2 units with a friend. if they work for a week (or 2 if he can miss them) i will post here, if not im gonna be here sooner, and try to find out more about driver issues.

thanks for your devotion

I'm not sure, but when I put "works fine in Linux, but windows crashes" into Google, I came across a thread where the Windows was 32 bit on 64 bit hardware, and I think there was a driver implicated.

what exactly do you mean by implicated?

Check the manual for your MB and get approved RAM for it.

Sometimes the 64 bit boards crash for no reason when using RAM that has not been approved for the MB

and: my brand of RAM (Apacer) is not in the qualified vendors list, but that shouldn't always cause trouble, should it...

Not always, but it is quite possible, and if it does, you only have yourself to blame. I found this out the hard way with a Shuttle barebones kit: Those lists exist for a reason.