Page 2 of 3 FirstFirst 123 LastLast
  1.    02 Sep 2017 #11
    Join Date : Sep 2017
    Posts : 14
    Windows 10
    Thread Starter

    still crashing...i might just buy another wireless card

    I also needed to repair my C:/ drive while windows was starting after a BSOD

    Is that caused by crashing at a bad time?
      My ComputerSystem Spec
  2.    02 Sep 2017 #12
    Join Date : Apr 2017
    Posts : 8,827
    windows 10 professional version 1607 build 14393.969 64 bit
      My ComputerSystem Spec
  3.    03 Sep 2017 #13
    Join Date : Jun 2015
    Posts : 12,865
    Windows 10 Pro

    Quote Originally Posted by Kronox001 View Post
    still crashing...i might just buy another wireless card

    I also needed to repair my C:/ drive while windows was starting after a BSOD

    Is that caused by crashing at a bad time?
    That is possible
      My ComputersSystem Spec
  4.    03 Sep 2017 #14
    Join Date : Sep 2017
    Posts : 14
    Windows 10
    Thread Starter

    i got a CLOCK_WATCHDOG_TIMEOUT BSOD(didn't get the dump file because it was stuck on 0%), can that also happen because of the bad wireless driver?

    I'll have a new wireless card tommorow
      My ComputerSystem Spec
  5.    03 Sep 2017 #15
    Join Date : Apr 2017
    Posts : 8,827
    windows 10 professional version 1607 build 14393.969 64 bit

    ...
      My ComputerSystem Spec
  6.    04 Sep 2017 #16
    Join Date : Sep 2017
    Posts : 14
    Windows 10
    Thread Starter

    I'm still freezing and getting the same bsod

    I uninstalled my wireless pci card(netr28x is gone) and removed it from my pc
    I'm using a TP-Link wireless usb now

    This is the new crash dump
      My ComputerSystem Spec
  7.    04 Sep 2017 #17
    Join Date : Jun 2015
    Posts : 12,865
    Windows 10 Pro

    0x133 with first param being 1 means something ran an extended period of time in an IRQL level of 2 or higher (IRQL = importance order in which the CPU processes things, the higher the earlier with a max of 13)
    Since it looks like multiple drivers are internally delaying execution, and a minidump isn't sufficient to identify which drivers cause this issue, I'm taking a different approach than normally.

    Please follow below instructions
    - Download the Windows Software Development Kit (SDK) executable from Windows 10 SDK - Windows app development,
    - Run in, when you get at the part where you can choose what to install, select only Windows Performance Toolkit,
    - Open an elevated command prompt,
    - Enter following command, this makes it easier to access the tool we need
    Code:
    SET PATH=%PATH%;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\
    If your SDK is installed on a different location, please change the path to specify the right path
    - Enter following command
    Code:
    xperf -on DiagEasy
    - Wait an extensive period and then run following command, preferable after you noticed some performance issues
    Code:
    xperf -d "%userprofile%\Desktop\trace.etl"
    Please upload the trace.etl to onedrive, google drive or dropbox and post a share link. Trace.etl will be too large to upload directly.
      My ComputersSystem Spec
  8.    04 Sep 2017 #18
    Join Date : Sep 2017
    Posts : 14
    Windows 10
    Thread Starter

    After i posted the new crash dump i noticed an older version of the wireless pci card driver in hidden devices in my Network adapter list in Device Manager and uninstalled it

    If i still crash now il do the Performance toolkit

    (I also did a Intel Processor Diagnostic without any problems)
      My ComputerSystem Spec
  9.    05 Sep 2017 #19
    Join Date : Sep 2017
    Posts : 14
    Windows 10
    Thread Starter

    Ran it for about 4 hours: trace.etl - Google Drive

    Some more info: Got another CLOCK_WATCHDOG crash yesterday night, it happenend while i was clicking through different times on a youtube video

    Since CLOCK_WATCHDOG can be caused by overclocking I've also defaulted my bios

    I've used "Show and hide updates" to try and stop windows from installing drivers for usb devices

    I told the place i bought the pc from that i was getting Watchdog errors and they just linked me this to solve it: How to fix my CLOCK_WATCHDOG_TIMEOUT error - [Solved] - CPUs
      My ComputerSystem Spec
  10.    05 Sep 2017 #20
    Join Date : Sep 2017
    Posts : 14
    Windows 10
    Thread Starter

    I've also just had a problem where a program wouldn't start and the process in Task Manager couldn't be ended, I read somewhere it could be a anti virus problem so i uninstalled the BullGuard AV 30 day trial that came with the PC and the program started while i was uninstalling it. Dont know if that could also cause those BSOD's
      My ComputerSystem Spec

 
Page 2 of 3 FirstFirst 123 LastLast


Similar Threads
Thread Forum
BSOD Alienware 15 R1, Error 0x124 and 0x133 hal.dll and ntoskrnl.exe
Hello! I'm having BSOD problems like DPC_WATCHDOG_VIOLATION and WHEA_UNCORRECTABLE_ERROR caused by hal.dll and ntoskrnl.exe. I'm using an Alienware 15 R1 with Intel i7 4710HQ with GTX980M and 16GB DDR3 RAM. This started somewhere around the middle...
BSOD Crashes and Debugging
[BSOD] I got random BSOD with ntoskrnl, please save me!
Hello, my PC recently has been receiving a lot of random BSODs . It comes suddenly when I surf the internet, or watching youtube videos. I was thinking that it all comes from my VGA card, but I can still play games such as Dota2 in Ultra settings...
BSOD Crashes and Debugging
BSOD playing Battlefield 1, error 0x133 DPC_WATCHDOG_VIOLATION
Hi there! I just got my Asus Strix 1070 yesterday, updated the bios for the micron memory fix, and today, after playing a long session of Battlefield 1, I got a "DPC Watchdog Violation" Bluescreen 0x133. Can anyone help me fix this issue? The GPU...
BSOD Crashes and Debugging
DPC_WATCHDOG_VIOLATION 0x133
My computer started freezing randomly after updating to Windows 10 (from win7). Mouse completely frozen, keyboard unresponsive. The only thing I could do was a hard reboot every time. I tried searching for info online and found lots of people...
BSOD Crashes and Debugging
BSOD code 0x133 caused by hal.dll & ntsokrnl.exe
I'm running a genuine MSDN copy of Windows 10 Enterprise. Recently from past month, the laptop has started behaving weirdly. Earlier the issue was that it would hang and after waiting hours I had to shut it down forcibly and then when re-starting,...
BSOD Crashes and Debugging
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 04:44.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums