BSOD While running OCCT


  1. Posts : 2
    Windows 10 64 bit
       #1

    BSOD While running OCCT


    On Sun 04-Sep-16 10:21:03 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\090416-8484-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
    Bugcheck code: 0x139 (0x3, 0xFFFFD00027C3C5B0, 0xFFFFD00027C3C508, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: The kernel has detected the corruption of a critical data structure.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 04-Sep-16 10:21:03 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x139 (0x3, 0xFFFFD00027C3C5B0, 0xFFFFD00027C3C508, 0x0)
    Error: KERNEL_SECURITY_CHECK_FAILURE
    Bug check description: The kernel has detected the corruption of a critical data structure.
    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 03-Sep-16 5:32:50 PM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\090416-8500-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
    Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFD0018FB84180, 0x2)
    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.


    Hi all
    I tried to overclock my cpu i7-6700k on asus rog viii ranger mobo with corsair vengeance lpx ddr4-3000 memory to 4.6Ghz. It was running fine, playing games etc. But when i run the OCCT, it BSOD. Below are the information from WhoCrashed. I could not upload the memory dump and minidump even after 10 times...not sure why.. I hope I have not spoil my cpu or memory. Please help. Thanks.


    On Sat 03-Sep-16 11:09:15 AM GMT your computer crashed

    crash dump file: C:\WINDOWS\Minidump\090316-8515-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
    Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFD0012A795180, 0x5)
    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.
      My Computer


  2. Posts : 17
    Windows10 Pro
       #2

    Read and follow instructions here: BSOD - Posting Instructions
      My Computer


  3. Posts : 2
    Windows 10 64 bit
    Thread Starter
       #3

    DonCeCo said:
    Read and follow instructions here: BSOD - Posting Instructions
    Thanks! ...here the attached.
      My Computer


 

  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 13:47.
Find Us




Windows 10 Forums