BSOD on Win7 Pro 64bit RRS feed

  • Question

  • Hi,  I keep getting random BSOD's from a bug check and I get this from the Memory.dmp 

    PROCESS_NAME:  explorer.exe
    00000000`775a17ba ??              ???
    LAST_CONTROL_TRANSFER:  from fffff80003088569 to fffff80003088fc0

    Here is the SkyDrive link to the Memory.dmp and the last minidump: https://skydrive.live.com/redir?resid=A78A98D6AB7A314!170&authkey=!AJLItK0V57zdifs

    Wednesday, January 30, 2013 2:13 AM

All replies

  • Hi.

    Just trying to get more info on the situation.

    Do you get these BSOD's just when the machine is idle, or when your busy with your average things? (email/browsing/etc.)

    Thx for the dump FILES BTW!

    Wednesday, January 30, 2013 9:09 AM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arg1: 0000000000000081, MmMapLockedPages called without MDL_MAPPING_CAN_FAIL
    Arg2: fffff9806434efc0, MDL address.
    Arg3: 0000000000000082, MDL flags.
    Arg4: 0000000000000000, 0.
    Debugging Details:
    BUGCHECK_STR:  0xc4_81
    PROCESS_NAME:  System
    LAST_CONTROL_TRANSFER:  from fffff800035243dc to fffff8000309dfc0
    fffff880`0399a378 fffff800`035243dc : 00000000`000000c4 00000000`00000081 fffff980`6434efc0 00000000`00000082 : nt!KeBugCheckEx
    fffff880`0399a380 fffff800`035377ea : fffff980`6434efc0 00000000`00000002 fffffa80`18b39c30 fffff880`0399b000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0399a3c0 fffff880`06f98823 : fffff980`82e72ea0 fffff980`86c26fc0 fffffa80`193a7140 fffffa80`000007ad : nt!VerifierMmMapLockedPages+0x4a
    fffff880`0399a400 fffff980`82e72ea0 : fffff980`86c26fc0 fffffa80`193a7140 fffffa80`000007ad fffff980`82e72ea0 : mcdbus+0x36823
    fffff880`0399a408 fffff980`86c26fc0 : fffffa80`193a7140 fffffa80`000007ad fffff980`82e72ea0 fffff980`82e72f70 : 0xfffff980`82e72ea0
    fffff880`0399a410 fffffa80`193a7140 : fffffa80`000007ad fffff980`82e72ea0 fffff980`82e72f70 fffff880`0399a960 : 0xfffff980`86c26fc0
    fffff880`0399a418 fffffa80`000007ad : fffff980`82e72ea0 fffff980`82e72f70 fffff880`0399a960 fffff980`86c26fc0 : 0xfffffa80`193a7140
    fffff880`0399a420 fffff980`82e72ea0 : fffff980`82e72f70 fffff880`0399a960 fffff980`86c26fc0 fffffa80`18b39d80 : 0xfffffa80`000007ad
    fffff880`0399a428 fffff980`82e72f70 : fffff880`0399a960 fffff980`86c26fc0 fffffa80`18b39d80 fffff880`0399a970 : 0xfffff980`82e72ea0
    fffff880`0399a430 fffff880`0399a960 : fffff980`86c26fc0 fffffa80`18b39d80 fffff880`0399a970 00000000`00000000 : 0xfffff980`82e72f70
    fffff880`0399a438 fffff980`86c26fc0 : fffffa80`18b39d80 fffff880`0399a970 00000000`00000000 fffff980`86c26fe8 : 0xfffff880`0399a960
    fffff880`0399a440 fffffa80`18b39d80 : fffff880`0399a970 00000000`00000000 fffff980`86c26fe8 fffffa80`0ea0de00 : 0xfffff980`86c26fc0
    fffff880`0399a448 fffff880`0399a970 : 00000000`00000000 fffff980`86c26fe8 fffffa80`0ea0de00 fffff800`03535f0d : 0xfffffa80`18b39d80
    fffff880`0399a450 00000000`00000000 : fffff980`86c26fe8 fffffa80`0ea0de00 fffff800`03535f0d fffff980`82e72ea0 : 0xfffff880`0399a970
    fffff880`06f98823 ??              ???
    SYMBOL_NAME:  mcdbus+36823
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: mcdbus
    IMAGE_NAME:  mcdbus.sys
    FAILURE_BUCKET_ID:  X64_0xc4_81_mcdbus+36823
    BUCKET_ID:  X64_0xc4_81_mcdbus+36823
    Followup: MachineOwner

    Bug Check 0xC4http://msdn.microsoft.com/en-us/library/windows/hardware/ff560187(v=vs.85).aspx

    The Blue Screen caused by ( mcdbus.sys ) , Mcdbus.sys with description MagicISO SCSI Host Controller is a driver file from company MagicISO, Inc. belonging to product MagicISO SCSI Host Controller.

    ** Resolution : Uninstall the MagicISO software it solve your Bluescreen.



    Wednesday, January 30, 2013 12:03 PM
  • Hi.

    Try using "Ultra ISO" or even "Virtual CD" they have the least problems with windows.

    Magic ISO/Daemon Tools/Power ISO/ISO Buster/Alcohol Soft/etc. They all have their little bugs and a lot of conflicts with other programs, I recommend you try an updated version of the program or switching to another similar vender.

    Wednesday, January 30, 2013 1:28 PM
  • Hi Albert!  I get the BSOD's when the machine is idle.  It has never happened when I was busy doing anything.  And, the machine has become noticeably slower... and its brand new with minimal apps and documents... like  my whole C:\ drive is only using 122GB out of 684.
    Wednesday, January 30, 2013 9:50 PM
  • Please upload and share copies of your System and Application logs from your Event Viewer to your Sky Drive and post a link here.

    To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window select Windows Logs and System. Place the cursor on System, select Action from the Menu and Save All Events as and give the file a name. Do the same for the Applications log.


    Hope this helps, Gerry

    Wednesday, January 30, 2013 9:56 PM
  • Hi Las!

    I did as you instructed and uninstalled the MagicISO MagicDisc.  It was NOT easy uninstalling that stupid thing, but I finally got it off my computer. I'll see how that goes!

    Wednesday, January 30, 2013 10:37 PM
  • Hi Gerry,

    I have uploaded the event logs you asked for.  I have saved both the Application and System event logs in 2 different formats just in case. One is a .csv and the other is the .evtx.  Thank you for your help on this as well!

    • Edited by Cmbingham Wednesday, January 30, 2013 10:48 PM added link
    Wednesday, January 30, 2013 10:48 PM
  • Hi,

    Please check whether this issue will occur again after uninstalling the MagicISO. If the issue persists, please upload the latest dump file for us to check the issue.


    Vincent Wang
    TechNet Community Support

    Thursday, January 31, 2013 5:44 AM
  • The last three BSOD errors are generated by Driver Verifier resulting in Bug Check Code 0xC4 with parameter 1 as 0x81
    The driver called MmMapLockedPages.
    (You should use MmMapLockedPagesSpecifyCache instead, with the BugCheckOnFailure parameter set to FALSE.)

    In the Article are links in the original of the Notes about the meaning of parameter 1 0x81.

    You should not leave Driver Verifier forever running. Stop it after use.

    Hope this helps, Gerry

    Thursday, January 31, 2013 11:02 AM
  • Hi Gerry!

    Thanks for the info! Where do I change the MmMapLockedPages parameter?  Also, how do I stop the driver verifier?

    Friday, February 1, 2013 10:17 PM
  • Where do I change the MmMapLockedPages parameter?

    Sorry  this is going beyond my level of expertise.

    Stop Driver Verifier:


    Hope this helps, Gerry

    Friday, February 1, 2013 11:31 PM