BSOD associated with Bios version

Page 1 of 2 12 LastLast

  1. Posts : 32
    WIN 7 Ultimate x64
       #1

    BSOD associated with Bios version


    New build, new parts, less than two months. Seems like years. Just kidding, but it has taken a lot of my time.

    GA P55A UD3P ver 1, i5 760, 8 GB Rip Jaw, Self installed Win 7 Ultimate 64 bit OEM, Radeon HD 5550 graphics. Mobo came with F5 bios. Not overclocked. Drivers updated to Gigabytes latest.

    Bios F5 works good. Also F10.

    Latest bios is F14. I can sometimes run with this bios
    but eventually I get a BSOD. It seems to happen on
    cold boots after a long cool down.
    It starts up, gets to blue windows start screen, goes to black then flashes BSOD (to fast to read) then begins a restart and continues cycling.

    I have tried the other bios's between F10 and F14. All have the same issue.
    Been backing up with Aconis so I have images of various states to play with. Went back to the clean install and F14 bios will BSOD there too, eventualy if not immediately.

    I do need help
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Your dump file is corrupt, could you try again :)
      My Computer


  3. Posts : 32
    WIN 7 Ultimate x64
    Thread Starter
       #3

    yowanvista said:
    Your dump file is corrupt, could you try again :)
    Certainly will resend. But the way I do this is to crash the computer with the F14 bios. Then install the F10 bios so I can recover the dump files and send them to you. Is this method OK?

    Thanks for the quick attention.
      My Computer


  4. Posts : 32
    WIN 7 Ultimate x64
    Thread Starter
       #4

    jokdom said:
    yowanvista said:
    Your dump file is corrupt, could you try again :)
    Certainly will resend. But the way I do this is to crash the computer with the F14 bios. Then install the F10 bios so I can recover the dump files and send them to you. Is this method OK?

    Thanks for the quick attention.

    Induced bsod again with F14 bios. Went to safe mode.
    Ran bsod application in admin mode. Just another bsod and reboot.
    Flashed bios to F10. Got the data and am sending it as
    BSOD_DATA2. Also sending first BESOD_DATA again.

    Hope this helps.
      My Computer


  5. Posts : 32
    WIN 7 Ultimate x64
    Thread Starter
       #5

    jokdom said:
    jokdom said:
    yowanvista said:
    Your dump file is corrupt, could you try again :)
    Certainly will resend. But the way I do this is to crash the computer with the F14 bios. Then install the F10 bios so I can recover the dump files and send them to you. Is this method OK?

    Thanks for the quick attention.

    Induced bsod again with F14 bios. Went to safe mode.
    Ran bsod application in admin mode. Just another bsod and reboot.
    Flashed bios to F10. Got the data and am sending it as
    BSOD_DATA2. Also sending first BESOD_DATA again.

    Hope this helps.
    Trying to send attachments.
      My Computer


  6. Posts : 32
    WIN 7 Ultimate x64
    Thread Starter
       #6

    WOOPS!!
    Spoke too soon. Have now had a bsod, during a long idle, with F10 bios.
    The only bios I have run with and not had a bsod is F5.
    F5 has run for weeks.
      My Computer


  7. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #7

    You are getting the stop 0x124 error, Seems a hardware component is faulty, read this for more information: Stop 0x124 - what it means and what to try
    Code:
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN
    
    BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN
      My Computer


  8. Posts : 32
    WIN 7 Ultimate x64
    Thread Starter
       #8

    Thanks yownavista.

    Could it also mean a bad motherboard or can I rule that out as the problem?

    I have pretty much done all the things recommended in the procedure
    you pointed to. Specially the clean install phase.

    I will proceed with stressing components in hopes of getting more data or clues. I have allready denuded the system of all unnecessary hardware.

    Thanks for your help and fast response.

    Cheers
      My Computer


  9. Posts : 32
    WIN 7 Ultimate x64
    Thread Starter
       #9

    More data and a puzzling discovery.

    I can not change Memory or Voltage parameters in any Gigabyte bios version for this mobo.

    I have disabled the board passwords.

    I can change Advanced Bios Settings and Advanced Peripheral Settings.

    Gigabyte tech service are dragging their feet. They give advice like "Look for short circuits". When I told them I could not set Memory
    values they responded "Try setting Command rate to 2 and set a lower memory voltage". Sheeeese!! I wish I could.

    Does anyone know or can they suggest a way to set this bios?
    A few days ago I could change CAS latency, tRCD, tRP and tRAS.
    By the time I got to Command Rate I could not change it to 2. It is frozen at 1.

    I did not realize until several days later that I could not change any Memory or Voltage setting.

    I have taken the CMOS battery out for an hour. When I put it back in and boot into bios setup, I reset the things I can but still can not change Memory or Voltage settings.

    Am I doing or not doing something to cause this?
    Or do I have a bad board?
      My Computer


  10. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #10

    By the time I got to Command Rate I could not change it to 2. It is frozen at 1
    Either its a problem with the board or with the RAM

    RAM - Test with Memtest86+


    RMA the board if it is still under warranty
      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:44.
Find Us