Page 4 of 8 FirstFirst ... 23456 ... LastLast
  1.    27 Aug 2017 #31
    Join Date : Aug 2017
    Posts : 50
    Windows 10
    Thread Starter

    zbook asked: "In the logs I see a Nvidia graphics driver. Does your computer only have Nvidia graphics or are there hybrid Intel graphics?"

    So, there are both. When I first built the system I did not yet have the NVIDIA graphics card, so it was using integrated graphics for a few days. When I got the NVIDIA card, I installed it and installed the NVIDIA drivers.
      My ComputerSystem Spec
  2.    27 Aug 2017 #32
    Join Date : Aug 2017
    Posts : 50
    Windows 10
    Thread Starter

    Reading the Display Driver Uninstaller instructions and about to perform that next.

    Actually, as I re-read your responses, you're saying if I have updated the NVIDIA drivers since July 22nd I don't need to perform this step? I definitely have done that.
      My ComputerSystem Spec
  3.    27 Aug 2017 #33
    Join Date : Aug 2017
    Posts : 50
    Windows 10
    Thread Starter

    sfc /scannow seems stuck at verification 39 percent complete for the last 10 minutes or so.
      My ComputerSystem Spec
  4.    27 Aug 2017 #34
    Join Date : Aug 2017
    Posts : 50
    Windows 10
    Thread Starter

    Second time running sfc /scannow it worked fine. Here are the results:

    Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.


    C:\WINDOWS\system32>sfc /scannow


    Beginning system scan. This process will take some time.


    Beginning verification phase of system scan.
    Verification 100% complete.


    Windows Resource Protection did not find any integrity violations.


    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth


    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0


    Image Version: 10.0.15063.0


    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.


    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is C Drive.


    Stage 1: Examining basic file system structure ...
    317440 file records processed.
    File verification completed.
    7542 large file records processed.
    0 bad file records processed.


    Stage 2: Examining file name linkage ...
    388698 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.


    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    35630 data files processed.
    CHKDSK is verifying Usn Journal...
    40307496 USN bytes processed.
    Usn Journal verification completed.


    Windows has scanned the file system and found no problems.
    No further action is required.


    487806975 KB total disk space.
    146637116 KB in 168901 files.
    118568 KB in 35631 indexes.
    0 KB in bad sectors.
    441655 KB in use by the system.
    65536 KB occupied by the log file.
    340609636 KB available on disk.


    4096 bytes in each allocation unit.
    121951743 total allocation units on disk.
    85152409 allocation units available on disk.


    C:\WINDOWS\system32>powercfg.exe /hibernate off


    C:\WINDOWS\system32>
      My ComputerSystem Spec
  5.    27 Aug 2017 #35
    Join Date : Aug 2017
    Posts : 50
    Windows 10
    Thread Starter

    zbook you asked for the memory.dmp file. I posted this previously and in checking the file currently in c:/Windows/MEMORY.DMP it looks like the exact same as the one I posted before, modified 6 days ago (same day and time as the last one I posted.) Here's the link to the one I posted before:

    MEMORY.DMP - Google Drive

    Would you still like me to upload a new version of it?
      My ComputerSystem Spec
  6.    27 Aug 2017 #36
    Join Date : Apr 2017
    Posts : 8,645
    windows 10 professional version 1607 build 14393.969 64 bit

    The prior version of the memory dump had corruption.

    1) Please post a new version of the kernel memory dump file.

    2) Make sure that there is no over clocking while troubleshooting.

    Sometimes there are problems in the bios that produce bsod.

    3) To ensure that there are no improper bios settings please reset the bios.

    Sometimes there can be failure to boot after resetting the bios.

    4) So please make sure your files are backed up.

    5) Please make a backup image with Macrium:

    Macrium Software | Macrium Reflect Free:

    Macrium Software | Your Image is Everything

    Place the backup image on another drive or in a cloud application.

    6) Please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings

    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    7) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:

    Speccy - Free Download - Piriform: Speccy - System Information - Free Download


    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID


    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer


    1) download and install the Intel Processor Diagnostic Tool
    When the test completes please use the Microsoft snipping tool to post an image into the thread.


    Download Intel® Processor Diagnostic Tool: Download Intel® Processor Diagnostic Tool
    The Intel® Processor Diagnostic Tool: The Intel® Processor Diagnostic Tool
      My ComputerSystem Spec
  7.    27 Aug 2017 #37
    Join Date : Aug 2017
    Posts : 50
    Windows 10
    Thread Starter

    Here's a newly uploaded copy of the MEMORY.DMP file.

    MEMORY.DMP - Google Drive
      My ComputerSystem Spec
  8.    27 Aug 2017 #38
    Join Date : Aug 2017
    Posts : 50
    Windows 10
    Thread Starter

    Haven't reset CMOS yet but ran the Intel Processor Diagnostic Tool. Result: Pass

    Click image for larger version. 

Name:	Processor.JPG 
Views:	1 
Size:	99.4 KB 
ID:	150688
      My ComputerSystem Spec
  9.    27 Aug 2017 #39
    Join Date : Apr 2017
    Posts : 8,645
    windows 10 professional version 1607 build 14393.969 64 bit

    open file explorer > this PC > local c: drive > search for
    %SystemRoot%\MEMORY.DMP
    C:\Windows\MEMORY.DMP

    For the memory dump file please rename it to memory.old.dmp

    Download and install whocrashed: http://www.resplendence.com/whocrashed

    In the left upper corner above ananlyze click tools > crash dump test > type ACCEPT >

    After the crash dump > click analyze > post result into the thread

    Use file explorer to find the memory.dmp and post a share link into the thread.


    After resetting the bios and posting the new memory.dmp file please read the following information carefully.
    It is very important to read the warning on temperature monitoring before performing this test.

    Again please reset the bios before performing this test.

    And again make sure that there is no over clocking.

    Run Prime95 - Stress Test Your CPU
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials


    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials


    Please use the Microsoft snipping tool to post images into the thread.


    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials



    Code:
    ************* Symbol Path validation summary **************Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    No module list information.  Delay kernel load.
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Windows 8 Kernel Version 15063 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x00000000`00000000 PsLoadedModuleList = 0xfffff803`449e15c0
    Debug session time: Mon Aug 21 21:59:12.223 2017 (UTC - 5:00)
    System Uptime: 0 days 3:28:46.546
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    No module list information.  Delay kernel load.
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Loading Kernel Symbols
    No module list information.  Delay kernel load.
    GetContextState failed, 0x80004002
    CS descriptor lookup failed
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Unable to get program counter
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 101, {18, 0, ffff9900a8ad9180, 6}
    
    
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
    
    
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    ReadControl failed - kernel symbols must be loaded first
    ReadControl failed - kernel symbols must be loaded first
    ReadControl failed - kernel symbols must be loaded first
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    Unable to get current machine context, HRESULT 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
    GetContextState failed, 0x80004002
      My ComputerSystem Spec
  10.    27 Aug 2017 #40
    Join Date : Aug 2017
    Posts : 50
    Windows 10
    Thread Starter

    Belowis the crash dump result from WhoCrashed. I am currently uploading the new MEMORY.DMP, it is almost 3 GB in size.

    Next will be the CMOS reset. And then Prime95 test.

    Re: overclocking, I have not made any changes to set any overclocking anywhere. BIOS was set to load defaults earlier today. Apart from that, what can I be checking to see if anything is overclocked perhaps by default?




    Crash Dump Analysis

    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.



    On Sun 8/27/2017 4:53:37 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\082717-4218-01.dmp
    This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
    Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x199D6B5F, 0x3C2A58ED)
    Error: MANUALLY_INITIATED_CRASH1
    file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
    product: WhoCrashed
    company: Resplendence Software Projects Sp.
    description: Resplendence WhoCrashed Crash Dump Test
    Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



    On Sun 8/27/2017 4:53:37 PM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
    Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x199D6B5F, 0x3C2A58ED)
    Error: MANUALLY_INITIATED_CRASH1
    file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
    product: WhoCrashed
    company: Resplendence Software Projects Sp.
    description: Resplendence WhoCrashed Crash Dump Test
    Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



    On Sat 8/26/2017 12:49:12 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\082617-4171-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
    Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFA50194347180, 0x7)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft Windows Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 8/26/2017 9:50:07 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\082617-4437-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
    Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFA980F04C0180, 0x6)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft Windows Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





    Conclusion


    4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



      My ComputerSystem Spec

 
Page 4 of 8 FirstFirst ... 23456 ... LastLast


Similar Threads
Thread Forum
BSOD CLOCK_WATCHDOG_TIMEOUT (& Others) On Some Games
Hi, I've had Multiple BSOD's While playing (High End) games. While playing games such as GTA IV or Player Unknown i have had multiple BSOD, this only seems to happen on games that require a lot of power to run. I have played games like ORI &...
BSOD Crashes and Debugging
Solved Diagnosing BSOD that only occurs while playing crysis 3
The error read - Session "EventLog-AirSpaceChannel" stopped due to the following error: 0xC0000188 Before anyone asks: Yes, my CPU overclock is stable. I ran intel's extreme tuning utility for 6+ hrs (temps rarely go above 73c...
BSOD Crashes and Debugging
CLOCK_WATCHDOG_TIMEOUT BSOD While Playing Hardware Intensive Games
Hey everybody, I've been struggling with this issue for a while, I thought I resolved it a few months ago but it has come back and I'm out of ideas. Ever since upgrading to Win10 at the start of last year I've started getting Clock Watchdog...
BSOD Crashes and Debugging
BSOD when playing games intensive games 0x00000124
A friend of mine is having bsod issues when playing certain games, example: Rainbox six siege, Battlefield One (BETA) and a few others. Wondering if anyone can give us a clue as to the cause. Windows Format is done, but to no avail,...
BSOD Crashes and Debugging
BSOD CLOCK_WATCHDOG_TIMEOUT playing any Game
Constantly getting CLOCK_WATCHDOG_TIMEOUT, while playing anything. GTA V it happens 10-20 minutes of starting the program. CS:GO it crashes 20-30 minutes later. I've tried analyzing the DMP files but they point to ntkrnlmp.exe. I've...
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 23:22.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums