BSOD running direct x10 and 11 games.


  1. Posts : 5
    Windows 7 home premium 64 bit
       #1

    BSOD running direct x10 and 11 games.


    Hey everyone, I've just bought my first pc pre-built and I'm having some BSOD issues while running games in directx10 and 11. I first had this problem when I was playing Civilization V in direct x 10-11 mode. After switching to direct x 9 the BSOD'es stopped. Then when I played Saints row the third in direct x 10-11 the same problem happened. Any information about my problem would be great!

    Bit of background info:
    I'm currently running a watercooled AMD Phenom x4 955 Black edition over clocked to 3.6ghz.
    My graphics card is an nvidia geforce GTX 480 and my pc has 8gb of ram.

    I've attached my crash reports and hope that you can help, thanks!

    If you need any more information, please ask.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hello isuckatusername.

    Update the BIOS. It is needed there.
    Code:
    BiosVersion = F4G
    BiosReleaseDate = 05/22/2009
    Get the BIOS Version F9b dated 2012/08/14; from GIGABYTE - Motherboard - Socket AM3 - GA-MA790XT-UD4P (rev. 1.0) . You may try @BIOS to update the BIOS. It is safe and secured way to do it.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the wattage of your PSU.
    ______________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8007e75028, b66b4000, 135}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8007e75028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b66b4000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  CivilizationV_
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`02f6ca88 fffff800`02e14a3b : 00000000`00000124 00000000`00000000 fffffa80`07e75028 00000000`b66b4000 : nt!KeBugCheckEx
    fffff880`02f6ca90 fffff800`02fd7443 : 00000000`00000001 fffffa80`07e76d30 00000000`00000000 fffffa80`07e76d80 : hal!HalBugCheckSystem+0x1e3
    fffff880`02f6cad0 fffff800`02e14700 : 00000000`00000728 fffffa80`07e76d30 fffff880`02f6ce30 00000000`00d7e300 : nt!WheaReportHwError+0x263
    fffff880`02f6cb30 fffff800`02e14052 : fffffa80`07e76d30 fffff880`02f6ce30 fffffa80`07e76d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02f6cc80 fffff800`02e07e8f : 00000000`00000000 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02f6ccc0 fffff800`02ebf4ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`02f6ccf0 fffff800`02ebf353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`02f6ce30 00000000`00526920 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0e091820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x526920
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 5
    Windows 7 home premium 64 bit
    Thread Starter
       #3

    Arc said:
    Hello isuckatusername.

    Update the BIOS. It is needed there.
    Code:
    BiosVersion = F4G
    BiosReleaseDate = 05/22/2009
    Get the BIOS Version F9b dated 2012/08/14; from GIGABYTE - Motherboard - Socket AM3 - GA-MA790XT-UD4P (rev. 1.0) . You may try @BIOS to update the BIOS. It is safe and secured way to do it.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the wattage of your PSU.
    ______________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8007e75028, b66b4000, 135}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8007e75028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b66b4000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  CivilizationV_
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`02f6ca88 fffff800`02e14a3b : 00000000`00000124 00000000`00000000 fffffa80`07e75028 00000000`b66b4000 : nt!KeBugCheckEx
    fffff880`02f6ca90 fffff800`02fd7443 : 00000000`00000001 fffffa80`07e76d30 00000000`00000000 fffffa80`07e76d80 : hal!HalBugCheckSystem+0x1e3
    fffff880`02f6cad0 fffff800`02e14700 : 00000000`00000728 fffffa80`07e76d30 fffff880`02f6ce30 00000000`00d7e300 : nt!WheaReportHwError+0x263
    fffff880`02f6cb30 fffff800`02e14052 : fffffa80`07e76d30 fffff880`02f6ce30 fffffa80`07e76d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02f6cc80 fffff800`02e07e8f : 00000000`00000000 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02f6ccc0 fffff800`02ebf4ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`02f6ccf0 fffff800`02ebf353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`02f6ce30 00000000`00526920 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`0e091820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x526920
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
    Thanks for replying. I've already had prime 95 run a stress test on my CPU and it returned no errors. After a BSOD occurs, the pc's temp is around 61-65 degrees, however the tj max of my processor is only 70 degrees. I will update the bios and run the other tests.
      My Computer


  4. Posts : 5
    Windows 7 home premium 64 bit
    Thread Starter
       #4

    After updating my bios using the method you said, my computer now finds a floppy disc drive in A:. I don't have a floppy disk drive, any help?
      My Computer


  5. Posts : 5
    Windows 7 home premium 64 bit
    Thread Starter
       #5

    isuckatusername said:
    After updating my bios using the method you said, my computer now finds a floppy disc drive in A:. I don't have a floppy disk drive, any help?
    Solved this by disabling the floppy drive in the BIOS.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Any more BSODs there?
      My Computer


  7. Posts : 5
    Windows 7 home premium 64 bit
    Thread Starter
       #7

    Arc said:
    Any more BSODs there?
    I recently had one on saints row the third in directx 9 mode which means that it can't be directx10-11 causing em, however that was before the bios update, not sure if that will change anything.
    I ran that gpu stress test and had no problems, the temp levelled out at 81C which is apparently good for a gtx 480. One thing i did notice is that the GPU never went to 100% load, only 99%, no idea what that could mean.
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Ok, now wait and observe how it is running :)
      My Computer


 

  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 19:53.
Find Us