[SOLVED] BSOD, Crashes - Windows 7 x64

[ytraccm]

Removed, KB3022345. ran sfc/exe/scannow ran sfcdetails.txt always the same errors with and without KB3022345 installed. With a simple task of playing a song, MSFT Media Player, screen freeze between 30 sec and 1 min 7 sec. Disabled AMD Turbo Core Technology, Reboot 2; 8 sec to lock up. Reboot 3; Adjust cpu Ratio from Auto to [4]. Reboot 4 lock up 7 sec. Reboot 5; Set HT Link Speed to [1] from Auto. Reboot 6; 21 sec to lock up. Reboot 7; song plays 2 min 13 sec to lock up. Reboot 8; Adjust CPU-NB Ratio from Auto to [4]. Reboot 9; song play to 20 minutes with internet active before screen locks. Reboot 10; run sfc.exe and sfcdetails.txt without KB3022345 installed, same errors as with KB20223454 installed, go to internet sysnative.com screen locks. Reboot 11; ran perfmon/report and for several minutes no lock up.

Self inflicted wound, self assembled unit, MSI 970 motherboard, MSI NVIDIA GeForce GTX 960 video card, AMD FX 8350 Eight-Core Processor, 16 GB RAM. Asus 802.11 Network Adapter, Win7 x64.

For 2 months I have tried to accomplish a use full computer with out success, hopefully with your kind help that will change. Much Thanks.

 

[Jared]

You're getting 0x101 bugchecks.
We'll need a Kernel memory dump from C:\Windows\memory.dmp.

 

[ytraccm]

computer name: OWNER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: MS-7693, MSI, 970 GAMING (MS-7693)
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 34305515520 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 5/18/2015 11:55:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051815-25537-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002EA5180, 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 be caused by a 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 Mon 5/18/2015 11:55:58 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002EA5180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 5/18/2015 12:02:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051715-31699-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002EFB180, 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 be caused by a 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 Sun 5/17/2015 11:25:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051715-22011-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002E88A40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT



On Fri 5/15/2015 12:30:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051415-35568-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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 be caused by a 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 Mon 5/11/2015 11:35:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051115-38657-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F65180, 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 be caused by a 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 Sun 5/10/2015 8:42:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051015-40404-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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 be caused by a 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.

 

[Jared]

Upload the dump file on C:\Windows\MEMORY.dmp to a file sharing site and post the download link here.

 

[ytraccm]

Upload the dump file on C:\Windows\MEMORY.dmp to a file sharing site and post the download link here.

A million thanks. I got it. Reset motherboard defaults. Worked my way through Bios and driver updates from MSi download center. Set motherboard HT Link from Auto to 1. For the first time I am able to run Extended HDD test. No .dmp to upload. Thanks again. Extremely nice of you to help out.