1. Join Date : Nov 2016
    Posts : 2
    Windows Ten
       3 Weeks Ago #1

    0x133, Watchdog while computer is idle for make than an hour or more?


    ASTRALGATE-Sat_11_12_2016_181141_60.zip

    I'm suspicious and im debating if its impending hardware failure, or something else. I have not installed any drivers recently, and only incurred a recent widnows update Possibly? I've been using windows 10 for a year. And it's most consistently given me hell, only for my gpu.

    Although my gpu has vert strict conditions in which it crashes. It wasnt a BSOD. (Driver crash, so it's my first suspect, considering that it's been acting up.) Although considering that this is happening while the gpu is less under load, makes me wonder if something else is going on?

    Windows has been ****ing with my drivers for quite awhile, so I can't really say where It's going with this.

    I just know that I'm getting a 0x133 STOP error, and I tried to diagnose it myself, but this particular stop error doesnt have symbols for me. So I have no idea whats going on. I ran an sfc /scannow and it was clean. So I had checked in case there was some corruption in system files.

    I really don't know what could be causing it. I ran the "Log collection" utility during the peak of much of my activity, so itll contain a lot of noise in terms of proccesses. I should've ran it when I just booted but. I've been working on solving it for the last 4 hours.

    It started exactly 2 days ago. When it woke me up with my computer whirring loudly 6 hours after I went to bed- my computer is loud on booting. I didn't shut it down. I'm not sure if there was a windows update during that time. I may have also lost power recently today? as the system reported losing power while I was asleep.

    Anyway I'm looking for a better direction on the problem. since I am not trained, and I don't have the skills to solve these sorts of problems myself.

    Edit: Add my power supply to a suspicion of hardware as there was no other reported power loss in the household anywhere else.

    Edit 2: Oh and if anyone finds anything strange, and you start pointing things out, mind explaining why you came to those conclusions, I'd like to improve and better self-diagnosis attempts in the future.
    Last edited by Fusioneko; 3 Weeks Ago at 20:44.
      My System SpecsSystem Spec


  2. Join Date : Apr 2014
    Space coast of Florida
    Posts : 4,039
    Windows 10 Pro X64 14393.105
       2 Weeks Ago #2

    No symbols available for build 14393.447 unfortunately so I can't get any useful info out of the dump. This is a Microsoft problem that they need to fix.

    Code:
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*G:\Symbols
    Symbol search path is: SRV*G:\Symbols
    Executable search path is: 
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 10 Kernel Version 14393 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
    Machine Name:
    Kernel base = 0xfffff803`cd691000 PsLoadedModuleList = 0xfffff803`cd996060
    Debug session time: Sat Nov 12 07:47:08.375 2016 (UTC - 5:00)
    System Uptime: 0 days 18:21:56.062
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
      My System SpecsSystem Spec


  3. Join Date : Nov 2016
    Posts : 2
    Windows Ten
       2 Weeks Ago #3

    Ztruker said: View Post
    No symbols available for build 14393.447 unfortunately so I can't get any useful info out of the dump. This is a Microsoft problem that they need to fix.

    Code:
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*G:\Symbols
    Symbol search path is: SRV*G:\Symbols
    Executable search path is: 
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 10 Kernel Version 14393 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
    Machine Name:
    Kernel base = 0xfffff803`cd691000 PsLoadedModuleList = 0xfffff803`cd996060
    Debug session time: Sat Nov 12 07:47:08.375 2016 (UTC - 5:00)
    System Uptime: 0 days 18:21:56.062
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Yeah I noticed that while debuggging on my own, I thought maybe I wasnt looking int he right places. Well heres to hoping for more information in the future. I may have isolated a culprit to a running program in the background. I've turned it off and see if It happens or not. Thanks for the up date.
      My System SpecsSystem Spec


  4. Join Date : Apr 2014
    Space coast of Florida
    Posts : 4,039
    Windows 10 Pro X64 14393.105
       2 Weeks Ago #4

    If it may be something starting at boot then you could use a Clean Boot to isolate it if the one you have not turns out not to be the cause.

    See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts
      My System SpecsSystem Spec


 


Similar Threads
Thread Forum
Solved AVG watchdog preventing computer from booting up
Last night I noticed quite abruptly that many of my apps had stopped working and the computer in general was acting very slow. I restarted the computer, but after the inital Toshiba opening screen the computer went blank with a little spinning...
AntiVirus, Firewalls and System Security
If computer is idle for an hour or so, it will not accept inputs
When I leave my Win 10 idle for an hour or so, it will stop all inputs, so I cannot do anything with it via my mouse or keyboard. I have tried plugging in a second keyboard, but still cannot access it. I have tried changing all of the settings to...
BSOD Crashes and Debugging
Computer Crashes-frecuency=1/hour-error 0x000001d8/debug log uploaded
Hi Forum, I bought last year a Lenogo Edge 15(i7 5500, 8gb RAM, NVIDIA 2gb, and ive got a lot of problems with it. Now the computer is crashing, so searching on the internet I found this Forum. I red the postings instructions, hope its fine the...
BSOD Crashes and Debugging
Computer stuck (100% disk usage) after exactly one hour of work
Hey, This is my last resort. I don't know what to do anymore except formatting my PC. Since a few days ago, my PC (Windows 10 on Dell XPS 15Z + 128GB SSD) is getting stuck EXACTLY 1 hour after reboot. I have reinstalled Windows 10 a few days...
Performance & Maintenance
1GB of RAM is being used while computer is idle!
This is bad, this is very bad. I don't like the fact it uses up so much memory, the computer needs this stuff and it is using so much of it! I just got this computer 3 days ago to replace my old one which was very slow. I don't want this to keep...
Performance & Maintenance
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 19:26.
Find Us
Twitter Facebook Google+



Windows 10 Forums