OMG hate this!

HaX

[H]ard|Gawd
Joined
Dec 17, 2005
Messages
1,916
I'm helping a buddy out with his new desktop that he built, but the thing is a nightmare. First off, here's his setup:

CPU: Intel Core 2 Duo E7500
Motherboard: Foxconn ELA
Memory: Kingston ValueRam 2GB (2x 1GB) DDR2 - 667
Hard Drive: WD Caviar 80GB Sata
Video Card: XFX Radeon HD 4770
PSU: Corsair 550 watt

Here's the story, Computer was built and then it was time to install the OS. We decided to install windows 7, it installed and then after we installed the updates and video drivers, upon after rebooting and logging in, in the desktop environment after a min it'll blue screen or gray screen. shitty, so if i boot into safe mode works fine.. leads me to be a driver issue.. but after any sort of updated driver i go through still does the same thing. It was such a pain in the ass that I said screw windows 7 and lets put vista on it. After installing vista it was working fine for a little while. Blue screened once... not sure what the problem was then. But after realizing there's a newer bios update for the motherboard decided to give it a whirl, and give windows 7 another try.

After installing the bios update, I tried installing windows 7, during the windows 7 setup screen it blue screened on me.. i was like WTF. I threw the installation disc across the room. Tried vista, it installed, but in the desktop environment it blue screens... wtf is the dealio... i've never had a problem like this in a long time... and it's been too long since i've built a desktop myself.. all i remember from building my own desktop is that I never had problems like this before.
 
Dude,

Just calm down. Take everything out except basic components then start trouble shooting. My guess is you have a bad RAM stick. Start there by testing one at a time.
 
Did you try memtest for a couple of loops?

Also, whats the code of the BSOD?
 
If the BIOS offers an extensive self test, I'd kick it off and see what it says. It could be memory, or perhaps a bad drive eating data, etc. Proper troubleshooting would isolate components, but I'm usually too impatient to do it properly.
 
No RageQuitting just yet.

PSU, Mobo, CPU, 1 stick o Ram, HDD, DVD/CD. That's it, nothing more, nothing less. Boot, format, install. Update OS, reboot. Stable? Cool. Update BIOS. Stable? Cool. Install video card. Let Windows recognize. Stable? Cool. Install drivers. Reboot. Stable? Cool. Now start adding in everything else you will be using. If it still BSOD's, try a different stick o Ram. Still having problems? Try another HDD.

If all else fails, RageQuit and get started on an i7 build.
 
No RageQuitting just yet.

PSU, Mobo, CPU, 1 stick o Ram, HDD, DVD/CD. That's it, nothing more, nothing less. Boot, format, install. Update OS, reboot. Stable? Cool. Update BIOS. Stable? Cool. Install video card. Let Windows recognize. Stable? Cool. Install drivers. Reboot. Stable? Cool. Now start adding in everything else you will be using. If it still BSOD's, try a different stick o Ram. Still having problems? Try another HDD.

If all else fails, RageQuit and get started on an i7 build.

lol i like that idea
 
maybe it's foxconn..i had bad luck with them in the past

Foxconn is the OEM for a lot of major brands, Intel included. I doubt its a quality issue. Could be a bad board just as any board could be bad, but them being "foxconn" isnt the issue.

Windows 7 will outperform vista in every case. I would never go back to vista even in the event of an issue like that.

Do some troubleshooting, and I am sure you will find out theres an issue with your memory or possibly your video card, considering you got a gray screen.
 
I had similar issues with an i5 build i just did for a friend. install would be ok then intermittent blue screens, grey screens, sometimes it would boot sometimes it wouldnt. ended up being the ram. did some googling to confirm people just had issues with this one set of OCZ stuff and a specific mobo. replaced ram, everything was good.
 
Normally, intermittant blue screen on a new build is memory.

Maybe going back to the basics will help.

Take the MB out. Reset the CMOS.
MB + HSF + one stick of RAM+ GPU.
POST to BIOS.
Update BIOS to latest revision.

Plug in HDD + DVD.
Repost.
If everything is OK............load up W7 to a reformatted HDD.

If everything is OK.......load all drivers.
Still OK, update and activate W7.

Now power down and trade out RAM............test each stick.
 
well... as far as memory goes... didn't have any other to test for known good ones.. but i ran memtest and windows memory diagnostic on it.. came back with no errors.
 
first.. we need the code.. or text that comes up in the BSOD.. because it can lead to exactly what the issue is.. for example.. if it said machine exception error.. then its just a simple raising of the cpu voltage and boom problem fixed..

second.. id recommend pulling the cmos battery out and unplugging the psu for 30-45 seconds.. which will reset the bios.. then boot up and see what happens.. if it screws up again.. go into the bios and set the bios to optimized default.. try again.. its all a process of elimination at this point.. though being that it is a foxconn motherboard i really wouldnt trust the bios being setup up correctly at default anyways..

also being that the system is using DDR2 667 and not 800.. go in the bios and make sure its setting the ram at 667 and at the correct voltage and not ddr2 800 just in case..
 
well i tried removing the battery and using the optimized default option in the bios and still same issue. as for the bsod code... it flashes for like a split second and disapears.. and unable to read it. cpu isn't being overclocked or anything and all the settings in the bios are set to default, same for memory.
 
Hit F8 just after the POST to get the advanced startup options (Safe Mode, etc). Then choose Disable automatic restart on system failure.

Linky
 
well... one blue screen during vista desktop environment gave me:

win32k.sys
page_fault_in_nonpaged_area

****Stop: 0x00000050 (0xC2C95E5F, 0x00000000, 0x8FD11DBC, 0X00000002)

Other one upon installing windows 7:

just says generic windows has detected a problem and has shut down to prevent damage

***Stop: 0X0000007F (0x0000000000000008, 0x0000000008005003, 0x00000000000006F8, 0xFFFFF8000D16780A)

well... i've tried known working video card and memory... im pretty sure it's the stupid motherboard...
 
Here's the Microsoft KB on your stop error: http://support.microsoft.com/kb/137539

It's RAM or the MB.

Make sure the RAM voltage is correct and that it's set right for 667 and not set to 800......

If you have the CPU at stock, the FSB may be too much for the RAM clocks......you may need to reset the FSB to RAM timings to correct that.
 
i've tried using DDR2 800 though also... im pretty sure it's not memory.. i checked the voltages and seems to be ok
 
If changing the RAM doesn't help, then I'd almost guarantee it's a faulty system board.

Yup................or the CPU is not seated correctly............you might want to remove the HSF, reseat the CPU, and reapply the paste.
 
I am gonna save you some trouble

reseat all of your ram. I had the same thing happen to be and I reseated all of my ram and the issue never came back.
 
HaX said:
well... as far as memory goes... didn't have any other to test for known good ones.. but i ran memtest and windows memory diagnostic on it.. came back with no errors.
I've said it before, but try more diagnostics, like MemTest86 ver. 3.x, Gold Memory 6.92, and Gold Memory 5.07. I've never had an error reported by MemTest+ or Gold Memory 6.92, not because they're inferior to their siblings, MemTest86 v. 3.x and Gold Memory 5.07, but probably because they use the memory differently (and I'm sure the opposite has been true for other users).

I've also said that if the memory module has a higher than normal voltage rating (1.80V for DDR2, 1.50V for DDR3), then the chips failed at normal voltage.
 
Back
Top