BSOD During Shogun 2 Loader


  1. Posts : 8
    Winsows 7 Ultimate x64
       #1

    BSOD During Shogun 2 Loader


    Hi there, I just built myself a custom computer last weekend (all parts are brand new) and it is crashing every time I try to load Shogun 2.
    My OS is:
    Windows 7 Ultimate 64 bit retail purchased reinstalled once after reformatting *crash occurred before reformatting as well as after.

    System specs are:

    System Manufacturer/Model Number: FA-990FXA-UD5
    CPU: AMD FX(tm)-6100 Six-Core Processor, 3300 Mhz
    Motherboard: Gigabyte AMD3+ FX
    Memory: G. Skill Ripjaws Series DDR3 1600Mhz (2x4GB)
    Power Supply: Corsair Builder Series CX600 V2 600 Watt
    Case: iCAN A9809 Mid Tower Gaming
    Graphics Card: AMD Radeon HD 6850

    Thanks so much for the help.
    Last edited by RobertCharles; 14 Nov 2011 at 18:41.
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    There are three main errors I see in your logs. Starting with least severe and moving on:

    Most likely unrelated to your BSODs, I see this:
    Code:
    Event[135]:
      Log Name: System
      Source: Service Control Manager
      Date: 2011-11-13T19:18:20.167
      Event ID: 7000
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Rob-PC
      Description: 
    The 7ByteIo service failed to start due to the following error: 
    The system cannot find the file specified.
    You may consider uninstalling Hot CPU Tester and see of anything changes.

    Next:
    Code:
    Event[548]:
      Log Name: System
      Source: atapi
      Date: 2011-11-13T17:49:28.209
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Rob-PC
      Description: 
    The driver detected a controller error on \Device\Ide\IdePort2.
    Check your hard drive with SeaTools: SeaTools for Windows | Seagate

    Finally, the probable cause of the BSODs:
    Code:
    Event[208]:
      Log Name: System
      Source: Microsoft-Windows-WHEA-Logger
      Date: 2011-11-13T18:39:54.263
      Event ID: 18
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-19
      User Name: NT AUTHORITY\LOCAL SERVICE
      Computer: Rob-PC
      Description: 
    A fatal hardware error has occurred.
    
    Reported by component: Processor Core
    Error Source: Machine Check Exception
    Error Type: Bus/Interconnect Error
    Processor ID: 0
    
    The details view of this entry contains further information.
    This is related to the 0x124 bugcheck, a processor error. It's not necessarily a physical CPU issue (RAM, motherboard, PSU, and BIOS are also possible), but given the error found in the event log, we can say it's probably either the CPU or motherboard. Run each of the three Prime95 tests: Hardware - Stress Test With Prime95

    It's up to you, you might skip the Prime95 and move directly to the RMA. Even if Prime95 comes up clean, I won't be convinced that neither component is the cause.

    ...Summary of the dumps:
    Code:
    
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sun Nov 13 21:35:07.061 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:12.216
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Sun Nov 13 21:39:35.624 2011 (UTC - 5:00)
    System Uptime: 0 days 0:00:11.779
    Probably caused by : hardware
    BUGCHECK_STR:  0x124_AuthenticAMD
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  3. Posts : 8
    Winsows 7 Ultimate x64
    Thread Starter
       #3

    Great advice, I have tried running Prima95 but only the first test nothing showed up after 14 hours but given that each test takes so long I think I will just go ahead and return it instead of running more/longer tests. Really appreciate the help in narrowing down the possible causes, thought for sure it was the graphics card after the Prima95 and memtest86 tests turned up with no errors. This has been a big headache but great learning experience.

    All the best,
    Robert
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #4

    What is the make and model of your power supply? There's a small chance that bad/insufficient power is causing the problem.

    FYI - no need to run the Prime95 tests for too long. The test will run indefinitely, but typically, we see results within 15-30 minutes. I said 2 hours in the Prime95 guide just to play things safe.
      My Computer


  5. Posts : 8
    Winsows 7 Ultimate x64
    Thread Starter
       #5

    The power supply is Corsair Builder Series CX600 V2 600 Watt 80 Plus Certified. (CMPSU-600CXV2)

    Good to know I heard from other sites that Prima95 should be run all night. I'll give the other two tests a quick go then.

    Thanks
    Last edited by RobertCharles; 14 Nov 2011 at 21:24.
      My Computer


  6. Posts : 8
    Winsows 7 Ultimate x64
    Thread Starter
       #6

    Just ran the second and third Prima95 tests for over 30 minutes each and got no errors. I also ran Driver Varifier and it caused a memory dump, I was told that might indicate why it's crashing. Here's the mini dump file it created in case that tells you anything.
    Last edited by RobertCharles; 14 Nov 2011 at 23:28.
      My Computer


  7. Posts : 13,354
    Windows 7 Professional x64
       #7

    I don't *think* this can explain those hardware errors, but I could be wrong and it's worth addressing anyway. The crash dump pointed to gdrv.sys, a driver for Gigabyte EasySaver. That program has been known to cause crashes before, so definitely uninstall it and see what happens.

    ...Summary of the dumps:
    Code:
    
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Mon Nov 14 22:19:42.165 2011 (UTC - 5:00)
    System Uptime: 0 days 0:01:06.336
    *** WARNING: Unable to verify timestamp for gdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
    Probably caused by : gdrv.sys ( gdrv+1809 )
    BUGCHECK_STR:  0xc4_f6
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  MiniWERServer.
    FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_gdrv+1809
    BiosReleaseDate = 10/13/2011
    SystemProductName = GA-990FXA-UD5
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      My Computer


  8. Posts : 8
    Winsows 7 Ultimate x64
    Thread Starter
       #8

    Uninstalltion didn't fix the problem unfortinatly looks like I will have to go the RMA route after all. Thanks a lot for the help.
      My Computer


  9. Posts : 13,354
    Windows 7 Professional x64
       #9

    Oh well, keep us posted!
      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 06:39.
Find Us