ntoskrnl.exe BSOD, random crashes

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 10 20H2
       #1

    ntoskrnl.exe BSOD, random crashes


    Hello all,

    I have been facing unexpected freezes and occasional BSOD for a couple of months. There is no pattern to this, my desktop can go for a couple of days with no incident and suddenly it freezes and I have to restart it. After the restart it may freeze again for a couple of times. At some point a BSOD occurs.

    My Windows 10 version is 20H2.

    Some additional information:
    windows 10 and all drivers are updated.
    sfc/scannow reports no corruption.
    dism reports no corruption and completes successfully.
      My Computer


  2. Posts : 1,404
    Windows 8.1 Enterprise x64
       #2

    Test RAM with memtest86 - MemTest86+ - Test RAM
    Connect RAM to other slots, start the computer with only one RAM chip and thus check the efficiency of all RAM chips and replace the RAM with another
      My Computer


  3. Posts : 6
    Windows 10 20H2
    Thread Starter
       #3

    No errors after 10 passes with memtest
      My Computer

  4. Ztruker's Avatar
    Posts : 13,701
    Windows 10 Pro X64 21H1 19043.1266
       #4

    Fill out System Specs for tenforums.

    See here: System Specs - Fill in at Ten Forums

    Fill out as much as you can, look at mine for an example of what can be included. The more information the better.

    Also noticed this in msinfo32.nfo under Components / Problem devices:

    Standard PS/2 Keyboard ACPI\PNP0303\4&8AB8035&0 This device is not present, is not working properly, or does not have all its drivers installed.

    Latest dump at 4/30 1:09PM shows this:
    Code:
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffff84812c729180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, The index of the hung processor.
    Are you doing any overclocking or over/under volting? If so, please reset all to nomional for awhile and see if that makes a difference.If it does then you can start tweqking again a little at a time until you find the safe settings for your system.
      My Computers


  5. Posts : 6
    Windows 10 20H2
    Thread Starter
       #5

    Ztruker said:
    Fill out System Specs for tenforums.

    See here: System Specs - Fill in at Ten Forums

    Fill out as much as you can, look at mine for an example of what can be included. The more information the better.
    Done :)

    Ztruker said:
    Also noticed this in msinfo32.nfo under Components / Problem devices:

    Standard PS/2 Keyboard ACPI\PNP0303\4&8AB8035&0 This device is not present, is not working properly, or does not have all its drivers installed.
    I can see this in Device Manager under hidden devices. I believe it's a general driver provided by Microsoft. I am using a Logitech keyboard with the SetPoint driver installed.

    Ztruker said:
    Latest dump at 4/30 1:09PM shows this:
    Code:
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: ffff84812c729180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, The index of the hung processor.
    Are you doing any overclocking or over/under volting? If so, please reset all to nomional for awhile and see if that makes a difference.If it does then you can start tweqking again a little at a time until you find the safe settings for your system.
    At the moment no. I used to but since the problem began I restored everything to the default settings.
      My Computer

  6. Ztruker's Avatar
    Posts : 13,701
    Windows 10 Pro X64 21H1 19043.1266
       #6

    Sorry for the late response. Let's try doing some stress testing.

    ===================================================
    Follow this tutorial to stress test your CPU:

    Prime95 - Stress Test Your CPU - Windows 10 Forums

    OCCT: OCBASE / OCCT

    For both the above, read the instructions carefully and watch your system when testing.
    If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

    For Intel CPUs (32 and 64 bit): Intel® Processor Diagnostic Tool

    The purpose of the Intel® Processor Diagnostic Tool is to verify the functionality of an Intel® microprocessor. The diagnostic tool checks for brand identification, verifies the processor operating frequency, tests specific processor features, and performs a stress test on the processor.
    ===================================================
    Follow this tutorials to stress test your GPU:
    FurMark - GPU Stress Test - Windows 10 Forums

    If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..

    Read the instructions carefully and watch your system when testing.
    If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall
    ===================================================

    Test your RAM
    Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
    DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

    Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:
    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

    If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.

    If this doesn't indicate any hardware problems then enable Driver Verifier and see if that yields a possible cause for the problem:

    Run Driver Verifier

    Driver Verifier-- tracking down a mis-behaving driver.

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /query

    If not active it will respond with

    No drivers are currently verified.

    Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

    Enable and Disable Driver Verifier in Windows 10

    Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.
      My Computers



  7. Posts : 6
    Windows 10 20H2
    Thread Starter
       #7

    Hello,

    I have successfully completed the requested stress tests.
    Code:
    Prime95		0 errors	3 hours
    OCCT		0 errors	1 hour
    MemeTest86	0 errors	14 passes
    Unigine		0 errors	18/18 scenes
    During the Unigine test the GPU temperature rose to about 90 degrees C and stayed there. I could probably clean the GPU and change it's thermal paste since it's been a while.

    Anyway I have activated the driver verifier and will let it run for 3-4 days.

    - - - Updated - - -

    I got a BSOD as soon as I rebooted my PC after configuring driver verifier.
    I have attached a new log collector zip file.
      My Computer

  8. Ztruker's Avatar
    Posts : 13,701
    Windows 10 Pro X64 21H1 19043.1266
       #8

    Code:
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
    Arg2: fffff80ca802244c, The address in the driver's code where the error was detected.
    Arg3: 0000000000000000, Pool Type.
    Arg4: 000000004c50534b, Pool Tag (if provided).
    *** WARNING: Unable to verify timestamp for PSINKNC.sys

    Code:
    STACK_TEXT:  
    fffff907`f6606668 fffff803`169dfe34 : 00000000`000000c4 00000000`00002000 fffff80c`a802244c 00000000`00000000 : nt!KeBugCheckEx
    fffff907`f6606670 fffff803`165acd45 : fffff803`16c22c98 00000000`00002000 fffff80c`a802244c 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xe0
    fffff907`f66066b0 fffff803`169d6df4 : 00000000`4c50534b fffff803`16c22c98 fffff80c`a802244c fffff803`16211ded : nt!VfReportIssueWithOptions+0x101
    fffff907`f6606700 fffff803`169e3ff2 : 00000000`00000000 00000000`00000000 00000000`000000c0 00000000`ffffffff : nt!VfCheckPoolType+0x90
    fffff907`f6606740 fffff80c`a802244c : 00000000`4c50534b 00000000`00000002 00000000`00000001 00000000`00000001 : nt!VerifierExAllocatePoolWithTag+0x62
    fffff907`f6606790 00000000`4c50534b : 00000000`00000002 00000000`00000001 00000000`00000001 00000000`00000000 : PSINKNC+0x2244c
    fffff907`f6606798 00000000`00000002 : 00000000`00000001 00000000`00000001 00000000`00000000 fffff80c`a802fe40 : 0x4c50534b
    fffff907`f66067a0 00000000`00000001 : 00000000`00000001 00000000`00000000 fffff80c`a802fe40 fffff907`f66067a0 : 0x2
    fffff907`f66067a8 00000000`00000001 : 00000000`00000000 fffff80c`a802fe40 fffff907`f66067a0 fffff80c`00000040 : 0x1
    fffff907`f66067b0 00000000`00000000 : fffff80c`a802fe40 fffff907`f66067a0 fffff80c`00000040 00000000`00000000 : 0x1
    Code:
    FOLLOWUP_IP: 
    PSINKNC+2244c
    fffff80c`a802244c 488bd8          mov     rbx,rax
    
    FAULT_INSTR_CODE:  48d88b48
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  PSINKNC+2244c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: PSINKNC
    
    IMAGE_NAME:  PSINKNC.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5fc70277
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  2244c
    
    FAILURE_BUCKET_ID:  0xc4_2000_VRF_PSINKNC!unknown_function
    
    BUCKET_ID:  0xc4_2000_VRF_PSINKNC!unknown_function
    
    PRIMARY_PROBLEM_CLASS:  0xc4_2000_VRF_PSINKNC!unknown_function
    psinknc.sys is part of Panda Cloud Antivirus and developed by Panda Security, S.L.

    Uninstall Panda Cloud Antivirus and run with Windows Defender/Security. Enable Driver Verifier again and see if it works better this time.

    No need for a antivirus other than Defender but if you feel you have to have one see if there is a newer version of Panda or try a different one.
    Again, not necessary as Defender is a very good antivirus program but your choice.
      My Computers


  9. Posts : 6
    Windows 10 20H2
    Thread Starter
       #9

    I uninstalled Panda Antivirus and re-activated the Driver Verifier. I got a new BSOD after the next reboot which was caused by the AMD driver. This is rather strange as it is an older driver which has been working flawlessly in Windows 10 for years.
      My Computer

  10. Ztruker's Avatar
    Posts : 13,701
    Windows 10 Pro X64 21H1 19043.1266
       #10

    Suggest trying a newer driver as the OS itself is always changing and what worked one day may not work well the next.
      My Computers


 
Page 1 of 2 12 LastLast

  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 14:55.
Find Us




Windows 10 Forums