BSOD on startup of multiple games, error 0x00000101

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Ultimate x64
       #1

    BSOD on startup of multiple games, error 0x00000101


    Every time that I try to open certain games I get an instant crash that only sometimes shows the BSOD. Other times it just drops and comes back on. These games include Serious Sam 3, Saints Row 3, and Lord of the Rings: War of the North. I never even get to see a logo or a menu, the game never quite opens.

    The diagnostic report is attached with my username as the .zip name.

    EDIT: I do not overclock, and seeing as it is on start up of these games I don't believe it is a heat issue.
      My Computer


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

    Fenrira said:
    EDIT: I do not overclock, and seeing as it is on start up of these games I don't believe it is a heat issue.
    Your CPU information:
    Code:
    AMD FX(tm)-8120 Eight-Core Processor, 3100 Mhz, 4 Core(s), 8 Logical Processor(s)
    But it actually says:
    Code:
    0: kd> !sysinfo cpuinfo
    [CPU Information]
    ~MHz = REG_DWORD 3332
    Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
    Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
    Identifier = REG_SZ AMD64 Family 21 Model 1 Stepping 2
    ProcessorNameString = REG_SZ AMD FX(tm)-8120 Eight-Core Processor           
    VendorIdentifier = REG_SZ AuthenticAMD
    So apparently it is appearing that the system is overclocked. It is running on more megahertz than stock.

    As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    You may not believe that it is a heat related issue, but as the computer is years old, we need to check the heat, as the bugcheck codes are mostly stop 0x124 and sometimes stop 0x101. 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. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    NETGEAR WG111v3 Wireless-G USB Adapter driver is failing here.
    Code:
    fffff880`09f41b08  fffff880`05d8349eUnable to load image \SystemRoot\system32\DRIVERS\wg111v3.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for wg111v3.sys
    *** ERROR: Module load completed but symbols could not be loaded for wg111v3.sys
     wg111v3+0xc49e
    And the driver is too old.
    Code:
    fffff880`05d77000 fffff880`05def000   wg111v3  T (no symbols)           
        Loaded symbol image file: wg111v3.sys
        Image path: \SystemRoot\system32\DRIVERS\wg111v3.sys
        Image name: wg111v3.sys
        Timestamp:        Wed Nov 18 15:17:46 2009 (4B03C2C2)
        CheckSum:         0007A170
        ImageSize:        00078000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    For an online game, it is enough reason for an instant BSOD.

    Update the driver from WG111v3 . If there is no feasible driver update available, better you opt to use another adapter with an up-to-date driver.

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

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    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.
    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Let us know the results.
    ________________________________________________________________________________________
    Code:
    BugCheck 124, {0, fffffa80071da8f8, 0, 0}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    --------------------------------------------------------------
    BugCheck 101, {19, 0, fffff88002fd7180, 3}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thank you for responding.

    I did my best to get an updated driver/software for my wireless adapter (I was not running the actual software before), and it seems that the driver is still showing the same date that you had shown in your reply. However, I play many other games, especially online games such as League of Legends and my wireless adapter (or anything) has never caused a BSOD when playing. I would also like to clarify that I ONLY get BSODS when starting up these three games, and I have rarely seen another one under any other circumstances, much less a recurring BSOD like this one.

    fffff880`05d77000 fffff880`05def000 wg111v3 T (no symbols)
    Loaded symbol image file: wg111v3.sys
    Image path: \SystemRoot\system32\DRIVERS\wg111v3.sys
    Image name: wg111v3.sys
    Timestamp: Wed Nov 18 15:17:46 2009 (4B03C2C2)
    CheckSum: 0007A170
    ImageSize: 00078000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

    I ran a memory test and got 0 errors after 8 passes. (Also, my RAM is 1866 MHz default, but my motherboard sets it to 1600MHz, not sure if this is relevant, but information can't hurt)

    I tried to set all the clock values back to default, but I may have already done so after I posted my diagnostic report since I was trying trying to explore the problem myself. The overclocking section in my BIOS is disabled. If my processor is still running overclocked, than I am not sure how to fix that.

    I ran a video stress test through Furmark and my GPU's temperature went up and then fluctuated between 77C - 79C. No BSODS. I wasn't quite sure how long I was supposed to run this test, but I assumed that once the temperature wasn't changing that it should be enough.

    Speccy screenshot shows some reasonable idle temps (this was actually taken shortly after stress testing the GPU, and the GPU was already back down to 52C, it normally idles around 50C). It also shows 799MHz on my RAM, it seems a lot of different frequencies correspond to my RAM and I am growing suspicious of it.

    I will be running the CPU test soon and will post the results.

    Thanks again for your time.
      My Computer


  4. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #4

    CPU stress test ran for 2 hours and 20 minutes with no BSOD or errors.
      My Computer


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

    If you cannot get an up-to-date driver for your device, I would suggest you to test the situation with another device/connection.
      My Computer


  6. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #6

    I booted my computer without my wireless adapter plugged in, started steam in offline mode, and then tried to play serious sam. It still crashed when opening the game.
      My Computer


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

    Fenrira said:
    I booted my computer without my wireless adapter plugged in, started steam in offline mode, and then tried to play serious sam. It still crashed when opening the game.
    Post it following the Blue Screen of Death (BSOD) Posting Instructions.
      My Computer


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

    Here it is.
      My Computer


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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa80071eb8f8, 0, 0}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    4: 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: fffffa80071eb8f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, 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:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`033705b0 fffff800`03327ca9 : fffffa80`071eb8d0 fffffa80`06a56040 fffffa80`069641a0 fffff880`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03370ad0 fffff800`03208ea7 : fffffa80`071eb8d0 fffff800`032822d8 fffffa80`06a56040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03370b00 fffff800`03170275 : fffff800`032e3b40 00000000`00000001 fffffa80`069c3e50 fffffa80`06a56040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03370b40 fffff800`030e6261 : fffff800`03282200 fffff800`03170250 fffffa80`06a56000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03370b70 fffff800`033792ea : 00000000`00000000 fffffa80`06a56040 00000000`00000080 fffffa80`069f75f0 : nt!ExpWorkerThread+0x111
    fffff880`03370c00 fffff800`030cd8e6 : fffff880`0316d180 fffffa80`06a56040 fffff880`031780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03370c40 00000000`00000000 : fffff880`03371000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------
    Follow it: Stop 0x124 - what it means and what to try
      My Computer


  10. Posts : 7
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Thank you very much.
    I updated my BIOS to the most recent and now Serious Sam works.
    I am currently installing one of the other two games that would cause crashes on start-up, and if it works then I will mark this as solved.
      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 20:18.
Find Us