BSOD when using RDP error: "KMODE_EXCEPTION_NOT_HANDLED" ntoskrnl.exe


  1. Posts : 3
    Windows 7 Enterprise 64Bit
       #1

    BSOD when using RDP error: "KMODE_EXCEPTION_NOT_HANDLED" ntoskrnl.exe


    Hi,

    My issue is to do with accessing my PC via RDP, I have a work PC which I should be able to access via RDP (mstsc) however whenever I attempt RDP access to my work PC from another, my work PC blue screens reboots, and then allows me access once rebooted. It will still grant me RDP access for a short while but coming back to it the next day it will then blue screen again. This is not only happening to me but too a couple of people within our company.

    I have tried allowing the port I use for port forwarding to access my PC through the firewall and I have tried installing all windows updates but nothing seems to have worked.

    I know that my PC is blue screening because I have attempted RDP access in the same room.

    Attached is the latest .dmp file.

    Cheers for the help. :)
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    What is uploaded here is not a .dmp as you said, it is a .txt.

    Post it following Blue Screen of Death (BSOD) Posting Instructions.
      My Computer


  3. Posts : 3
    Windows 7 Enterprise 64Bit
    Thread Starter
       #3

    Sorry about that wasn't sure if I had done that right here is the .zip file
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Well, it is Caused by Deep Freeze. Though I dont have any idea what it may be.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000046, fffff80002f05b80, 0, fffff80002ea849b}
    
    *** WARNING: Unable to verify timestamp for DeepFrz.sys
    *** ERROR: Module load completed but symbols could not be loaded for DeepFrz.sys
    Probably caused by : DeepFrz.sys ( DeepFrz+24810 )
    
    Followup: MachineOwner
    ---------
    And, it is very old, too.
    Code:
    lmvm DeepFrz
    start             end                 module name
    fffff880`0197d000 fffff880`019b2d00   DeepFrz  T (no symbols)           
        Loaded symbol image file: DeepFrz.sys
        Image path: \SystemRoot\System32\Drivers\DeepFrz.sys
        Image name: DeepFrz.sys
        Timestamp:        Tue Feb 09 00:28:31 2010 (4B705ED7)
        CheckSum:         0003D26F
        ImageSize:        00035D00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Search for updates in (probably) Download Form | Faronics.
      My Computer


  5. Posts : 3
    Windows 7 Enterprise 64Bit
    Thread Starter
       #5

    Alright then cheers.

    Deepfreeze is our anti viral software, it freezes a hard drive on your PC and this hard drive will revert back to the way it was originally. (for future reference) :)
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Lol ... learned a new thing :)

    Update it, and let us know the result.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:16.
Find Us