Built new computer, blue screen on startup

J

jameshooks

New Member
So I just built myself a computer for the first time, and I'd been running it for almost a week no problems. At this point it got some windows startup issue, which windows failed to repair, so i had to reinstalled everything (ugh). Now, only another 3 days or so later, the computer blue screens every time I start it up, right after the windows 7 logo.

specs:
evga x58 le mobo
6 gigs mushkin ram
intel i7 930 cpu
nvidia gtx 470 gpu
corsair HX 750watt psu

Any idea why this is happening? I sure as hell don't.
 
alright, after blue screening literally 8 times in a row my computer has now started up. sorry I never caught the error message, but while I have it running, is there a way to check what caused it? maybe a way to check to stability of the hardware or something i dunno.
 
sorry for the bump, but this same problem came back and i didn't want to bother with a new thread.

On startup, i get the blue screen with error code

"Stop: 0x0000001A (0x0000000000041790, 0xFFFFFA80014F20B0, 0x000000000000FFFF, 0x0000000000000000)"

I've found one guy with the same problem, his solution was to change the bios from supposedly unstable automatic settings to some more stable manual ones. How would i find these settings for my particular motherboard?, or is this even the problem?
 
Looks like a memory problem. Have you checked to make sure its running at its default speed/timing and voltage?
 
0x0000001A: MEMORY_MANAGEMENT
This memory management error is usually hardware related.

Have you run memtest on the memory? As StrangleHold rightly asks: What does the BIOS have the memory voltage set at and does it match Mushkin's voltage specs?

Have you tried running your system with 4 gigs?
 
k, so i check the bios, its running at 1.5v with target 1000ish target frequency. Which is wrong so I changed those to 1.65v and 1600hz.

But, now the computer just automatically goes into startup repair, checks for errors and says

"root cause found:

Boot critical file c:\windows\system32\drivers\fltmgr.sys is corrupt
repair action: file repair
result: failed. error code = 0x490"

suggestions?
 
No it wasn't, but I changed it. I still had that corrupt system filethough, so I just said f*&k it and reinstalled the system, I had a backup so I didn't lose my files. Making sure to backup a system image this time so I can just fix it pronto next time (though I hope there isn't a next time).

So, I've changed all my bios settings to the correct timings/voltage/speed, is it safe to say this won't happen to my computer again? or is there something else I need to change to make sure my memory is stable?
 
i have a similar problem same scenario build my computer, On startup the images that show on screen are scrambled though, then windows will start to load and a blue screen comes up but i can't read the code then it will restart with the images all clear after that happens??????? I have a 1090T black edition, 8GB of OCZ gold ddr3, and a gigabyte ga-890gpa-ud3h which has an onboard GPU that I'm using till I get a graphics card. I already updated all my hardware drivers and it still happens.
 
ive heard good things about mushkin, but never used it
if you're settings are right and memtest didnt show any problems then i dont see why it would come back
do you have enough virtual memory allotted in windows?
 
mitsman23 said:
i have a similar problem same scenario build my computer, On startup the images that show on screen are scrambled though, then windows will start to load and a blue screen comes up but i can't read the code then it will restart with the images all clear after that happens??????? I have a 1090T black edition, 8GB of OCZ gold ddr3, and a gigabyte ga-890gpa-ud3h which has an onboard GPU that I'm using till I get a graphics card. I already updated all my hardware drivers and it still happens.
Click to expand...

A lot of motherboards need the latest BIOS upgrade to run that chip. Have you done so?
 
I ended up dropping the voltage on my RAM in my BIOS to 1.45 volts instead of 1.5 volts so far it has not happened again and I've restarted several times since then. I haven't updated the BIOS yet but I should.
 
mitsman23 said:
I ended up dropping the voltage on my RAM in my BIOS to 1.45 volts instead of 1.5 volts so far it has not happened again and I've restarted several times since then. I haven't updated the BIOS yet but I should.
Click to expand...

My dropping the voltage on CPU and RAM did not work. So I'm going to try to find the most up to date BIOS I can and hope that it will fix my problem. Is there anyone that might be able to help me find the BIOS I'm looking on Gigabyte's site and see a bunch of different things i could download for my motherboard. The Model # is GA-890GPA-UD3H Rev-1.0. Any help at all is greatly appreciated.
 
I looked at the website for your motherboard and though they had BIOS updates under the Download Tab I didn't see anything for North America. I would contact Gigabyte via email tech support and ask them what BIOS you need to run this cppu.

Give them a brief description of what you are running into.
 
K just looked at ur boards specs, takes up to 6 dimms tri-channel
Are they installed correctly (2gb/ channel) and what mushkin ram are u using?
 
You must log in or register to reply here.
Back
Top