Bootup BSOD - CPU failure?

Page 1 of 2 12 LastLast

  1. Posts : 12
    Win XP Pro/Win 7 Pro
       #1

    Bootup BSOD - CPU failure?


    Problem:
    Win7 Pro 64-bit installed and worked perfectly for a week. Then it began giving me the occasional random BSOD on bootup until it eventually stopped booting at all. I tried recovering from the Win7 install disk but it gives me the same BSOD. Here is where it occurs:

    It boots from the disk and copies the files just fine


    Then the progress bar moves for a short time


    Then this:


    Troubleshooting:
    I ran several HDD tests (CHKDSK, Seatools, SpinRite 6) without a single error. I also tested the memory (memtest86 and windiag) but found no errors. I finally formatted the HDD for a fresh install and it still didn't work.

    I reinstalled XP Pro 32-bit and it has been working flawlessly for six months.

    Since then, I have systematically replaced the HDD, memory, DVD-ROM, PSU, and motherboard (going from a P35 to P45 chipset). I also tried three different video cards (1 ATI and 2 nVidia). The only thing I have not replaced is the CPU (e8400) because of the expense. None of these things fixed the problem.

    When I try to install, I disconnect all the peripherals and internal components not necessary for installation. I've tried a PS/2 keyboard with no USB devices connected. I tried the backup disk I got from MS instead of the ISO I downloaded (which is what I used to install in the first place). I've flashed to the latest BIOS. I've played with every BIOS setting I can think of that might be causing the problem. None of this works.

    Solutions?
    The only hardware I haven't tested is the CPU. XP 32-bit works fine but Win7 64-bit does not. Is it possible that a CPU could fail in a way that it will not run a 64-bit OS but will still run a 32-bit OS?

    It's got to be a hardware failure but I have never heard of a CPU acting this way. What else is there to try before replacing the CPU for an unlikely fix?

    Original setup:
    e8400
    Gigabyte P35-DS4
    4GB Corsair DDR2 800
    Seagate Barracuda 250GB
    Geforce 8800GT
    Antec Truepower 550W

    New setup:
    e8400 (same one)
    Gigabyte EP45-UD3P
    4GB Patriot DDR2 1066
    WD Black 500GB
    Radeon 4890
    Antec Truepower 750W

    EDIT: added hard drives to setups
    Last edited by rcjhood; 20 Apr 2010 at 09:41.
      My Computer


  2. Posts : 5,056
    Windows 7 x64 pro/ Windows 7 x86 Pro/ XP SP3 x86
       #2

    Stop error 7B means windows cant access the boot drive. Your chipset drivers/ storage drivers may be acting up or your hard drive may be failing. Though you did say, XP has been running fine for 6 months.

    Try updating your chipset drivers/ storage drivers. As a side note, does your bios have the option to switch from AHCI to IDE? I just remembered this because in XP, i used to occasionally come across this error and that was always because in the bios the drive mode had got toggled from IDE to AHCI.
      My Computer


  3. Posts : 12
    Win XP Pro/Win 7 Pro
    Thread Starter
       #3

    The SATA controller is set to IDE by default and AHCI does not work either.

    Are you talking about updating the windows drivers? I don't even have Win7 installed so I'm not sure how that would help install from the disk.

    What else could keep it from accessing the boot drive? I've tried two different cleanly formatted, error-free HDDs so it must be a problem in BIOS, no? But why would it have failed like it did, BSODing intermittently at first, then failing altogether?

    Should I scrounge up a PATA drive to try booting from?
      My Computer


  4. Posts : 236
    Win 7 64 bit professional
       #4

    Have you tried resetting the bios. Sometimes bios corruptions due to weak batteries etc. can be the problem. There are two steps that you can take.
    1) go into bios and set it to default.
    2) reset the bios on the motherboard using jumpers and temporarily removing the bios battery.
    If step 1 does not work, try step two.
      My Computer


  5. Posts : 12
    Win XP Pro/Win 7 Pro
    Thread Starter
       #5

    Yes I've reset the BIOS several times. The problem persists across different motherboards anyway.
      My Computer


  6. Posts : 12
    Win XP Pro/Win 7 Pro
    Thread Starter
       #6

    Anyone have a clue here? I am completely out of ideas at this point. I wonder of Microsoft could help...

    Also - when it BSODs before it's even installed, does it do a dump anywhere on the hard drive?
      My Computer


  7. Posts : 236
    Win 7 64 bit professional
       #7

    here is a long shot and I am reaching. Windows XP will not access your 4 GB of RAM, however Windows 7 64 bit will access all the RAM. It is possible that you have a bad stick of memory that is ignored by Windows XP but comes into play with Windows 7. Try removing two sticks in different combinations and see if that makes a difference.
      My Computer


  8. Posts : 12
    Win XP Pro/Win 7 Pro
    Thread Starter
       #8

    That's a good thought but I've already tried it. I tried each stick individually from both matched sets and in every slot. I've also tested them thoroughly with memtest and windiag. I'm pretty sure it's not the memory.
      My Computer


  9. Posts : 236
    Win 7 64 bit professional
       #9

    Another long shot-- have you tried underclocking your cpu or increasing your vcore and vdimm ?
      My Computer


  10. Posts : 12
    Win XP Pro/Win 7 Pro
    Thread Starter
       #10

    Nope, I'll give those a try. But if installing Windows 7 means that I have to underclock my CPU, I'm going to be pissed.
    Last edited by rcjhood; 24 Apr 2010 at 21:19.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:06.
Find Us