1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

BSODs resulting from playing Eve Online

By Phanixis ยท 5 replies
Aug 15, 2011
Post New Reply
  1. So, I just got into Eve online recently. Interesting game, but its got a penchant for bringing about BSODs. I had no BSODs since I formatted my drive, until I play this. I suppose I could stop playing, but I would like to see if I can get the BSOD errors corrected.

    I had three BSODs total. After the second, I updated my video drivers, and that worked for a while. I now have another. I will append the minidump at the end of this file.

    Can anyone diagnose the minidump for me. Any help would be greatly appreciated.


    Minidump File:

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [D:\WINDOWS\Minidump\Mini081511-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*d:\windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.101019-0340
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
    Debug session time: Mon Aug 15 00:21:45.765 2011 (UTC - 4:00)
    System Uptime: 0 days 7:48:08.644
    *** WARNING: Unable to verify checksum for ntkrnlmp.exe
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 3B, {c0000005, fffff800011a9ebd, fffffadfb4b1dcb0, 0}

    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+33f )

    Followup: Pool_corruption


    0: kd> !analyze -v
    * *
    * Bugcheck Analysis *
    * *

    An exception happened while executing a system service routine.
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff800011a9ebd, Address of the instruction which caused the bugcheck
    Arg3: fffffadfb4b1dcb0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

    Debugging Details:

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    fffff800`011a9ebd 48894108 mov qword ptr [rcx+8],rax

    CONTEXT: fffffadfb4b1dcb0 -- (.cxr 0xfffffadfb4b1dcb0)
    rax=fffffadfcda6f010 rbx=0000000000000001 rcx=0010fadf03eecf00
    rdx=fffffadfce258000 rsi=0000000000000000 rdi=fffff800011ce1c0
    rip=fffff800011a9ebd rsp=fffffadfb4b1e4c0 rbp=fffff800011ce1c0
    r8=fffffadfce258880 r9=0000000000000001 r10=fffffadfccb31c10
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=000000000000000d
    iopl=0 nv up ei ng nz ac po cy
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297
    fffff800`011a9ebd 48894108 mov qword ptr [rcx+8],rax ds:002b:0010fadf`03eecf08=????????????????
    Resetting default scope




    PROCESS_NAME: ExeFile.exe


    IRP_ADDRESS: fffffadfccd344f8

    LAST_CONTROL_TRANSFER: from fffff800011aa03d to fffff800011a9ebd

    fffffadf`b4b1e4c0 fffff800`011aa03d : fffffadf`ccd2e6e0 fffffadf`cca2ac20 fffffadf`ccd2e6d0 fffff800`011ce1c0 : nt!ExDeferredFreePool+0x33f
    fffffadf`b4b1e530 fffff800`01049e5c : fffffadf`b4b1e680 fffff800`01027abd fffffadf`cba2d040 fffffadf`b4b1e730 : nt!ExFreePoolWithTag+0x759
    fffffadf`b4b1e5f0 fffff800`01027eb1 : fffffadf`ccd34570 00000000`00000000 00000000`00000000 fffffadf`cbb55ee0 : nt!IopCompleteRequest+0x121
    fffffadf`b4b1e690 fffff800`01027abd : fffffadf`00000040 00000000`00000000 00000000`00000000 fffff800`011b0180 : nt!KiDeliverApc+0x215
    fffffadf`b4b1e730 fffff800`010272ab : 00000000`ccd2e450 00000000`00000000 fffffadf`c208f7b6 fffffadf`ccd2e74c : nt!KiApcInterrupt+0xdd
    fffffadf`b4b1e8c0 fffff800`01030d45 : 00000000`00000001 00000000`00000000 00000000`00000000 fffffadf`cbb55ee0 : nt!KiExitDispatcher+0x1d3
    fffffadf`b4b1e8f0 fffff800`01025229 : fffffadf`cbb55ee0 00000000`00000000 00000000`a0000003 fffffadf`cbb55ee0 : nt!KeInsertQueueApc+0xd4
    fffffadf`b4b1e940 fffffadf`c201479c : 00000000`00000000 00000000`00000002 00000000`00000000 fffffadf`b4b1ecf0 : nt!IopfCompleteRequest+0xa26
    fffffadf`b4b1e9b0 fffffadf`c202a362 : 00000000`00000001 fffffadf`b4b1ecf0 00000000`00000000 fffffadf`cbb55ee0 : tcpip!IPDispatchDeviceControl+0x147
    fffffadf`b4b1ea20 fffff800`0127f0f1 : 00000000`00000008 fffffadf`cbb55ee0 00000000`00000001 00000000`00000000 : tcpip!TCPDispatch+0x1df
    fffffadf`b4b1ea70 fffff800`0127ebf6 : 00000000`00000000 00000000`00000afc 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0xa79
    fffffadf`b4b1eb90 fffff800`0102e33d : fffffadf`cca2ac20 fffffadf`cba2d040 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
    fffffadf`b4b1ec00 00000000`78b83e48 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
    00000000`10f3f098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b83e48

    fffff800`011a9ebd 48894108 mov qword ptr [rcx+8],rax


    SYMBOL_NAME: nt!ExDeferredFreePool+33f

    FOLLOWUP_NAME: Pool_corruption

    IMAGE_NAME: Pool_Corruption


    MODULE_NAME: Pool_Corruption

    STACK_COMMAND: .cxr 0xfffffadfb4b1dcb0 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+33f

    BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+33f

    Followup: Pool_corruption
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,979   +71

    0x3B errors are usually caused by faulty video drivers. because of your error code and your symptoms I suggest doing the following...

    1. Go to our Download section and click on Utilities and then download Driver Sweeper 3.1 to your desktop screen and install.

    2. Download the latest diver(s) for your video card but don't install them.

    3. Uninstall your video card drivers and reboot your PC into Safe Mode. Run Driver Sweeper and remove ONLY the video card drivers. I had someone use it on their chipset drivers! If it doesn't find any video card drivers that is quite okay; just leave all other drivers alone.

    4. Reboot and install new video card drivers.
  3. Phanixis

    Phanixis TS Rookie Topic Starter Posts: 53

    Ok, thanks for the advice. I will go ahead and carry out this procedure.
  4. Phanixis

    Phanixis TS Rookie Topic Starter Posts: 53

    How exactly does this program work. Are the entries that show up after I click "analyze and clean" redundant and undesired entries? I don't want to accidentally remove anything critical.

    Thanks for the help.
  5. Phanixis

    Phanixis TS Rookie Topic Starter Posts: 53

    It is done.

    I did put an extra restart in there before going into safe mode and windows was trying to automatically install the drivers after that restart, so hopefully it did not screw this process up. If I get another bluescreen I will probably end up repeating the process.

    Thanks again for the help.
  6. Route44

    Route44 TechSpot Ambassador Posts: 11,979   +71

    Yes, please keep us informed. The whole thing with Driver Sweeper is to only use it on your video card drivers and nothing else. All other drivers that show up in that list are to be left alone.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...