:help:
Hello!, I'm seeking some wisdom on a problem I have with my new system build.
Specs:
AMD64 3000+ with ChaintechNVF4
Kingmax SuperRAM 1Gb(2x512) PC3700
XFX 6600GT
WD 80Gb SATA, BenQ 16XDVDRW
Coolmax 400Watt PSU
Problem: When windows starts to boot a blue screen of death(BSOD) appears very fast(too fast to read) and the system reboots.
noTe: turned off DEP and was able to observe the BSOD, which spit MACHINE_CHECK_EXCEPTION.... blah... STOP:0x0000009C...etc.
Test/Observations: On my first install of WinXP on the new system I didn't notice this, wasn't paying attention. I only took it as far as the NVF4 drivers, at which point i decided to install WinXP again by using a floppy to load the IDE drivers and to use the newer drivers for all components. I also updated the BIOS to v.2.
The installation went flawless, booted to windows and installed the drivers for the NVF4. After the restart it gave me a BSOD at boot, which was too fast to read. I ignored the problem and continued with the rest of my system config, but the problem presisted as i kept restarting/shutdown. I decided to ignore the problem and started to use my system, I was able to use it normally(played HL2, DOOM3, with no problems), although it took a few tries to get windows to boot with out a BSOD.
I first decided to figure out what was wrong by going on the hunch that it might be the RAM, I tested the ram using Memtest86(ran it for 2 passes) and Prime95(1:30hours). The RAM passed both test. I didn't do an exhustive test because I though that if flaky RAM would crash the system at boot then it would probably crash very quick in a more intensive task. I then tried stoping the system from rebooting after the BSOD, so i could read the message but the setting had no effect. I then tried disabling DEP in the boot.ini to see if it would fix the BSOD, but instead it allowed me to read the BSOD...
At this point I noticed that it the error would happen about 99% of the time after a cold start, but happen less often when the system was rebooted.
After reviewing the BSOD i decided to reinstall WinXP again, didn't install by preloading drivers, install went well. Instead of rebooting I shutdown the system to test it out, the BSOD was a no show. I then istalled the NF4 drivers and restarted, again BSOD. I unistalled and installed the drivers one by one, and noticed that the error would only happen when I would install the IDE SW Drivers. I decided to try out various driver versions and system BIOS, combined in diffrent way they all produced the same result. Only BSOD with the install of the IDE SW Drivers. I also tried enabling/disabling various options in the BIOS, etc. I even moved the HD to various inputs, and moved the RAM around. Same result.
Conclusion:
Dunno what to do now? It seems like its a hardware issue and the specific hardware is the motherboard, but im not too sure? Could it still be the RAM? Something esle? Should I follow my idea to RMA the mobo?...any other thoughts?
THANKS for your time:beer:, sorry for the long post didnt want to leave out details. :bang:
Hello!, I'm seeking some wisdom on a problem I have with my new system build.
Specs:
AMD64 3000+ with ChaintechNVF4
Kingmax SuperRAM 1Gb(2x512) PC3700
XFX 6600GT
WD 80Gb SATA, BenQ 16XDVDRW
Coolmax 400Watt PSU
Problem: When windows starts to boot a blue screen of death(BSOD) appears very fast(too fast to read) and the system reboots.
noTe: turned off DEP and was able to observe the BSOD, which spit MACHINE_CHECK_EXCEPTION.... blah... STOP:0x0000009C...etc.
Test/Observations: On my first install of WinXP on the new system I didn't notice this, wasn't paying attention. I only took it as far as the NVF4 drivers, at which point i decided to install WinXP again by using a floppy to load the IDE drivers and to use the newer drivers for all components. I also updated the BIOS to v.2.
The installation went flawless, booted to windows and installed the drivers for the NVF4. After the restart it gave me a BSOD at boot, which was too fast to read. I ignored the problem and continued with the rest of my system config, but the problem presisted as i kept restarting/shutdown. I decided to ignore the problem and started to use my system, I was able to use it normally(played HL2, DOOM3, with no problems), although it took a few tries to get windows to boot with out a BSOD.
I first decided to figure out what was wrong by going on the hunch that it might be the RAM, I tested the ram using Memtest86(ran it for 2 passes) and Prime95(1:30hours). The RAM passed both test. I didn't do an exhustive test because I though that if flaky RAM would crash the system at boot then it would probably crash very quick in a more intensive task. I then tried stoping the system from rebooting after the BSOD, so i could read the message but the setting had no effect. I then tried disabling DEP in the boot.ini to see if it would fix the BSOD, but instead it allowed me to read the BSOD...
At this point I noticed that it the error would happen about 99% of the time after a cold start, but happen less often when the system was rebooted.After reviewing the BSOD i decided to reinstall WinXP again, didn't install by preloading drivers, install went well. Instead of rebooting I shutdown the system to test it out, the BSOD was a no show. I then istalled the NF4 drivers and restarted, again BSOD. I unistalled and installed the drivers one by one, and noticed that the error would only happen when I would install the IDE SW Drivers. I decided to try out various driver versions and system BIOS, combined in diffrent way they all produced the same result. Only BSOD with the install of the IDE SW Drivers. I also tried enabling/disabling various options in the BIOS, etc. I even moved the HD to various inputs, and moved the RAM around. Same result.
Conclusion:
Dunno what to do now? It seems like its a hardware issue and the specific hardware is the motherboard, but im not too sure? Could it still be the RAM? Something esle? Should I follow my idea to RMA the mobo?...any other thoughts?
THANKS for your time:beer:, sorry for the long post didnt want to leave out details. :bang:
Facebook
Twitter