New
#31
Code:BugCheck 1E, {0, 0, 0, 0} Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )Code:Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOSThe kernel detected a illegal or unknown processor instruction, this may be reason why it is pointing to a hardware issue, I would follow these steps:Code:1: kd> !error c000001d Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:
Additional Help - Using Driver Verifier to identify issues with Drivers
We seem to be picking up quite a few problematic drivers from this, so there may be other programs or drivers which are causing the bugchecks.
We can stress test the CPU for any problems also:
Enable "Round off checking" before the test (see first post below tutorial).