1. #1

    bsod windows 8.1

    Hello there!

    Here( Bsod windows 8.1 )is a link where I asked my question, but no one there can help me.
    So a member told me to try here.



    (PS: i'm figuring out how to upload my memory.dmp file, because it takes so long here.)
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    TomasD's Avatar
    Join Date
    May 2013
    Location
    Kaunas, Lithuania
    Posts
    461
    • specs System Specs
      • Manufacturer:
        Lenovo
      • Model Number:
        X230T
      • Motherboard:
        Lenovo ThinkPad X230 Tablet
      • CPU:
        Intel Core i5-3320M
      • Memory:
        Corsair Vengeance 2x8GB DDR3-1600 (800 MHz)
      • Graphics:
        Intel HD Graphics 4000
      • Sound Card:
        Realtek ALC269
      • Disk Drives:
        SAMSUNG SSD 830 Series (238 GB)
      • Display:
        BenQ BL2400
      • Operating System:
        Microsoft Windows 8.1

    Re: bsod windows 8.1

    Hi,

    The BSOD seems to be caused by CORM40.sys driver, used by your Corsair M40 Gaming Mouse. Please download and install the latest driver and firmware for this mouse.
    http://www.dabasinskas.net (MCP | MCTS | MCITP | MCSA | MCSE | MVP | MS | ITV3F | ZCE | VCA)


  3. #3

    Re: bsod windows 8.1

    Hi,

    I noticed you also posted your thread on MS Answers, to which I replied (here)

    Let's keep all assistance here and refrain from cross-posting so we don't have confusion. Be sure to follow Tomas' instructions and let us know how it goes.

    Regards,

    Patrick

  4. #4

    Re: bsod windows 8.1

    https://www.dropbox.com/s/a3azpwirl1gtbf5/MEMORY.DMP - this the link to my memory.dmp

    I already done that by the way Tomas.

  5. #5

    Re: bsod windows 8.1

    The attached DMP file is of the KMODE_EXCEPTION_NOT_HANDLED (1e) bug check.

    This indicates that a kernel-mode program generated an exception which the error handler did not catch.

    BugCheck 1E, {ffffffffc0000047, fffff803058dbbf4, 1a, ffffe00000fca000}


    Code:
    0: kd> kv
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff803`071de6e8 fffff803`059d3e9e : 00000000`0000001e ffffffff`c0000047 fffff803`058dbbf4 00000000`0000001a : nt!KeBugCheckEx
    fffff803`071de6f0 fffff803`059551ed : fffff803`05b03000 fffff803`05800000 0003ece8`00781000 00000000`00000286 : nt!KiFatalExceptionHandler+0x22
    fffff803`071de730 fffff803`058db595 : 00000000`00000000 fffff803`071de860 fffff803`071dee80 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd
    fffff803`071de760 fffff803`058dbc2a : 00000000`00000000 00000000`00000000 00000000`c0000047 00000000`00000000 : nt!RtlDispatchException+0x455
    fffff803`071dee60 fffff803`0598957d : ffffe000`01dc63d0 00000000`00000000 ffffe000`03212170 fffff803`05a9156e : nt!RtlRaiseStatus+0x4e
    fffff803`071df400 fffff800`03bebabe : 00000000`00000064 ffffe000`00000001 00000000`00000000 ffffe000`034b8060 : nt! ?? ::FNODOBFM::`string'+0x2b3dd
    fffff803`071df4a0 fffff803`058a7f08 : ffffe000`0253d010 fffff803`071df5c9 ffffe000`01da9f50 ffffe000`0253d48b : CORM40+0x1abe
    fffff803`071df520 fffff800`002e18fc : 00000000`ffffffff 00000000`00000000 00000000`00000004 ffffe000`014e58f0 : nt!IopfCompleteRequest+0x438
    fffff803`071df630 fffff800`002ee364 : ffffe000`024cde00 00000000`00000000 fffff803`00000001 ffffe000`024cdc02 : Wdf01000!FxRequest::CompleteInternal+0x23c
    fffff803`071df6f0 fffff800`02b8eee2 : ffffe000`024cde00 fffff803`071d0000 ffffe000`024cdc60 ffffe000`024cdc60 : Wdf01000!imp_WdfRequestComplete+0x8c
    fffff803`071df760 fffff800`02b8fe58 : ffffe000`024cde00 00000000`00000001 ffffe000`024cde80 fffff803`071df8e0 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x15a
    fffff803`071df7c0 fffff800`02b7d02b : 00000000`00000780 ffffe000`0150bf20 00000000`00000000 fffff803`05857489 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x3a8
    fffff803`071df870 fffff800`00379c81 : 00000000`00000000 ffffffff`00000003 00001fff`feaf42c8 00000000`ffffffff : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427
    fffff803`071df970 fffff803`0585ad10 : fffff803`05af0f00 fffff803`071dfb20 ffffe000`0150bd30 ffffe000`01c3a430 : Wdf01000!FxInterrupt::DpcHandler+0xc1
    fffff803`071df9a0 fffff803`0585a9f0 : ffffe000`00000000 00001f80`00000001 00000098`33099d0b 00000000`00000002 : nt!KiExecuteAllDpcs+0x1b0
    fffff803`071dfaf0 fffff803`059517ea : fffff803`05aee180 fffff803`05aee180 00000000`001a3fe0 fffff803`05b46a80 : nt!KiRetireDpcList+0xd0
    fffff803`071dfc60 00000000`00000000 : fffff803`071e0000 fffff803`071da000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    -- FAILURE_BUCKET_ID: 0x1E_c0000047_CORM40+1abe

    ^^ Right, so CORM40.sys (Corsair mouse driver as we know) made an attempt to release a semaphore (twice possibly?) such that its maximum count would have been exceeded.

    In computer science, particularly in operating systems, a semaphore is a variable or abstract data type that is used for controlling access, by multiple processes, to a common resource in a parallel programming or a multi user environment. A useful way to think of a semaphore is as a record of how many units of a particular resource are available, coupled with operations to safely (i.e., without race conditions) adjust that record as units are required or become free, and, if necessary, wait until a unit of the resource becomes available.



    Something may be causing conflicts with your mouse driver:

    1. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it may be causing conflicts:

    avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

    Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

    2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

    3. Sapphire Trixx is VERY likely causing conflicts, so please uninstall ASAP.

    4. If after all of the above the crashes remain, uninstall any/all Corsair mouse software/drivers, shut down, remove mouse, boot up, plug it in, and allow Windows to install the generic mouse drivers and see if you still crash.

    Regards,

    Patrick

  6. #6

    Re: bsod windows 8.1

    I have done everything, we will see if it still occurs.
    Can I use Msi afterburner instead of sapphire trixx?

  7. #7

    Re: bsod windows 8.1

    Great, keep us updated.

    Can I use Msi afterburner instead of sapphire trixx?
    No, please refrain from installing any OSD/HWM GPU software for the time being.

    Regards,

    Patrick

Similar Threads

  1. BSOD while running Windows Store on Windows 8.1
    By hacker8 in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 01-15-2014, 09:33 AM
  2. Windows 7 x64 BSOD - PFN_LIST_CORRUPT BSOD
    By emreblt in forum BSOD, Crashes, Kernel Debugging
    Replies: 4
    Last Post: 03-23-2013, 03:23 AM
  3. [SOLVED] BSOD on Upgraded Windows 8 PRO from Windows 7 Home Premium
    By hbeaufelipe in forum BSOD, Crashes, Kernel Debugging
    Replies: 17
    Last Post: 03-21-2013, 01:18 PM
  4. BSoD on Windows Defender Quick Scan in Windows 8
    By akshay2000 in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 12-24-2012, 11:39 PM
  5. Windows 7 bsod
    By Corseth in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 11-17-2012, 06:50 AM

Log in

Log in