locked
Win7 Ultimate 64, crashing in firefox due to mrxsmb20.sys? RRS feed

  • Question

  • Hi all,

    I'm getting sporadic crashes when using Firefox (maybe 1 per day). The problem occurs, or has only occurred up until now, when i click on a new tab or to expand an existing one. That's the only time it happens.

    Had a look in bluescreenview expecting to find a flash issue or similar driver issue but instead found the below;

    From what i can tell this is a windows driver/process so i don't really know what to do as any other problems like this have usually been caused by third party software.

    If you need the minidump or any other info let me know.

    Many thanks

    Tuesday, May 7, 2013 7:19 AM

Answers

  • Hi I1ttledb,

    I agree with ZigZag3143x. Meanwhile,based on your minidump file, we could see Probably caused by : atikmpag.sys. So it may be because of ATI video card’s compatibility.

    You could try to update your video card driver applied to your computer from AMD official website:

    http://support.amd.com/us/gpudownload/Pages/index.aspx

    Best regards,

    Karen Hu

    • Marked as answer by Cloud_TS Wednesday, May 15, 2013 1:37 AM
    Wednesday, May 8, 2013 8:58 AM

  • "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".


    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

    BugCheck 116, {fffffa8005c3d4e0, fffff88004548e6c, ffffffffc0000001, 3}
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+8e6c )


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com

    • Proposed as answer by Ty Glander Thursday, May 9, 2013 9:19 PM
    • Marked as answer by Cloud_TS Wednesday, May 15, 2013 1:37 AM
    Wednesday, May 8, 2013 1:25 AM

All replies

  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  We need at least 2 DMP FILES to diagnose and confirm


    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
     *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    http://www.wikihow.com/Use-SkyDrive

    To ensure minidumps are enabled:

    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.

    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com

    Tuesday, May 7, 2013 3:50 PM
  • SMB shouldn't be involved in a video error. That being said:

    Bugcheck 0x116 is Bug Check 0x116: VIDEO_TDR_ERROR

    Without the crashdump (as per ZigZag above) it is hard to tell what is going on.

    In the interim however you can try:

    http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” How to ask a question that is fixable.


    • Edited by Ty Glander Tuesday, May 7, 2013 5:18 PM
    Tuesday, May 7, 2013 5:18 PM
  • Hi,

    Thanks for the replies guys, here's the minidump.

    Cheers


    Edit: and the system Info
    • Edited by l1ttledb Wednesday, May 8, 2013 1:02 AM
    Wednesday, May 8, 2013 12:57 AM

  • "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".


    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

    BugCheck 116, {fffffa8005c3d4e0, fffff88004548e6c, ffffffffc0000001, 3}
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+8e6c )


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com

    • Proposed as answer by Ty Glander Thursday, May 9, 2013 9:19 PM
    • Marked as answer by Cloud_TS Wednesday, May 15, 2013 1:37 AM
    Wednesday, May 8, 2013 1:25 AM
  • Hi I1ttledb,

    I agree with ZigZag3143x. Meanwhile,based on your minidump file, we could see Probably caused by : atikmpag.sys. So it may be because of ATI video card’s compatibility.

    You could try to update your video card driver applied to your computer from AMD official website:

    http://support.amd.com/us/gpudownload/Pages/index.aspx

    Best regards,

    Karen Hu

    • Marked as answer by Cloud_TS Wednesday, May 15, 2013 1:37 AM
    Wednesday, May 8, 2013 8:58 AM