BSOD Secondary Processor

Hello Shaan and welcome to Sevenforums.

BSOD Analyse

Drivers

When the CLOCK_WATCHDOG_TIMEOUT happens, it's usually caused by a driver hogging the processor. Here's a canned speech that I'd suggest you to follow. The canned speech is not provided by me, and I won't take any credit for it. It's by carrona.org, our friend here at 7F.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Thank you,
Frederik.

The description you attached to your post is a very common way of gaining the BSOD, no worries there. Thank you for this update.

Best Regards,
Frederik.

shaan1 said:

Okay,

Now i have had driver verifier running for more then 36 hours including my regular stuff such as firefox thunderbird etc, my day to day programs that are always on but

so far no BSOD or crash so what is the next diagnoses step do i leave it running? until it does crash or is there something else we can do to find out?

Yet, I do not recommend troubleshooting your computer while the verifier is on. Once we'll have the BSOD verifier produced, I can dig more into a detailed dump - and finally get some conclusions.

For now you should just be using your computer as you're used to, until the BSOD drama happens. When it happens, you should wrap them up in a zip, and upload them. Thank you for your updates.

Best Regards,
Frederik.

Hey Shaan,

Let the verifier be turned on, because the produced dump doesn't give conclusions. Upload another dump when you've gotten one. We're still in the 0x101 corner, therefore - I recommend you to run some tests.

Memtest

Looking at your bugcheck it's likely that a memory corruption event were there. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors. To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

The 0x101 can also indicate a driver failing the processor, that's why I recommend you to leave the verifier on.

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

Thank you!
Frederik.

Hello Shaan.

Malwarebytes

Please do a full scan with Malwarebytes. You might want to run it twice as it won't always detect all the errors.
malwarebytes.org

SFC-command // Windows corrupt??

We usually ask people to do this command to check if Windows is corrupted. It's the most common one used to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

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

Leave verifier ON for now, the image was not loaded properly. We might want to wait for another crash to upload. Do what you're used to do when making the system crash.

Best Regards,
Frederik.