Results 1 to 8 of 8
  1. #1
    New Lounger
    Join Date
    Oct 2013
    Posts
    3
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Issues with BSOD - :(

    New machine I built, was wondering if anyone could help me by reading this DUMP file for me and looking for drivers that I may need to update? I tried installing the debug tool used to do so by downloading it from Microsoft's site, but it won't install.

    I thank anyone that bothers to help me in advance, I really appreciate it.

    -----
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: d1
    BCP1: FFFFF880099F0000
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF880043D0FA0
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\102713-6708-01.dmp
    C:\Users\********\AppData\Local\Temp\WER-12152-0.sysdata.xml

    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
    Attached Files Attached Files

  2. #2
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,485
    Thanks
    283
    Thanked 573 Times in 477 Posts
    Welcome to the Lounge!

    It looks like the crash was triggered by the KillerNetworks Gigabit Ethernet Controller driver, e22w7x64.sys. Download and reinstall the latest driver for the KillerNic, if that doesn't fix it (I don't think there's a newer version), there are many very similar problems/potential fixes outlined if you follow this search: https://duckduckgo.com/?q=%22X64_0xD1_e22w7x64%22 (and the Google/Bing links at the bottom).
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff880099f0000, 2, 0, fffff880043d0fa0}
    
    *** WARNING: Unable to verify timestamp for e22w7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
    Probably caused by : e22w7x64.sys ( e22w7x64+19fa0 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff880099f0000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880043d0fa0, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b4100
    GetUlongFromAddress: unable to read from fffff800030b41c0
     fffff880099f0000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    e22w7x64+19fa0
    fffff880`043d0fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  SC2.exe
    
    ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre
    
    TRAP_FRAME:  fffff88008898670 -- (.trap 0xfffff88008898670)
    .trap 0xfffff88008898670
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000360 rbx=0000000000000000 rcx=fffffa8011e6baa8
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880043d0fa0 rsp=fffff88008898800 rbp=fffffa8011e6b9f0
     r8=0000000000000300  r9=0000000000000000 r10=fffff8000300c588
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    e22w7x64+0x19fa0:
    fffff880`043d0fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14 ds:00000000`00000248=????????????????
    .trap
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e7c169 to fffff80002e7cbc0
    
    STACK_TEXT:  
    fffff880`08898528 fffff800`02e7c169 : 00000000`0000000a fffff880`099f0000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`08898530 fffff800`02e7ade0 : fffff8a0`00fb2124 fffff8a0`00022290 fffff880`08898810 fffffa80`0d84bb40 : nt!KiBugCheckDispatch+0x69
    fffff880`08898670 fffff880`043d0fa0 : fffffa80`0d84bb40 00000000`00002384 fffffa80`0d84bb58 fffffa80`0d84bb40 : nt!KiPageFault+0x260
    fffff880`08898800 fffffa80`0d84bb40 : 00000000`00002384 fffffa80`0d84bb58 fffffa80`0d84bb40 fffffa80`0d849a38 : e22w7x64+0x19fa0
    fffff880`08898808 00000000`00002384 : fffffa80`0d84bb58 fffffa80`0d84bb40 fffffa80`0d849a38 fffff880`043cfeb2 : 0xfffffa80`0d84bb40
    fffff880`08898810 fffffa80`0d84bb58 : fffffa80`0d84bb40 fffffa80`0d849a38 fffff880`043cfeb2 00000000`00000002 : 0x2384
    fffff880`08898818 fffffa80`0d84bb40 : fffffa80`0d849a38 fffff880`043cfeb2 00000000`00000002 00000000`00000000 : 0xfffffa80`0d84bb58
    fffff880`08898820 fffffa80`0d849a38 : fffff880`043cfeb2 00000000`00000002 00000000`00000000 fffffa80`1237e450 : 0xfffffa80`0d84bb40
    fffff880`08898828 fffff880`043cfeb2 : 00000000`00000002 00000000`00000000 fffffa80`1237e450 00000000`0000024c : 0xfffffa80`0d849a38
    fffff880`08898830 00000000`00000002 : 00000000`00000000 fffffa80`1237e450 00000000`0000024c fffffa80`0da8cc10 : e22w7x64+0x18eb2
    fffff880`08898838 00000000`00000000 : fffffa80`1237e450 00000000`0000024c fffffa80`0da8cc10 fffff880`043da432 : 0x2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    e22w7x64+19fa0
    fffff880`043d0fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  e22w7x64+19fa0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: e22w7x64
    
    IMAGE_NAME:  e22w7x64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50bf79c4
    
    FAILURE_BUCKET_ID:  X64_0xD1_e22w7x64+19fa0
    
    BUCKET_ID:  X64_0xD1_e22w7x64+19fa0
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xd1_e22w7x64+19fa0
    
    FAILURE_ID_HASH:  {13809988-6ac7-9638-6d45-c609868649bd}
    
    Followup: MachineOwner
    Older drivers listed:
    http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
    http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
    http://www.carrona.org/drivers/driver.php?id=ALSysIO64.sys
    http://www.carrona.org/drivers/driver.php?id=WPRO_41_2001.sys
    http://www.carrona.org/drivers/driver.php?id=bflwfx64.sys
    http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys
    e22w7x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. <- KillerNic driver = trigger.
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=imsevent.sys
    http://www.carrona.org/drivers/driver.php?id=ikbevent.sys
    http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys
    http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys
    http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
    LGSUsbFilt.Sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. <- Logitech USB filter for HID (mouse/keyboard?)
    http://www.carrona.org/drivers/driver.php?id=LGSHidFilt.Sys
    Last edited by satrow; 2013-10-28 at 06:58.

  3. The Following 2 Users Say Thank You to satrow For This Useful Post:

    maelstromking (2013-10-28),zigzag3143 (2013-11-20)

  4. #3
    New Lounger
    Join Date
    Oct 2013
    Posts
    3
    Thanks
    1
    Thanked 0 Times in 0 Posts
    Thanks Satrow, I did some digging and I think that I have narrowed the crash down to the Killer Network Service adjusting the priority of Skype and Starcraft II and thusly causing a crash. (I have been able to reproduce the Starcraft II crash and I have since not been using Skype while playing League of Legends).

    There's a work around... the most impactful 100% guaruntee is to disable the Qualcom Atheros Killer NIC service from starting when you boot your machine, then either kill the currently running service or reboot.

    I'm going to check tonight to see if I have the most up to date drivers from Killer's site.
    I'll post back if I notice anything good or bad.
    Last edited by maelstromking; 2013-10-28 at 18:10.

  5. #4
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,485
    Thanks
    283
    Thanked 573 Times in 477 Posts
    Nice work, you have a good understanding of your PC, I'm pretty sure you're on the right track

  6. #5
    New Lounger
    Join Date
    Oct 2013
    Posts
    3
    Thanks
    1
    Thanked 0 Times in 0 Posts
    I found some updated driver's on the Killer website, not sure at this point where I got my starting drivers, either windows 7 defaults or (I think this is more likely) MSI's bundle off their site for my motherboard. So far so good... it also has better tools for monitoring how it affects TCP priority in applications (you can adjust it yourself very quickly if you don't like what it is doing). I may disable that feature altogether, but if it doesn't crash again I'll probably let it ride out like it's going now. I'll post back in a couple weeks if I don't get any more BSOD's. Thanks again for turning me onto the right driver to investigate.

  7. #6
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,485
    Thanks
    283
    Thanked 573 Times in 477 Posts
    Check in the Networking Properties for the KillerNIC that there isn't something else running interference with it; 3rd party Firewall 'helper' (if you have one installed) and TCP/IP v4 are all that's 'vital' for reaching the 'net safely, file/folder sharing and TCP/IP v6 are optional, depending on your setup and usage; anything else should be treated as suspect during troubleshooting.

  8. The Following User Says Thank You to satrow For This Useful Post:

    zigzag3143 (2013-11-20)

  9. #7
    New Lounger
    Join Date
    Nov 2013
    Posts
    11
    Thanks
    0
    Thanked 1 Time in 1 Post
    BSOD occurs due to problem pertaining with the system files, startup problems. Here are some common diagnostic:

    Repair System Files

    1. Insert Windows installation.
    2. Click Start, select Run.
    3. Type SFC /SCANNOW
    4. Click OK or press ENTER.

    Diagnose Startup Problems

    1. Click Start, select Run.
    2. Type MSCONFIG
    3. Click OK.
    4. Click the Startup tab, disable all items.
    5. Click Apply | OK.
    6. Reboot your machine.

  10. #8
    Star Lounger
    Join Date
    Dec 2009
    Location
    Finland
    Posts
    56
    Thanks
    1
    Thanked 1 Time in 1 Post
    So, you managed to sort your problem? Whether or not, for your and anyone's future reference, here's a nice tool for viewing dump files: Bluescreenview from Nirsoft.

    Although I must admit that just viewing the dump file doesn't necessarily disclose the true perpetrator. E.g. I had recently a BSOD case where the system onboard NIC _seemed_ to be the culprit, but actually it turned out to be a case of bad sound card driver installation. And even then uninstalling and reinstalling the driver via its utility program didn't solve the case. Only after also uninstalling the device from Windows Device Manager and then reinstalling it properly did the trick. Properly - meaning that the card was in place but no plugs in the back panel before rebooting. Sometimes those devices can be a bit picky --

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •