BSOD, Win10 Not creating DMP files. Sonic Wall VPN Client culprit?

  1. Posts : 4
    Windows 10 Pro 64bit

    BSOD, Win10 Not creating DMP files. Sonic Wall VPN Client culprit?

    Hello, I need help with my Windows 10 PC not creating memory.dmp files upon BSOD. The attached debug files are likely referencing the last BSOD for which a minidump or memory.dmp was created. Since then I have had 2 more BSOD's, each time forgetting to write down the error code on the actual Blue Screen, and no record of the crash appears in the Event Viewer, just that the computer was not cleanly shut down. I ran a program call "WhoCrashed" which only found the minidump from 9-24, and identified Dell Sonicwall Global VPN Client as the likely culprit.

    Here are the details of that report:

    On Thu 9/24/2015 6:58:02 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092415-6343-01.dmp
    This was probably caused by the following module: swipsec.sys (0xFFFFF801ADA52555)
    Bugcheck code: 0xD1 (0xFFFFE00044AEA000, 0x2, 0x0, 0xFFFFF801ADA52555)
    file path: C:\Windows\system32\drivers\swipsec.sys
    product: Dell SonicWALL Global VPN Client
    company: Dell SonicWALL, Inc.
    description: Dell SonicWALL VPN Client IPsec Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: swipsec.sys (Dell SonicWALL VPN Client IPsec Driver, Dell SonicWALL, Inc.).
    Google query: Dell SonicWALL, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

    I am more concerned with Windows not creating dump files right now than I am with the actual BSOD's as I have only had two in the last two weeks or so, so they are not super frequent.

    After the first BSOD with no memory dump I changed the "Write Debugging information" setting in Startup and Recovery to "Automatic Memory Dump", and set the Paging File to system managed.

    After the 2nd BSOD with no memory dump I changed the "Write Debugging information" setting in Startup and Recovery to "Kernel memory dump" and kept the Paging file set to system managed.

    See Below.
    Attachment 41967Attachment 41968

    I have also attached the requested debug file. Any help is appreciated.
      My Computer

  2. axe0's Avatar
    Posts : 14,863
    Windows 10 Pro

    Hi ComponentActual,

    Minidump - Configure to create in Windows 10

    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
      My Computers


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

Designer Media Ltd
All times are GMT -5. The time now is 01:25.
Find Us

Windows 10 Forums