Random BSOD code 124

Hello every one!
The last mont I am facing a serious problem with random BSOD's with the following details:

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.
Locale ID: 1032

Extra information about the problem
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8009C62028
BCP3: 00000000F2000000
BCP4: 000000000020008F
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

My set up is:
M/B: Gigabyte GA-P55A-UD5 rev. 1
Memory: Corsair 4X2GB modules CMX4GX3M2A1600C9
Processor: Intel i7 860 @ 2.80
Bios ver.: F13b (latest beta posted on the official site)
PSU: Corsair TX 750 (750W) enthusiast series
Video card: Sapphire HD 5870 1GB vram running with the latest drivers form ati (12.2 preview driver)
Sound: on board realtek running R2.67 driver
OS: windows 7 64bit
Disk drives: 1. WESTERN DIGITAL Velociraptor 150GB WD1500HLFS, 2. WESTERN DIGITAL 250GB WD2500YS, both set up to run in AHCI mode with the drivers provided from gigabyte using the intel driver and rapid storage technology GUI.
Mouse & keyboard combo: Logitech LX 710 laser with the latest drivers from the official site v.5.33.14

I do not OC. The bios has the default settings. What I have changed does not affect OC (logo on startup etc)
This happens randomly. I play Battlefield 3 only and it happens while i play and while on desktop doing nothing.
I recently formatted all my HDDs and performed a clean install. Five minutes after the new installation (no drivers loaded by me) and i had a BSOD.

Note: before the format the HDDs where setup as IDE. After the format I changed to AHCI. BSODs happen in both.

I asked for a new vbios from sapphire but they did not give me one.
I am pretty desperate for a solution.
I have searched a lot and did not come up with a a working solution.
I am attaching my minidumps in case someone can read them because i cannot.
Any help would be appreciated.

Minidump files: minidmp.zip - 45 KB
27 answers Last reply
More about random bsod code
  1. Welcome to Tom's Forum! :)

    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Probably caused by : hardware

    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Probably caused by : hardware

    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Probably caused by : hardware


    Assuming the IDE -> AHCI as cause, BIOS change back to IDE if BSOD persists then change the following registries, change both Start values to 0 (zero):

    Boot into the BIOS, change SATA -> AHCI, Save and Exit = Yes

    IF you can boot into Windows as AHCI then either change the above registry values or use 'Fix It' -> http://support.microsoft.com/kb/922976

    Otherwise you need to disconnect ALL of the attached hardware (USB, USB Headers, etc), including a different keyboard then boot to see if the error is gone. IF yes then (1) at a time start adding stuff. I've seen it all, so even the cases' USB front panel can use this.
  2. I noticed your other thread -> http://forums.tweaktown.com/gigabyte/47794-problem-random-bsod-code-124-a.html

    It's not the DRAM Voltage or QPI/VTT since as you said it's running Defaults. The RAM at Default is 1.50v NOT 1.65v.

    Question, what changes have you made to your system? Have you tried a Restore Point prior to the problem?


    You 'can' try to to re-install ntoskrnl.exe, hal.dll, PSHED.dll
    1. re-install - http://answers.microsoft.com/en-us/windows/forum/windows_7-system/no-boot-windows-7-error-ntoskrnlexe-is-missing-or/bed3d422-57d2-477e-bc41-db456e9533cf
    2. SFC - http://answers.microsoft.com/en-us/windows/forum/windows_7-system/error-psheddll-has-been-deleted-or-is-corrupted-on/6ddaaeec-bea1-4ff6-987c-72b06fd23c07
  3. I use my computer sin 01/2010 without any problems. Only the past couple of months i started having problems.
    I don't know why but i suspect the realtek driver or chip causing the problem. I think my first bsod happened when i updated this driver with a newer one from gigabyte, had a lot of bsods and then rolled back and all was working fine up to certain point.
    The only change that i made was to put an extra 4gb of ddr. i do not know if this is responsible for my bsods. the only thing that i changed in bios a couple of times was XMP and i changed it back after a while because i noticed that the processor speed does not drop when idle when using XMP.
    Other than that i do not mess with voltages because i know they cause problems.
    I just tried the suggestions that you might have seen in my other post.
    :sweat: :sweat: :sweat:
  4. In the Device Manager are there any {? or !} listed devices?

    If an onboard chipset is messed-up there's little that can be done except to 'try' to right-click Disable and see if that solves the problem. Your dump file didn't list any 'specific' HW. I've seen AV apps cause ntoskrnl.exe failures.

    The simplest thing to do IMO:
    1. Run SFC (first option) -> http://i1013.photobucket.com/albums/af254/Jaquith/Scan-Drives-Windows-7.jpg
    2. Run MSCONFIG select Diagnostic and see if any changes
    3. Besides disconnecting peripheral hardware as stated above, Disable some onboard controllers, boot and test.

    IF there was a Vendor code in the dump then it would be a lot easier to detect.

    My 'typical' solution to Windoze is the re-install it than wasting a lot of time and ending-up doing it anyway...
  5. My av is eset smart security all settings defaults.
    In the device manager all is ok. In the bios i have disabled all controllers not used, IDE, Marvell chip, eSata. The only one enabled is AHCI mode.
    This the reason why i re-installed windows 7 but my first bsod happened in the first 10minutes of using the new installation and with no drivers loaded by me, only the ones windows installs by itself.
    Another thing that i have tried prior to format was this: http://forums.electronicarts.co.uk/battlefield-3/1455182-fix-battlefield-3-bad-company-2-realtek-bsod.html
    But it did not help.
  6. If you think it's the Realtek then Disable and get ANY sound card, they all are better.

    Did you verify the (2) registry values I posted above? They ARE required to avoid BSOD from AHCI.
  7. I checked the registry settings and the msahci was already 0 but the iastorv was set to 3. i run fix it and now is set to 0.
    I agree about realtek.
    I am really grateful for your help.
  8. "iastorv was set to 3" = IDE, and will indeed cause Random BSOD's...test now (reboot) and see if the BSOD is resolved.
  9. Thank you very much for your advice.
    I changed it to 0 and now I will see how it goes and report back.
  10. Good Luck! :)
  11. Hello again.
    After a lot of searching and testing today I had another bsod while playing BF3.
    jaquith can you please see if there is anything new or interesting in the minidump?
    Thanks in advance!

    030912-12464-01.zip - 22 KB
  12. Nope, looks like the same issue:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

    Unable to load image PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll

    Probably caused by : hardware


    If this is happening during BF3 then you might want to contact the GPU vendor and see if they're running across this issue.
  13. First of all thank you very very much for your time and for the immediate reply!
    Searching the action center of win7 i also found this:


    Video hardware error

    ‎9/‎3/‎2012 21:31

    Not reported

    A problem with your video hardware caused Windows to stop working correctly.

    Problem signature
    Problem Event Name: LiveKernelEvent
    OS Version: 6.1.7601.
    Locale ID: 1032

    Extra information about the problem
    BCCode: 117
    BCP1: FFFFFA8006FD7380
    BCP2: FFFFF88004A078B8
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Any suggestions?
  14. and another bsod!
  15. Good thread on ASACPI.sys - http://www.sevenforums.com/crashes-debugging/97709-blue-screen-win7-bccode-117-a-2.html

    Also, a 'beta' BIOS can be the root issue, try rolling back (i.e. re-flash) to F12. Newer, isn't always better and that goes for beta GPU drivers; use validated WHQL drivers if possible not ati (12.2 preview driver)
  16. I had the same problems with the previous official bios.
    I even got a bsod trying to enter safe mode.
    I am confused and very very upset. I don't know what to do!
  17. What about the GPU drivers? IMO use the WHQL driver.
  18. Hello.
    Last night I reset my CMOS, flashed back to F12, reset my cmos again, customized ram and voltage settings, installed the newest official drivers from ati (12.2).
    I will see................!
  19. I will ........... hope!
  20. As far as asacpi.sys is concerned i read the thread but i cannot find the file in my system32 folder. Since it is for asus do I need it? My m/b is gigabyte.
  21. No need unless you are still having problems.
  22. Hello again. After almost two months of running smoothly last couple of weeks I started having the same problems again. Can anyone PLEASE read the minidumps and tell me what they point to?
    Thanks in advance.
    minidumps.rar - 41 KB
  23. it seems like your CPU/GPU has failed;
    you are getting 0x124 and 117 right? 0x124 is a CPU failure blue screen
    0x117 or 0x116 is your GPU failure;

    and looks like your CPU has a built in GPU;
  24. After a lot of testing of trial and error and a lot of hardware combinations I found out that for a strange and unknown reason my system runs trouble free (no bsods at all!) using only 4 gb of ram (the original sticks that i bought the system with and is included in the gigabyte qvl list).
    Any ideas or suggestions are welcome!
  25. I think I finally found the problem.
    I set DRAM to 1.5v and qpi/vtt to 1.34v and all looks good up to now.
    I had to fine tune the motherboard because it was an older model than the vengeance ram.
    Thank you all.
  26. I am back.
    After all this time the problem came back.
    A. I will buy a new mono
    B. I will buy a new VGA card
    C. I will mess with the voltages a little more
    I wanted to flip a coin but it has only two sides and I don't know the correct voltage levels so that I don't fry anything.
    Any suggestion would be highly appreciated.
Ask a new question

Read More

Gigabyte Blue Screen Motherboards