...ok I get a BSOD PAGE_FAULT ....error stop (0x50 code) when i put in 2 x 1G of pc26400C4DHX corsair RAM...now in this scenario, i could boot into safe mode w/networking. i take a stick out, (1 x 1G ) i could boot into normal mode...i am new to forums, infact this is my 1st one...i tried a lot of things and i will list everything i tried...
i have a EVGA 750I FTW MOBO
Q6600 w/ 2 x 1G corsair PC6400DHX mem 2.1v (dual channel)
Nvidia Palit 9600GT (1)
Real Power Pro 750 SLi PSU
THermalright ultra 120 extreme w/ s-flex 1600rpm
thermaltake M9 tower
AIrlink101 Super G wireless adapter
WD 160G SATA HDD and FIreball 20G--dual bootable
i have no XP Pro SP2 repair CD... i followed advice online on how to take
XP PRO on the FIreball lct20G off an old computer and stick in new hardware ...by erasing all the drivers and creating a hardware profile that is blank...i know i know, changing MOBO's need a reinstall but...like Admiral AKbar says, "We have no choice"...
...now when i changed it over to the new computer, it didn't boot up except in safe mode w/ networking (with both sticks of RAM) upon giving up after calling EVGA 20 times
(If anyone of you work for EVGA, you know who i am) i decided to check the RAM sticks by...trying both each stick individually...it worked, booting into normal mode, 1 each...then i put 1 into each slot...it worked.. then i ran bootable MEMTEST86 +...both sticks passed individually and them both together.
..not booting into normal mode means, it BSOD's after loading the drivers and after the Login page is up for 11 seconds (logging in and not logging-in is the same) i attempted to debug with windbg and symbols...
and i have 20 .dmp files ... could attach 1 to anyone who wants it !
1. i flashed the BIOS to e175_sz17..no change
2. i turned off BIOS cacheable...no change
3. i reset CMOS no change
4. loaded default settings no change
5. i optimized settings ...no change
6. i set 800 mhz for RAM, raised volt to spec 2.1v and raised NB and CPU volts no change
B4 i RMA the MOBO( memory controller)... it could still be the RAM and/or XP drivers/stability... debugging :::the driver that cant be listed probably due to ntoskrnl.exe file::::
before i get new RAM, there is got to be a way to rule out driver conflict
because XP didnt recognize ACPI multiproc until i changed the HAL.DLL, ntoskrnl.exe, and ntlmpna.exe filesi have got to see if there are other wacky driver or registry/memory reference problems or bolder voltage/other settings