Also I had some crashes because of ipv6 stack installed in windows xp 64 bit.
I know the ipv6 stack is not reliable and can crash the computer.
I don't know if it's a windows xp 64 bit bug or if it's a network chip driver bug... or maybe even hardware bug.
It could be that some software was left over after removing the ipv6 stack...
But the last time I removed it everything seemed to work ok afterwards...
But the ipv6 stack stuff is definetly suspicious as well as the network drivers/chips.
However this does not explain the hang in memtest... unless maybe memtest had some weird bug... but that's too far fetched that everything is bugged.. and the time was weird... and then there were reboot issue's...
Maybe all the crashes I had the last year just screwed the hardware...
I have at least 20 minidumps or so just from the last year or so... so maybe random software crashes could just be bad for hardware for some reason. Like maybe suddenly loss of airflow or so.
Especially during high cpu activity or gaming activity right before the crash.
The cpu was hot... the gpu was hot... the fans were spinning fast... then suddenly a software crash happens...
A minidump is made...
The system resets/reboots.
The fans first spinning slowly... then later shortly spinning fast.. then later spinning slowly again.
Maybe a sudden build up of heat could occur.
It's a far fetched/wacky explanation.. but maybe this is the problem...
Most likely is just overheat in general...
Let's hope it's just overheat in general because that should be an easy problem to solve... if it's anything else then ouch nasty problem ;)
Bye, Skybuck.