Windows 8 and 8.1 Forums


Multiple BSOD playing Call of Duty: BO3

  1. #1


    Posts : 52
    Microsoft Windows 8.1 Pro 64-bit 9600 Multiprocessor Free

    Multiple BSOD playing Call of Duty: BO3


    Ever since I've started playing Call of Duty: Black Ops 3 on my computer I've been experiencing BSOD. The BSOD errors I've experienced are: DRIVER_IRQL_NOT_LESS_OR_EQUAL, DRIVER_OVERRAN_STACK_BUFFER, MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION, and possibly others that I'm forgetting.

    I ran memtest86 for 18 passes and it returned no errors for my RAM. I upgraded to windows 10 and the BSOD and computer crashes seemed to increase. I downgraded back to windows 8.1 pro and did a clean install. I'm still getting BSOD but they seem to be happening slightly less frequently, but it still makes it very annoying when trying to play games. Right now the only things I have installed are steam, geforce, COD: BO3, and some drivers for my graphics card and drivers so I can use a PS3 controller with steam.

    I am running a genuine copy of windows. Here are my computer specifications.

    processor: Intel(R) Core(TM) i5 CPU, 760 @ 2.80GHz, 2.40GHz
    Installed memory (RAM): 8.00 GB
    system type: 64-bit Operating System, x64 based-processor
    Operating System: Windows 8.1 Pro
    Video Card: NVIDIA GeForce GTX 570

    I have uploaded the zip file with the memory dump.

    Thanks in advance for your help.

      My System SpecsSystem Spec

  2. #2


    Posts : 660
    windows 8.1


    3 of 5 dumpfiles have:
    Code:
      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: ffffe00001932028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  f
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
    STACK_TEXT:  
    fffff804`007cca38 fffff803`ff5c7cdf : 00000000`00000124 00000000`00000000 ffffe000`01930028 00000000`be000000 : nt!KeBugCheckEx
    fffff804`007cca40 fffff803`fefc8cf1 : 00000000`00000001 ffffe000`00164090 ffffe000`00164090 ffffe000`01930028 : hal!HalBugCheckSystem+0xcf
    fffff804`007cca80 fffff803`ff5c816c : 00000000`00000728 00000000`00000000 fffff804`007cce70 00000000`00000000 : nt!WheaReportHwError+0x22d
    fffff804`007ccae0 fffff803`ff5c84d9 : ffffe000`00000010 ffffe000`00164090 fffff804`007ccc88 ffffe000`00164090 : hal!HalpMcaReportError+0x50
    fffff804`007ccc30 fffff803`ff5c83c4 : ffffe000`00161ad0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
    fffff804`007ccc80 fffff803`ff5c860e : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
    fffff804`007cccc0 fffff803`ff5c878f : ffffe000`00161ad0 fffff804`007ccef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    fffff804`007cccf0 fffff803`fef697bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff804`007ccd20 fffff803`fef69571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    fffff804`007cce60 fffff800`00ecb1ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    fffff804`007b7510 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fwpkclnt!FwpsNetBufferListRetrieveContext0+0x2a
    Usual causes: Hardware, Incompatibility, May be driver corruption

    1 dumpfile has:
    Code:
      
    BugCheck D1, {ffffffffffffffe1, 2, 1, fffff80002464b84}
    *** WARNING: Unable to verify timestamp for e1i63x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1i63x64.sys
    Probably caused by : e1i63x64.sys ( e1i63x64+25b84 )
    Usual causes: Device driver
    e1i63x64.sys Driver Description: Intel(R) Gigabit Adapter NDIS 6.x driverDriver Update Site: https://downloadcenter.intel.com/
    Update to a windows 8.1 compatible driver, if there are no windows 8.1 driver this intel gigabit adapter may not be compatible and the 3 WHEA_UNCORRECTABLE_ERROR (124) BSOD could point to this device.

    The last one was:
    Code:
    BugCheck 3B, {c0000005, fffff80191a5043e, ffffd000259d6b00, 0}
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseAllocation+5a )
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80191a5043e, Address of the instruction which caused the bugcheck
    Arg3: ffffd000259d6b00, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Usual causes: System service, Device driver, graphics driver, ?memory
    This could point to DirectX. Did you already update all the windows updates because this also updates directX.
    Check if your Call of Duty Black OPs DVD or Download has a DirectX folder and update to this version.
      My System SpecsSystem Spec

  3. #3



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    The 0x124 are persistent in the problem, an internal error. Looks like the cache on core 5 timed out.
    This could be due to a driver problem, possibly some outdated drivers.
    Please update the Creative drivers/software, there are many drivers of Creative outdated.
    Code:
    0: kd> !errrec ffffe0000187f028
    ===============================================================================
    Common Platform Error Record @ ffffe0000187f028
    -------------------------------------------------------------------------------
    Record Id     : 01d13d378409d2d2
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 12/23/2015 4:50:01 (UTC)
    Flags         : 0x00000000
    
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0000187f0a8
    Section       @ ffffe0000187f180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000106e5
    Processor ID  : 0x0000000000000000
    
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0000187f0f0
    Section       @ ffffe0000187f240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : e5 06 01 00 00 08 10 00 - fd e3 98 00 ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    
    Proc. Info 0  @ ffffe0000187f240
    
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0000187f138
    Section       @ ffffe0000187f2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Error         : Internal timer (Proc 0 Bank 5)
      Status      : 0xbe00000000800400
      Address     : 0x00003800011411ea
      Misc.       : 0x0000000000007fff
    Regarding the 0x3B:
    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Attachment 66760
      My System SpecsSystem Spec

  4. #4


    Quote Originally Posted by axe0 View Post
    The 0x124 are persistent in the problem, an internal error. Looks like the cache on core 5 timed out.
    This could be due to a driver problem, possibly some outdated drivers.
    Hmm.
    Internal timer errors, in my experience, are usually CPU dependent, and thus are caused by a faulty CPU itself.
    It is very rare that such is caused by a driver.
    Atop of this, a cache doesn't simply timeout. The error is caused by an internal timer mechanism failing, which we cannot interpret. (The documentation isn't released, closed source).
      My System SpecsSystem Spec

  5. #5



    BSOD Kernel Dump Analyst
    Posts : 2,274
    Windows 10 Pro


    I know, it isn't 100% correct, but I'm fortunately still learning
      My System SpecsSystem Spec

  6. #6


    Posts : 52
    Microsoft Windows 8.1 Pro 64-bit 9600 Multiprocessor Free


    Quote Originally Posted by axe0 View Post
    The 0x124 are persistent in the problem, an internal error. Looks like the cache on core 5 timed out.
    This could be due to a driver problem, possibly some outdated drivers.
    Please update the Creative drivers/software, there are many drivers of Creative outdated.
    Code:
    0: kd> !errrec ffffe0000187f028
    ===============================================================================
    Common Platform Error Record @ ffffe0000187f028
    -------------------------------------------------------------------------------
    Record Id     : 01d13d378409d2d2
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 12/23/2015 4:50:01 (UTC)
    Flags         : 0x00000000
    
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0000187f0a8
    Section       @ ffffe0000187f180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000106e5
    Processor ID  : 0x0000000000000000
    
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0000187f0f0
    Section       @ ffffe0000187f240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : e5 06 01 00 00 08 10 00 - fd e3 98 00 ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    
    Proc. Info 0  @ ffffe0000187f240
    
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe0000187f138
    Section       @ ffffe0000187f2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    
    Error         : Internal timer (Proc 0 Bank 5)
      Status      : 0xbe00000000800400
      Address     : 0x00003800011411ea
      Misc.       : 0x0000000000007fff
    Regarding the 0x3B:
    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Attachment 66760

    So I got the Physx driver but I'm not entirely sure if I found the right graphics driver. I searched "NVIDIA graphics driver windows 8.1 64-bit" in google and got this "http://www.nvidia.com/object/notebook-win8-preview-64bit-326.01-whql-driver.html" but it doesn't say what video cards it supports. Is this the driver to which you are referring?


    Actually i think I got it. I did the custom installation and only checked the graphics driver, physX driver and clean install. However I received 2 of these messages "there was a problem starting C:\Windows\system32\nvspcap64.dll, the specified module could not be found"
    Last edited by logicalthought; 25 Dec 2015 at 02:35.
      My System SpecsSystem Spec

  7. #7


    Posts : 52
    Microsoft Windows 8.1 Pro 64-bit 9600 Multiprocessor Free


    I have recieved a new BSOD: CLOCK_WATCHDOG_TIMEOUT, but this is the only BSOD I've recieved since posting. However, the game itself has been closing on me without warning (this is before I tried any suggestions). I'm am in the process of trying your suggestions.

    Thank you again for all your help thus far.
      My System SpecsSystem Spec

  8. #8


    australia
    Posts : 4
    windows 8.1


    Hi mate,

    after going through nearly 2 months of multiple BSOD's (only while gaming) and pulling out much hair, hunting for conflicts and driver problems and possible memory issues, it ended up being a bios problem, thanks to this site,,, don't know if you have but flash to the latest bios to at least eliminate it.

    yours pipco
      My System SpecsSystem Spec

  9. #9


    Posts : 660
    windows 8.1


    Do not know if you already updated your networkadapter but i found a windows 8 driver for it. https://downloadcenter.intel.com/pro...t-Ethernet-PHY
    If you also play online this is very important.

    As @axO asked update your Creative drivers they are from 2010 and outdated .

    However, the game itself has been closing on me without warning (this is before I tried any suggestions).
    Black Ops 3 was a game with many bugs/problems, (play it myself). There was also a I5 processor bug/problem, this was later solved with a patch/update.
    Did you install all the updates./patches.
    What are your settings, seeing that you don't have a highend kaart, set them not to high. Search for the good settings for your card/model (google).

    If you keep BSOD please upload a new SF.zip.
      My System SpecsSystem Spec

  10. #10


    Posts : 660
    windows 8.1


    Quote Originally Posted by pipco View Post
    Hi mate,

    after going through nearly 2 months of multiple BSOD's (only while gaming) and pulling out much hair, hunting for conflicts and driver problems and possible memory issues, it ended up being a bios problem, thanks to this site,,, don't know if you have but flash to the latest bios to at least eliminate it.

    yours pipco
    I already look at that, but unfortunately the TS has already the latest biosversion
    Intel Corp.
    BIOS Version KGIBX10J.86A.5936.2011.0630.2250
    BIOS Starting Address Segment f000
    BIOS Release Date 06/30/2011
    from intel website
    BIOS Update [KGIBX10J.86A]

    Version: 5936 (Latest) Date: 7/1/2011
      My System SpecsSystem Spec

Page 1 of 11 123 ... LastLast
Multiple BSOD playing Call of Duty: BO3
Related Threads
Hey guys, i got a fast simple question. So when i play with a friend Call of Duty Advanced Warfare over Skype, and he starts his game, the boosting lvl goes from 30dB+ to 60dB+ wich blows my ears almost each time. We did tick off the "Allow Full Control" option in the Mic settings menu, but YET it...
Ive recently got a new router from my ISP. Ever since that Every so often i disconnect from only Call of Duty. I never disconenct when im on the dashboard or Minecraft. I think it has something to do with PTP or something. Ive disconnected 3 times when i got on mw2. Ive Port Forwarded, Turned...
Hey guys, So I've been thinking of buying Call of Duty: Advanced Warfare on Steam. It looks really awesome, but what's been holding me back is the thought of buying the game and then only getting ~2fps on the thing. I was taking a look at my GPU on NotebookCheck, and when I scrolled down I...
i was using can you run it site to test if i can run the game but it failed because of the cpu 35710 and i know my cpu can boost up to 3.00ghz so is this mean i can or can't run the game
11.04.2014 42683 Call of Duty: Advanced Warfare Reveal Trailer - IGN Video
Compatibility with Call of Duty 2 in Software and Apps
:mad: I have CoD2 which is a fairly old game but still one of the most used games for online. problem is it doesn't play well with Win8, when game launches its stuck with the windows cursor not the game's , thats until i go to start menu and go back in the game again, and sometimes it doesn't...
Good evening, I was wondering if anyone else has problems playing Call of Duty 2 under Windows 8? In Windows 7 I had no problems, running perfectly. Now, when I join a public server, I'm being kicked with the message: Unkown Windows API function Any solutions? I know it's an old game...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook