Surface Pro 3 BSOD KMODE_EXCEPTION_NOT_HANDLED mrxsmb20.sys

Hi
Have been having repeated BSOD's on my vanilla Surface Pro 3 i5 256 GB:
KMODE_EXCEPTION_NOT_HANDLED mrxsmb20.sys
They only appear to happen when I am on the docking station.
I have done a clean "Recovery" from preserving user files once, and most recently a clean recovery of the device.
Windows Updates have been installed, and the November driver pack was downloaded (today) and installed for good measure.
I am using BlueScreenView from NirSoft but I can't see any other driver that might be causing the problem.
Advice much appreciated.
Thanks
David

Hi Hunter Group ,
I wonder if there is any luck that this issue has been resolved.
According to your description, please tell us dose this issue persist after you installed all updates of November packs?
Please make sure you have installed last update of your surface firmware for good measure:
https://www.microsoft.com/en-in/download/details.aspx?id=38826
In most cases, you will experience mrxsmb20.sys blue screen errors after you’ve installed new hardware or software.
Mrxsmb20.sys blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues such like
Incorrectly configured, corrupted Windows device drivers, Virus or malware infection, hardware related to mrxsmb20.sys, Damaged or removed system files, damaged hard disk and memory (RAM) corruption.
Since this issue can be caused by installed third party software, the first thing to do is perform a clean boot see if the issue disappears.
Then You could conduct a Full Malware Scan of Your PC and run Windows System File Checker ("Dism /Online /Cleanup-Image /RestoreHealth") in Command Prompt with administrator permission. If no Virus or malware infection and the
Component Integrity is fine. Please check for Hard Drive Corruption ("chkdsk /f").
How to run “chkdsk” (Windows XP, Vista, 7, and 8):
1. Click the Start button.
2. Type "cmd" in the search box...  hit ENTER
3. A black box will open with a blinking cursor.
4. Type "chkdsk /f" and hit ENTER.
5."chkdsk" will begin scanning for hard disk corruption that could be causing mrxsmb20.sys STOP errors.
6. Follow the on-screen commands.
If the issue persists you could check or upload your DMP log to help us find corrupt or incompatible drivers or where the memory corruption happens.
About more information about “Dism /Online /Cleanup-Image /RestoreHealth”:
http://technet.microsoft.com/en-us/library/hh824869.aspx
Regards

Similar Messages

  • Surface Pro 3 BSOD

    We're getting frequent BSOD with---
    * Surface Pro 3
    * Windows 8.1 (updated to Win 10 to attempt to fix but no luck)
    * ZCM FTF Roll Up 1 for...

    Hello, I have some new Dell OptiPlex 9020 computers with windows 8.1 x64 pro. I installed the ZCM agent on one for imaging. It installed fine but...

  • Wifi on Surface Pro - installed with ndiswrapper but not working

    Hi there guys.
    I have installed Arch on a Surface Pro and most things work well.
    The biggest problem so far is wifi - it comes with a 88w8797 Marvell Avastar chipset. I managed to find the drivers and used ndiswrapper to install them.
    $ ndiswrapper -l
    mwlu97w8 : driver installed
    device (1286:2043) present (alternate driver: mwifiex_usb)
    The ndiswrapper help page says that one should get rid of alternate drivers before enabling ndiswrapper but I have no clue where to start - that seems to be a kernel loaded module (link) but it really doesn't do much apparently.
    I did 'modprobe ndiswrapper' but as you can see below, nothing seems to be really happening
    # iwconfig
    enp0s20u2u3 no wireless extensions.
    lo no wireless extensions.
    dmesg returns this on ndiswrapper
    $ dmesg | grep ndiswrapper
    [ 2.996565] ndiswrapper version 1.58 loaded (smp=yes, preempt=yes)
    [ 4.230024] usbcore: registered new interface driver ndiswrapper
    The gnome network manager, just like iwconfig, shows no able wireless.
    I'm at a loss on what to do, any help is greatly appreciatted
    Last edited by OttoRobba (2013-02-21 10:26:50)

    The blacklisting was a good call as I had completely forgot to do so. Made a /etc/modprobe.d/blacklist.conf  with 'install mwifiex_usb /bin/false' -  nothing changed though, the wireless network still won't show.
    # lsusb
    Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
    Bus 003 Device 003: ID 058f:6254 Alcor Micro Corp. USB Hub
    Bus 003 Device 002: ID 1286:2043 Marvell Semiconductor, Inc.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 045e:0795 Microsoft Corp.
    Bus 002 Device 003: ID 045e:079c Microsoft Corp.
    Bus 002 Device 004: ID 03eb:8209 Atmel Corp.
    Bus 002 Device 005: ID 045e:0794 Microsoft Corp.
    Bus 003 Device 006: ID 04e8:6863 Samsung Electronics Co., Ltd
    # lspci
    00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
    00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
    00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
    00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
    00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
    00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller (rev 04)
    00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
    00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
    It seems ndiswrapper is failing to load - I wonder if there is another module claiming the device?
    #dmesg
    [ 4.191249] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'__chkstk'
    [ 4.191274] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'MmGetSystemRoutineAddress'
    [ 4.191295] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeIoWorkItem'
    [ 4.191305] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisQueueIoWorkItem'
    [ 4.191326] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeMdl'
    [ 4.191336] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateMdl'
    [ 4.191346] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferAndNetBufferList'
    [ 4.191356] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeNetBufferList'
    [ 4.191366] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeNetBufferListPool'
    [ 4.191376] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferListPool'
    [ 4.191386] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMAllocatePort'
    [ 4.191403] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIdleNotificationComplete'
    [ 4.191413] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIdleNotificationConfirm'
    [ 4.191423] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMFreePort'
    [ 4.191432] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMNetPnPEvent'
    [ 4.191443] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIndicateReceiveNetBufferLists'
    [ 4.191453] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSendNetBufferListsComplete'
    [ 4.191463] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMOidRequestComplete'
    [ 4.191473] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMIndicateStatusEx'
    [ 4.191483] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMSetMiniportAttributes'
    [ 4.191493] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisSetOptionalHandlers'
    [ 4.191504] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateMemoryWithTagPriority'
    [ 4.191514] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisOpenConfigurationEx'
    [ 4.191523] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisFreeTimerObject'
    [ 4.191533] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisCancelTimerObject'
    [ 4.191543] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisSetTimerObject'
    [ 4.191599] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateIoWorkItem'
    [ 4.191613] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMRegisterMiniportDriver'
    [ 4.191623] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisMDeregisterMiniportDriver'
    [ 4.191648] ndiswrapper (import:232): unknown symbol: NDIS.SYS:'NdisAllocateTimerObject'
    [ 4.191663] ndiswrapper (load_sys_files:199): couldn't prepare driver 'mwlu97w8'
    [ 4.191827] ndiswrapper (load_wrap_driver:121): couldn't load driver 'mwlu97w8'
    [ 4.191926] usbcore: registered new interface driver ndiswrapper

  • Restarts and Hangs on Surface Pro 3

    Has anyone been experiencing a high number of restarts and hangs on the Surface Pro 3? Over the course of three days I have had 11 BSODs. I scanned the minidmp and it points to ntosknrl.exe. And the event log has the usual unhelpful 
    "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
    I am reading a lot about the wireless card issues on the SP3, wondering if maybe it is caused by this and an update might do the trick in the upcoming weeks. The restarts happen around the same time when the device wakes, and is not online.. 
    Anyone else experiencing this?
    Thank you

    I guess I can see the logic behind that. I'm not sure exactly how Connected Standby would work when you are using a hypervisor. The one thing that is annoying is that the Surface Pro 3 (or maybe it's just a Windows 8.1 thing in general?) has a nasty bug
    between hibernation and Wi-Fi. If you were connected to a wireless network and then go into hibernation, when you come out of it, it looks like it's still connected to the wireless network but you get no connectivity. I was able to work around this by creating
    a scheduled task based on the alert that's generated from exiting hibernation (event that says exiting low powered state or something like that) that kicks off a Powershell script that uses netsh to find the connected network, disconnect from it and then reconnect
    to it. It works pretty well but what a workaround to have to do just to conveniently exit hibernation and then automatically regain wireless connectivity!

  • Surface Pro 3 Windows 8.1 Pro N HID Sensor Collection

    I've been tasked with creating an enterprise image on the surface pro 3. I'm using MDT 2013. I've added the driver pack to MDT for the surface pro 3.
    All drivers install except for HID Sensor collection device and the simple device orientation sensor.
    However, if I deploy my personal windows 8.1 pro image to the computer, it works fine.   Just not with 8.1 Pro N.
    In device manager it says error 10, cannot start device for the collection device.  The orientation sensor is not even listed.
    Any help would be appreciated.  All windows updates have been applied.

    The two files in use by "Simple Device Orientation Sensor" in Device Manager are: c:\windows\system32\drivers\umdf\sensorservicedriver.dll
    **I do not have this driver
    c:\windows\system32\drivers\wudfrd.sys
    **This driver is present
    There is also a "sensor monitoring service" service running. When disabled it breaks the ambient light and rotation sensor (probably other items too). At least that is a place to start. I can try and zip these to an email account if you like to
    see if it helps at all.
    **THIS WAS THE KEY** I found this in Services, and it was actually running, set to 'Manual.' I stopped the service and saw my screen brightness (assuming because it disabled the ambient light sensor) come on to full. I then changed it to Automatic, and restarted
    the service. After this I wishfully rotated my Y3P 90 degrees clockwise and the auto rotate did its job! I completely shut down the Y3P and booted up again... still working!
    I'm curious as to why it wasn't working even when the service was running, but not going to dwell on it now that everything is peachy.
    I really appreciate your time and help on an issue that diverged from the OP. I know this may break forum etiquette a bit but I was on a wild goose chase trying to find the solution. KUDOS! KUDOS FOR THIS MAN!!!

  • Help install net framework 3.5 on surface pro

    Hi everybody , my name is Bruno and im from Mexico . I have some problems with my surface pro installing net 3.5 . ive never used a Windows pc before so .... ive tried to install the 3.5 and 2.0 package and didnt work , ive tried  lots of method and
    didnt work neither . ive downloaded the iso Windows 8.1 Enterprise x86 and tried the dism method but it allways drop an error message when i put dism /online /enable-feature /featurename:NetFx3 /all /source:x:\sources\sxs /limitaccess +
    ive tried runing the iso as a DVD and puting the source as it appears E or D and ive tried to copy the sys folder to C and puting source:c:\sxs with the same thing
    i got allways  stocked at 66.6% whit an error message 0x800f081f and saying that it cant find the source files ..
    I hope anybody can help me because i cant execute some files that i need to ....
    Thanks and Greetings from mexico

    Thanks a lot forhelping me , at the end i did some actualizations and after that did the turn windows method again , the first time didnt work but the second time did .... finally :D haha kinnda feel happy now :3 thanks again for the help :) greeting from
    mexico have a good day

  • Is there a work-around to enable Digital Photo Pro on the Microsoft Surface Pro ????

    Is there a way to use Digital Photo Pro on the Microsoft Surface Pro?
    As I understand the problem  DPP is unable detect the screen resolution of the tablet ( the defauilt res of the tablet
    is 1920 x1080) with a minimum of 1024 x768.
    It would be usful if one could type in your working screen res into at startup if that's the only problem
    ___I've looked at other screen drivers from Intell but I realize if I could install thrm I'de lose the touch functionallity
    Are there any other ideas out there???
    Thanks  artB

    Canon DPP is Canon provided application for desktop/laptop computers and they don't have a version for any tablets as far as I'm aware (not even iOS or Android versions).
    But there are other photo editing programs that would work.  I have an iPad.  While Apple has their own photo software (which isn't going to work on a Windows tablet) Adobe has an app called PS Touch.  
    PS Touch isn't nearly as full featured as Photoshop.  It limits the image resolution (it resizes any images that you import to it so they don't exceed the max resolution) but it does have most of the commonly used adjustments.  So if a person were just trying to get something out, it works in a pinch.
    One other catch is that PS Touch can't deal with RAW images... so it's JPEG only.  But I can import JPEGs off the card into the iPad and then edit them -- not as well as I can if they're on a regular computer, but this is what I'ved when I'm away for a weekend with my camera.
    Tim Campbell
    5D II, 5D III, 60Da

  • Polygonal lasso tool not working with stylus on Surface Pro 2

    Hi guys,
    I'm new here so please bare with me if I'm posting in the wrong place or don't make immediate sense.
    Hardeware / software used: surface pro 2 and I'm running photoshop CS5.
    Problem is a fairly basic one: I am trying to make basic selections using the polygonal lasso tool (using the stylus that comes with the tablet) but it simply will not work. All I get when I touch the stylus to the screen is the circle that appears then fades. If I attach the keypad and try using that then it works no problem at all.
    Does anyone have any ideas as to whether there is a particular setting that I need to switch on or off e.g. something relating to pressure sensitivity (although not sure why this would affect this particular selection tool)?
    I've searched the web and come up with nothing so far so any help is greatly appreciated!
    Thanks for your time
    Scott

    same problem on surface pro 3 !!!!
    and i think quite significant, for lot of artists using polygonal lasso a lot (including me). How come that the stupid surface cannot work properly

  • How do I install itunes on a surface pro 2 tablet?

    My ipad won't update through the ipad so I need to do it through my computer but all I have is a surface pro 2 windows tablet and I cant install iTunes on it. Is there anyway to download it for my computer or other ways of updating ipads if it wont work on the ipad??

    iTunes should install on a Surface Pro 2 just like any other PC running Windows 8.1.  If you go to http://www.apple.com/itunes/ and click the Download iTunes button the next page should give you access to the appropriate installer.  Note, though, that the relatively limited storage, especially on the lower spec models, may limit the size of library you can have without using external storage.  iTunes itself requires 400Mb of free disc space to be installed.
    iTunes does not run on the original Surface and the Surface 2 that run Windows RT.  The new Surface 3 runs full Windows 8.1 and should support iTunes just like the Pro 2 and Pro 3.

  • Problem push and hold on a Surface Pro tablet's touch screen

    Hi,
    I tried posting this before, but I can't find my origional post so I hope I'm not spamming accidentally.
    I have a problem with my program on a Windows 8.1 Surface Pro tablet. I programmed a button to be 'push-and-hold', but when I touch the tablet nothing happens until I release my finger. This briefly controls the button. When I connect a USB mouse to the tablet, it responds normally; when I press the left mouse button: the button in my program goes down until I release the mouse button. I tried about every setting in the Touch section of the Windows control panel without any succes.
    Does anyone have a suggestion?
    Any help would be greatly appreciated.
    Chris  

    Previous Post.
    http://forums.ni.com/t5/LabVIEW/Press-and-hold-on-a-Surface-pro-touch-screen/m-p/2816346
    If you clicked on your username and looked at your profile, you can see the messages you've created or replied to in the past.

  • Using Bitlocker Data Recovery Agent (DRA) on Surface Pro 3

    We currently have the Data Recovery Agent (DRA) configured in our Bitlocker Policy for our Windows 7 Systems, and it works fine. In situations where the Recovery Key for the computer object was not backed up to AD correctly for whatever reason or the computer
    object was deleted, our HelpDesk can connect the encrypted drive to another system, and then use the certificate for the DRA to unlock the drive.
    I'm wondering if the BitLocker DRA Certificate unlock method will work for Surface Pro 3 devices, in the case that that their computer object and normal BitLocker recovery key is deleted or missing in AD for whatever reason. Seeing as how our helpdesk can't
    easily remove the internal HD from a Surface Pro 3 (I think only MS can do this?), I'm wondering if this BitLocker recovery option is still an option for Surface Pro 3's and if it is not then if there is another recommended option for Surface Pro 3's and/or
    other Windows 8.1 Tablets used in an enterprise environment.

    noctlos wrote:
    Using linux-3.18 and -3.19 kernels, with wayland/weston v. 1.7. In its own tty, i try to run weston, and I get the following stderr:
    Could anyone help me to figure this out? Thanks.
    Seems that the problem lies in libinput. Maybe you can report that upstream. I suggest you recompile libinput with debug info and do not strip the binaries to obtain better backtraces.
    Edit:
    I have also tried running `swc-launch -- velox`, and get the following error:
    Running on /dev/tty2
    velox: error while loading shared libraries: libinput.so.5: cannot open shared object file: No such file or directory
    Server exited with status 127
    Restoring VT to original state
    So, perhaps I am having some libinput trouble. Does this seem correct?
    Well, that's a different problem. libinput has several soname bumps because of API and ABI incompatibility. You have to rebuild swc against the newest libinput. (Although I'm not sure if swc developer updated the code to new API)
    Edit 2:
    Just to tack this on here for `gnome-session --session=gnome-wayland --debug`
    I'm not expert on this, it may be related to libinput problem. If you don't include GDK_BACKEND=wayland environment variable when launching gnome-wayland.
    Last edited by jdbrown (2015-03-01 08:04:39)

  • Bit Locker on surface pro 3 ssd card

    I had a surface pro 3 which I managed to damage. There was data on the ssd that I needed so I have got it out and connected it to my laptop by usb. When I try and use open it, it comes up with bit locker drive encryption so I need a bitlocker recovery
    key. help anyone?

    Do you have the recovery key ? If you don't have it, I'm sorry to say but you'll loose all the data. 
    Arnav Sharma | http://arnavsharma.net/ 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.

  • Type UI in CS6 in Surface Pro 3 is too small.  Adobe needs to isuue a fix for CS6.

    I don't need to upgrade CS6 for any photography reason.  Adobe should make CS6 UI readable fro surface pro 3 users.  They have a fix for later versions.  Why not make it available in other earlier versions of photoshop.  This is not a question of adding new features, it is a question of making the UI readable.

    Mylenium wrote:
    Nobody goes back to fix up a 5 year old software that was never meant to be run on computers that didn't exist back then.
    However good software companies like Microsoft fixes bugs user report on their Current  Software.  Adobe should fix bugs on current marketed software  like CS6 Adobe chooses not to. Microsoft fixed XP till the middle of 2014 years after windows 7 and win 8 were current.   Bugs go unfixed in Photoshop release after release. Adobe Program support continues to be sub par year after year.
    Currently there are three CS6
    perpetual Mac version 13.0.6
    perpetual PC version 13.0.1.3
    subscription version 13.1.2 PC and Mac

  • Speed grade does not work on my surface pro 3

    Two questions:
    Speed grade does not work on my surface pro 3. It open normaly but when I import a video I ear only the sound the image is black.Why?
    So I try to install it on a over computer but in the creativ cloud software I didn't it. Why ?

    I would suggest you are wasting your time trying to use SG on a Surface Pro 3. SG minimum hardware specifications ask for a discrete GPU that supports a GPGPU language like CUDA http://helpx.adobe.com/x-productkb/policy-pricing/system-requirements-speedgrade.html
    If you want to do colour correction then try using Adobe Premier effects such as the Fast Color Corrector or Curves.

  • Press and hold on a Surface pro touch screen

    Hi,
    I am having some problems with my Surface Pro, trying to control a relay 'press-and-hold'. When I connect a mouse to the Tablet, Windows registers the left mouse up and down events perfectly, allowing the user to control the relay exactly the way I intended, but when I use the touch screen with either the stylus pen or my finger it only seems to press the LabVIEW on release.
    Does anyone have a solution for this problem?
    Chris

    Jeff-P wrote:
    I just tested this on my touchscreen laptop and got a similar behavior. Windows doesn't seem to be registering the left click when you touch the screen until you release. My guess is that this is related to the press+hold for right click functionality on Windows. When I touch and hold for over a second, I get a right click, but when I touch and hold for a shorter time, I get a left click that only registers when I take my finger off. This is consistent with the way that the Windows UI handles touch as well (test the start button for an example).
    Interestingly, if I change the mechanical action of the LabVIEW boolean to 'Switch Unit Released' I can't actually toggle the button ever because the press and hold does not register as a left click, and eventually registers as a right click.
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect 
    Actually, this is expected behavior.  Try clicking a button on any Windows app, then, while holding down the button, move off of it.  The button does not register as pressed.  This feature has saved me any number of times. 
    edit:
    Or do you mean it doesn't even depress the button?
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Maybe you are looking for