BSOD when computer idles - 0x101

Hi Maeson.

We can understand your frustration, but debugging has a very little to do with stop 0x101. Because .....

Code:

BugCheck 101, {19, 0, fffff88002fd7180, 3}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

The cause is always unknown for stop 0x101; the crash dump recording mechanism always fails to get it.

But from the description of the issue we get an idea that the issue is hardware related.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd7180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.

But the crash dumps does not provide any more information.
In order to search for the reason behind such a clueless BSOD, the best is to follow the possible causes of teh issue as summed up by H2SO4 .....

• BIOS bug
• a driver whose activity is causing the target processor to lock up
• a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)

You already enabled driver verifier which was not very helpful, but pointed to the Logitech Gaming Framework, and it was nicely covered by Laith earlier.

Code:

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  LCore.exe

The first thing is about overclocking. I noted that you said your system is not overclocked .... which may not be the fact as per the information available. Your processor's information ....

Code:

[Processor Information (Type 4) - Length 42 - Handle 0004h]
  Socket Designation            Socket 942
  Processor Type                Central Processor
  Processor Family              3fh - Specification Reserved
  Processor Manufacturer        AMD              
  Processor ID                  200f6000fffb8b17
  Processor Version             AMD FX(tm)-8350 Eight-Core Processor           
  Processor Voltage             8eh - 1.4V
  External Clock                200MHz
  Max Speed                     4000MHz
  Current Speed                 4000MHz
  Status                        Enabled Populated
  Processor Upgrade             Specification Reserved
  L1 Cache Handle               0005h
  L2 Cache Handle               0006h
  L3 Cache Handle               0007h

But the running state of the processor during the BSOD says ....

Code:

CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 0 21,2,0 AuthenticAMD 4334 0000000000000000                   203b3dfe

So apparently it is highly overclocked.

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too. How To Clear CMOS (Reset BIOS)

Report us for any further BSOD after doing it.

If you get any more BSOD, I would suggest you to clear CMOS following the method three as stated in How To Clear CMOS (Reset BIOS).

What is the situation after stopping overclocking?

No problem!

Good news. :)

Nice troubleshooting there, Laith! Your post #10 was the solution to the issue.