Strange but consistent BSOD

Hi, I'm in need of a little help. I've recently completed my first build and I'm somewhat of a novice.
My set up is i7-930, Gigabyte x58-ud3r v2, 6G of Corsair ddr3-1333 TR3X6G1333C9, Evga superclocked GTS 450, 1TB WD Cavier Blue and an LG 22x DVD burner all powered by an Antec EA650.

My problem is that I'm getting a BSOD whenever my computer has been turned off (still plugged in and receiving power) for a long period of time (3-4+ hours). The crash always occurs when it attempts to load Windows 7 (Ultimate64). The blue screen flashes too quickly for me to make out what the error codes are. However, after attempting start-up repair a few times, it will eventually load into Windows.

Anyway, here's the minidump error information:

110710-22510-01.dmp 11/7/2010 7:53:32 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00041790 fffffa80`0466fc50 00000000`0000ffff 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+70740 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16617 (win7_gdr.100618-1621) x64 C:\Windows\Minidump\110710-22510-01.dmp 8 15 7600

I should also add that once I get it to start up, restarting or starting after a shorter period of time (1-3 hours or so) of being off is fine. I also have had no trouble once it gets going, it's never crashed once I've gotten into Windows on anything.

I've run memtest86+ for several hours/seven passes and it came up with zero errors across the board. I've also run Windows Memory Diagnostic a few times with no errors as well. I've attempted a fresh install with Windows 7 and have no non-essential hardware installed.

Any help on what may be the cause would be appreciated.
4 answers Last reply
More about strange consistent bsod
  1. Could be caused by any number of things. I would start by checking the following in this order:

    Memory- run memtest testing the memory in ALL configurations, individual sticks in different slots and then adding sticks as you go.

    Video and sound drivers- make sure all are up to date. Don't forget to erase the forceware leftovers from your registry (from safe mode using driver sweeper or something similar) before installing new forceware.

    Anti-Virus program uninstall and reinstall.

    A quick check of the web shows this problem popping up quite a bit. Never had the problem though. --> knocks on wood.
  2. Ok, I've run every diagnostic for every piece of hardware in all configurations and I've yet to uncover a hardware error/problem. I've also procured a couple other legit Windows 7 dvd's to install from and test.

    I have had a crash for every start up of Windows 7 64 bit (Ultimate and Home Premium tested) after 6 hours or so of the computer being off since I built the system.
    The 32 bit Home Premium version of 7 is 3 for 3 with successful (no crash) start ups regardless of the time off.

    I suspect a driver issue since I'm not having problems on 32 bit version of windows but as far as I'm able to tell, I have updated all mobo drivers, gpu drivers, dvd and hdd drivers.

    Thanks for the help....
  3. Ok, in further update, I've successfully booted the system into 64 bit from cold boot state with a 2 gig stick of ram in slots 1, 3, and 5 respectively of the mobo, 4 gigs (2x2gigs) in slots 1-3 and 1-5, and 6 gigs in slots 1-2-3.
    When I try slots 1-3-5 I get a crash.

    Windows 64 bit system recognized 6 gigs when I had it in slots 1-2-3.
    I think I can rule out RAM problems and move onto something to do with the motherboard.

    Is there anything in the bios that I'm not configuring correctly or something I should know for why I can't put 6 gigs on one memory controller with an i7-930?

    Please help!
  4. As an update, since I desperately tried to find an answer to this problem and never did...I RMA'd the mobo and got a new one. It had the same problems and I discovered that this sort of issue is common to gigabyte mobos. I RMA'd and got an Asus P6X58D-E and no more crashes.
    If you're having the issue, it seems like the board wants specific ram, even if you're using good ram, and there's no way to fix the issue without replacing either your mobo or your ram at this point. I spent a month trying just about every other option and nothing worked. RMA and move on....
Ask a new question

Read More

Homebuilt Blue Screen Systems