Please help with new build

[bwatson283]

This may be long but please bear with me. I bought components to build a new pc, I have been building for more than 7 years now, and this one has me stumped.

I put everything together in this case, http://www.newegg.com/Product/Product.asp?Item=N82E16811133020 , everything went in fine and booted to Bios just with one tweak. Turning it on for the very first time I heard one long followed by 3 short beeps, which is a RAM issue. I had all 4 sticks of the RAM in there (4x1GB), so I just took the last stick out and it booted just fine.
Then, I prepped to install Windows. I decided to put the last stick back in and experiment, it booted fine with the stick in there now.

Windows installed FAST! Got to love x2! No errors during the install, it was a success. It was now time to install my apps. I installed the video, Chipset, and apps for the DVD ROM and DVDR ROM that I had brought from my old system. My DVD ROM is old school, A Pioneer slot loading. My DVDR is this http://www.newegg.com/Product/Product.asp?Item=N82E16827136105 .

The next morning is when the fun started. At this point is when everything started going downhill. After it sat idle for 8 hours while I sleep. My computer would stay in windows for about a max of 1 hour now, I started to encounter random reboots without the BSOD showing up. Within windows out of the 4x1GB sticks, it only read 3.5gb total, I took out the last stick out and it read the 3 gigs fine in windows. I have been running without the last stick from now on.
Late that afternoon, I read how to try and stop the auto reboots and SHOW the BSOD before I have to shut it off. I saw that it said something like Bad_??(Forgot)_Header. I was reading on the technet forums and found that some people where saying it was a issue with those LG drivers, and/or sp2 in general, or indexing service.

I uninstalled the software that I that was on the LG install cd. So it is just the windows DVD drivers running it now, it didn?t seem to affect me any differently now. The next few auto reboots didn?t have a BSOD, but the windows error report said that it was an video card issue. It was something along the lines of the video card got put into an indefinite hardware loop that crashes the system. The steps were:
-Update/Change the video drivers.
-Turn the hardware acceleration way down and/or turn off the Enable Write Combining.
-Replace the Card.
I had older nvidia drivers that I used, good thing I keep a lot of files for a long time, but it didn?t solve anything.
I replaced it with a general PCI card, and it was the same flippin issue, so video is out of the question.

So now I am thinking it is RAM or PSU. I have pumped up the volts on the RAM thinking that it wasn?t getting the power it needed. That didn?t seem to solve the issue.
Maybe the RAM is not fully compatible with the board????

The Reboots are still happening, any ideas?????


I bought this CPU
http://www.newegg.com/Product/Product.asp?Item=N82E16819103759

This PSU
http://www.newegg.com/Product/Product.asp?Item=N82E16817153036

This Motherboard
http://www.newegg.com/Product/Product.asp?Item=N82E16813131593

This RAM
http://www.newegg.com/Product/Product.asp?Item=N82E16820227139

These HD?s
http://www.newegg.com/Product/Product.asp?Item=N82E16822148149

This Video Card
http://www.newegg.com/Product/Product.asp?Item=N82E16814150216

 

[mechBgon]

If you haven't tried 2.1 volts on that RAM yet, try that. And/or try Memtest86+ from http://www.memtest86.com before and after the voltage change to see whether it's having memory errors.

 

[bwatson283]

I did pump up volts to 2.00 and it didn't fix the issue, my board wouldn't let me take it to 2.1. Memtest didn't find any issues with the sticks, so the RAM work ok itself. Maybe it is not 100% compatible to the new Crosshair board, when the RAM and the video and CPU all work in conjunction.

 

[sieistganzfett]

Hi, win xp 32 bit will only let you use 3gb, the 4th gb is useless pretty much. Memtest passed just once, or were you willing to let it run for 2+ passes? (I let it run through test 5 a couple times, or just let it do all tests for 24 hours, but rarely will memory fail after even just one pass, but I have seen it happen and it took 3 or more passes to show the ram was bad.) is all of the settings in the bios at the defaults by the way? you dont need to start pumping up the voltages past what the ocz says, does ocz say that ram supports that board (i'm sure it does support it, so i don't think that could be why) if everything on the bios is at the defaults, you tried a pci video card and you cut down to just your OS hard drive (unless your doing raid) and only 1 stick of ram, disconnect any external drives, and troubleshoot from there with just the basics going into windows, disable all your un-needed things from starting up via msconfig too.

Sounds like you already did disable the ?automatically restart? option on system failure, under the settings for the ?startup and recovery?, (system properties, advanced tab, to get to this), that?s a good start.

To find out whats going on in more detail, use windows debugger, I think you can really benefit if you use this to see if there is a relationship of any kind between your large amount of minidumps that are now available on the pc under the windows minidump directory. If the errors are random, then its probably hardware, but if its almost always or always the same driver, just update that.

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Most of the time installed Windows Debugger, and using it to check the dump file will tell why windows crashed. after installing run !analyze -v and lmv commands to find out what did it.
**** after dbg_x86_6.6.07.5.exe installed, open windbg, set FILE|symbol file path to click "reload" box, then ok.
SRV*c:\local cache*http://msdl.microsoft.com/download/symbols

**** then file|open crash dump and run the commands

!analyze -v will tell you the error, click the link on the drive
under Debugging Details:
DEFAULT_BUCKET_ID -tells the general category of the failure
IMAGE_NAME -tells what driver is at fault, like if DRIVER_FAULT
click on the driver highlighted under MODULE_NAME it tells info like path to that module

lmv -tells loaded modules in detail, then click edit|find for that driver listed under IMAGE_NAME


****IF
*if driver at fault is ntoskrl.exe (windows core) or win32.sys (driver most responsible for the GUI layer on windows),it is PROBABLY NOT WINDOWS needing to be reinstalled, it is PROBABLY some third-party device driver that called it.
*if the driver at fault is an antivirus driver, it is PROBABLY NOT the anti virus needing to be reinstalled.
*

 

[patentman]

Originally posted by: sieistganzfett
Hi, win xp 32 bit will only let you use 3gb, the 4th gb is useless pretty much.

While I understand that this is an allocation problem inherent to a 32 bit OS, the 4th GB definitely does something. My computer runs worlds better with the 4th GB in then without it. I don;t know what the extra RAM is being used for, but whatever it is its resulting in a noticeable improvement.