BSOD issues when trying to fresh install

Page 1 of 2 12 LastLast

  1. Posts : 5
    Windows 7 Professional
       #1

    BSOD issues when trying to fresh install


    Hello everyone,

    I am experiencing some problems with my computer and in a desperate attempt to figure out the problem before I purchase a new computer I am hoping someone can shed some light on my situation.

    All of a sudden one last week I had some problems opening up notepad++ so I uninstalled and reinstalled then restarted hoping that would resolve the situation. However, upon rebooting the pc I was given a BSOD error. I was at this point able to get into windows safe mode in where I managed to back up critical data and then went on to attempt some fixes:

    At this stage I tried:

    CHKDSK (which would not schedule, because as soon as the computer restarted the BSOD would appear)

    Windows recovery (attempted several times but on restart totally locked up on loading windows, however safe mode accessible still)

    Registry clean

    Clean boot (again wouldn't work due to the BSOD)

    As a last resort I tried to reinstall windows although this just BSOD when attempting to install, I also tried installing my old version of XP to see if this made any difference, but same problem.

    I was unable to access the BIOS settings either as this would just lock up when trying to get in so after attempting to solve this by clearing the cmos with no avail I decided it must be the motherboard so I purchased a new one along with a new SSD.

    After setting up the new motherboard and drive I am now able to access the BIOS without problem. Temps look good but when trying to boot windows 7 install (and XP) same problem, excot windows just hangs on the loading windows after one spin of the windows circle logo it just freezes otherwise it produces the BSOD (see error code below)

    I have now tried the following:

    1) memtest ran for 10 cycles overnight 0 errors
    2) tried to boot up ubantu some kind of kernel panic error (see attached SS)
    3) disconnected everything apart from essentials (one ram, no gpu, with and without fans etc)
    4) disconnected front panel usb and hd audio to see if the usb head is causing the issue
    5) tried my old psu to see if the psu was causing the problem
    6) tried different cables from my current psu
    7) purchased a cheap keyboard to see if that was causing the problem

    I am not sure what direction to head now other than go and buy a new case ram and cpu.

    Ubantu screenshot:




    Windows 7 code on install attempt:

    0x00000124 0x000000000000000xfffff 0xfffffa8006b9d0281 0x00000000fe200000 0x000000000005110a


    Please note: there is no windows install on the new drive I cannot post dmp files as their is no operating system installation to get them from.
      My Computer


  2. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #2

    0x124 is a hardware error, but without having an OS installed it's virtually impossible to even start figuring out which compenent it is. Unfortunately it's going to be trial and error on your part. My first suggestion would be to hook up a spare HDD and see if Windows will install on that to rule out your current HDD.
      My Computer


  3. Posts : 5
    Windows 7 Professional
    Thread Starter
       #3

    Did you even read my post?
      My Computer


  4. Posts : 26,863
    Windows 11 Pro
       #4

    In your screenshot the last line is shutting down CPU with NMI. From what I can find NMI is a memory parity check. And yes, I read your post and know you ran memtest. I would go into bios and set optimized defaults and try and see if you have PCI in your bios to disable it. see if that makes it any different. PCI in bios is sometimes called parity check.
      My Computer


  5. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #5

    I will admit to speed reading the OP as I was at work with not much time. I'll also admit to having no inclination to read it in its entirety now either.
      My Computer


  6. Posts : 5
    Windows 7 Professional
    Thread Starter
       #6

    Boozad said:
    I will admit to speed reading the OP as I was at work with not much time. I'll also admit to having no inclination to read it in its entirety now either.
    Yet, you had ample time to write that completely pointless reply?
      My Computer


  7. Posts : 5
    Windows 7 Professional
    Thread Starter
       #7

    essenbe said:
    In your screenshot the last line is shutting down CPU with NMI. From what I can find NMI is a memory parity check. And yes, I read your post and know you ran memtest. I would go into bios and set optimized defaults and try and see if you have PCI in your bios to disable it. see if that makes it any different. PCI in bios is sometimes called parity check.
    Any idea where to find that in the BIOS? My motherboard is a asus P8 z77 lx. I can't see any options other than PCIe settings and PCIe x16
      My Computer


  8. Posts : 26,863
    Windows 11 Pro
       #8

    You may not have that option. Some boards don't. I'm not sure but I believe it has to do with server grade ram, which many boards don't use. but some do.
      My Computer


  9. Posts : 12
    Windows 7 Home Premium 64-bit
       #9

    BSOD Code 124 is normally from vCore being too low. Load your optimized defaults and increase your vCore just a little bit and remember to keep an eye on your temperatures.
      My Computer


  10. Posts : 5
    Windows 7 Professional
    Thread Starter
       #10

    Replaced cpu problem is now fixed
      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 10:07.
Find Us