Windows 10: BSOD on startup - possibly caused by Windows Defender

Discus and support BSOD on startup - possibly caused by Windows Defender in Windows 10 BSOD Crashes and Debugging to solve the problem; I am experiencing constant BSOD shortly after startup after upgrading to the latest Windows 10 Preview Build(10532). It was happening in 10525, went... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by mjt1987, Aug 31, 2015.

  1. mjt1987 Win User

    BSOD on startup - possibly caused by Windows Defender


    I am experiencing constant BSOD shortly after startup after upgrading to the latest Windows 10 Preview Build(10532). It was happening in 10525, went away after restoring to retail build, then came back when upgrading to 10532.

    I've included a mini-dump. The BSOD goes away when disabling Windows Defender. I would like to be able to use the preview build as it has updates to the precision touchpad that make it much smoother. I also want to verify this is a windows issue and not something hardware related that the preview build brings to light.

    Memtest86 ran overnight with no issues. Hard drive sentinel found no problems as well.

    :)
     
    mjt1987, Aug 31, 2015
    #1
  2. Marie Ave Win User

    BSOD on Newly Bought Laptop Caused By Driver watchdog.sys

    Hi Brandon,

    It appears the code 0x00000113 is a VIDEO_DXGKRNL_FATAL_ERROR bug which indicates that the Microsoft DirectX graphics kernel subsystem has detected a violation.

    We suggest that you follow the steps provided in the Troubleshoot blue screen errors article.

    Let us know how it goes.
     
    Marie Ave, Aug 31, 2015
    #2
  3. BSOD on Newly Bought Laptop Caused By Driver watchdog.sys

    I was not using my PC for 30 minutes and then it suddenly blue screened without knowing the cause. I ran BlueScreenView and got this

    Bug Check Code: 0x00000113

    Parameter 1: 00000000`00000019

    Parameter 2: 00000000`00000002

    Parameter 3: 00000000`000010de

    Parameter 4: 00000000`00001c8c

    Caused By Driver: watchdog.sys

    Caused By Address: watchdog.sys+333e

    Processor: x64

    Crash Address: ntoskrnl.exe+1640e0

    SPECIFICATIONS:

    CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80Hz (8 CPUs), ~2.81 GHz

    GPU: NVIDIA® GeForce® GTX 1050Ti 4 GB GDDR5

    RAM: 8 GB DDR4

    Storage: 128 GB SSD + 1 TB HDD
     
    BrandonJLFlores, Aug 31, 2015
    #3
  4. axe0 New Member

    BSOD on startup - possibly caused by Windows Defender

  5. axe0 New Member
    Please try to upload the zip file again, it may be that the dump files are corrupted.
     
  6. mjt1987 Win User
    Hmm - strange. Here it is again. What about the single dump file in the first .zip attachment I posted?
     
    mjt1987, Aug 31, 2015
    #6
  7. axe0 New Member
    That dump is included with your 2nd upload, but unfortunately I couldn't get anything from it as it looks like it is corrupted too.
     
  8. mjt1987 Win User

    BSOD on startup - possibly caused by Windows Defender

    That is very strange. I ran the log program again - as administrator, lets see if this is any different.

    Also, could this be because I am running the Preview Build 10532, and therefore they are different dump files?

    I have ran Seatools and memtest without any issues already. I can ran the other ones tonight.

    First let me know if this .zip is any different.
     
    mjt1987, Aug 31, 2015
    #8
  9. axe0 New Member
    Yes, that could be possible, but I can't say for sure.
    Is there a specifically reason why you are still in the preview?

    The dumps are not different.
     
  10. mjt1987 Win User
    The XPS13 has a precision touchpad which is jerky in anything but MS Edge. The preview builds fix that. From your experience, if I have no problem with regular build, and disabling MS Defender removes the issue in Preview, should I be concerned? Especially since memtest and hard drive tests show no issue? The error codes are "page fault in non paged data" btw.
    I have a day left before I cannot return the laptop.
     
    mjt1987, Aug 31, 2015
    #10
  11. axe0 New Member
    How long have you ran memtest? How many passes?

    A wild guess about the error, either a driver has referenced wrong memory or the memory (RAM or the hard drive) are damaged.
     
  12. mjt1987 Win User
    I ran it for 4(I see now that you recommend 8, I can do that tonight).
    I'm curious why disabling windows defender would eliminate the issue though. I would think a driver or hardware problem would come up in other ways as well.
     
    mjt1987, Aug 31, 2015
    #12
  13. axe0 New Member

    BSOD on startup - possibly caused by Windows Defender

    It would be possible that some driver is interfering with it, but there are so many drivers that could do that.
    Yet, there are more methods that could cause it that are in the background.
     
Thema:

BSOD on startup - possibly caused by Windows Defender

Loading...
  1. BSOD on startup - possibly caused by Windows Defender - Similar Threads - BSOD startup possibly

  2. Windows Defender causing issues

    in Windows 10 BSOD Crashes and Debugging
    Windows Defender causing issues: Hello! Recently im getting more and more annoyed by the Windows Defender as it takes up 100% CPU by now and i cant open the Service Center because nothing happens when i click it. I cant restart the Service Center Service either because its greyed out for me and i cant...
  3. BSOD, minidump and help with possible cause

    in Windows 10 BSOD Crashes and Debugging
    BSOD, minidump and help with possible cause: Minidump I tried my best to get as much info out of this as possible, so far i have "SYSTEM_SERVICE_EXCEPTION (3b)" and "00000000c0000005" which means a memory access violation. I did a sfc, a memtest and such with no avail, but it does throw out "DEFAULT_BUCKET_ID:...
  4. Windows defender at startup

    in AntiVirus, Firewalls and System Security
    Windows defender at startup: How to ensure windows defender is active at start up? Win 10! https://answers.microsoft.com/en-us/protect/forum/protect_defender-protect_start-windows_10/windows-defender-at-startup/d9a1387a-c2c0-4547-ad1d-790dfe45c866
  5. BSOD - multiple fault buckets are possible cause?

    in Windows 10 BSOD Crashes and Debugging
    BSOD - multiple fault buckets are possible cause?: Hello, I am assisting some friends fixing their computer and I'm trying to Isolate the error. I was hoping to have assistance to diagnosing said error. In the windows error reporting I have noticed they have had multiple fault buckets over the past few months. Here is the...
  6. BSOD at startup ocassionally, possibly Nvidia drivers?

    in Windows 10 BSOD Crashes and Debugging
    BSOD at startup ocassionally, possibly Nvidia drivers?: Howdy, Upgraded to windows 10 from 8.1 (computer came with windows 7 originally), and now I am having all sorts of issues with windows 10. One of them being frequent BSODs during startup. BlueScreenView is showing ntoskrnl.exe is the problem (but as I have read here, most...
  7. BSOD caused by ntoskrnl.exe and ntkrnlmp.exe on startup

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by ntoskrnl.exe and ntkrnlmp.exe on startup: This happened after Dell came out and installed a new monitor in the machine. I am posting this from Safe Mode as we speak from the computer with the issue. I have tried running a chkdsk on the computer and it fixed some errors. I tried finding the logfile, but maybe I had...
  8. BSOD: Possibly caused by Errors on Hard Drive. Not sure...

    in Windows 10 BSOD Crashes and Debugging
    BSOD: Possibly caused by Errors on Hard Drive. Not sure...: For more on this BSOD (Crash), please refer to C Drive Missing in Windows 10 - Page 3 - Windows 10 Forums. Attachment 81014 51031
  9. Intermittent BSOD - Possible root cause?

    in Windows 10 BSOD Crashes and Debugging
    Intermittent BSOD - Possible root cause?: So I've been having quite a time with this computer. I upgraded a bunch of the hardware inside, nothing major, a 750ti/i3 setup just to game lightly on. It started out fine and over the course of a few weeks, I got more and more frequent BSODs, usually with...
  10. BSOD occurs at random times, possibly caused by ntkrnlmp.exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD occurs at random times, possibly caused by ntkrnlmp.exe: My memory dump is quite large, around 500 mb, so I cannot attach it here. I have compressed it into a .zip file and uploaded it to Dropbox. [Removed, see later post] I'll try and be as helpful as I can. The BSODs seem to happen at any time really, but most often during...