[Win7] BSOD

D

devilishlyx

New member
Joined
Jun 13, 2014
Posts
4
· OS - Windows 8.1, 8, 7, Vista ? Windows 7
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? Windows 7 x64 ultimate - custom built PC
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? full retail
· Age of system (hardware) 2 years approx
· Age of OS installation - have you re-installed the OS? 2 years approx

· CPU i5 2500k
· Video Card GTX 680
· MotherBoard P8Z680-V GEN 3
· Power Supply - brand & wattage (if laptop, skip this one) Corsair CMPSU-750TXV2UK Enthusiast Series TX750 V2 High Performance 750W Power Supply

· System Manufacturer Myself (custom built)
· Exact model number (if laptop, check label on bottom) ?

· Laptop or Desktop? Desktop


I should give some more information on this problem, so here goes. Sporadically, mostly while playing graphically intensive games, my pc will freeze for 10 seconds, then come up with a blue screen error, stating something along the lines of 'clock interrupt not received on secondary processor'. It started fairly recently and now appears more and more often. I would really love it if someone could help me fix this before it gets too bad. Thank you so much in advance!
 

Attachments

Last edited:
Re: BSOD windows 7

Hi,

There are no DMP files located in your output folder. Please manually navigate to C:\Windows\Minidump and zip up any and all crash dumps, and then attach to your next post.

Regards,

Patrick
 
Re: BSOD windows 7

Not a problem, thanks very much!

This looks like a faulty processor at first glance given the bug checks (0x9C and 0x101). With that said, to be absolutely sure, I'll require you to please do two things:

1. Enable generation of kernel-dumps:

-- Creating a Kernel-Mode Dump File (Windows Debuggers)

-- After enabling generation, kernel-dumps are located at C:\Windows and named MEMORY.DMP.

-- You will need to upload it to somewhere such as Mediafire, Onedrive, etc, as it'll be too large to attach here.

2. Once you have kernel-dumps set, please enable Driver Verifier as well:

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8/8.1)
- DDI compliance checking (Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel-Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

Using Driver Verifier to identify issues with Windows drivers for advanced users


After both of the above are done, when the system goes ahead and crashes, please paste the link to the crash dump.

Regards,

Patrick
 
Re: BSOD windows 7

Bad news.

CLOCK_WATCHDOG_TIMEOUT (101) bug check again.

This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

Also, the dump itself is extremely corrupt:

Code: 
Unable to read PsLoadedModuleList
Page 9e0015d08 too large to be in the dump file.
GetContextState failed, 0x80004002
CS descriptor lookup failed
Page 9e0015d08 too large to be in the dump file.
GetContextState failed, 0x80004002
Page 9e0015d08 too large to be in the dump file.
GetContextState failed, 0x80004002
Page 9e0015d08 too large to be in the dump file.
GetContextState failed, 0x80004002
Page 9e0015d08 too large to be in the dump file.
GetContextState failed, 0x80004002
Unable to get program counter
Page 9e0015d08 too large to be in the dump file.
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
Page 9e0015d08 too large to be in the dump file.
GetContextState failed, 0x80004002
Page 9e0015d08 too large to be in the dump file.
GetContextState failed, 0x80004002

As I said above, very likely this is a faulty CPU. The final recommendation I will make is to go ahead and run Memtest for NO LESS than ~8 passes (several hours) to be sure your RAM is okay.

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
Re: BSOD windows 7

At the moment, I neither have a working DVD drive (long story due to incompatibility upon making the PC) or a working USB stick. Given the results you saw earlier, is it pretty much definite that it's the i5 processor? If so, I have meant to upgrade to an i7 for a long time for faster video rendering, so this may be the ideal time to make that push. Would you need to have the information from this Memtest program to verify it isn't indeed the RAM, or is it likely it's either the processor, or the processor AND the ram? If it could be both, maybe it would be best for me to get a USB drive asap.
 
Re: BSOD windows 7

I am very confident this is a bad processor given the 0x9C bug check + 0x101 together, especially with an 0x101 after enabling verifier (it was also corrupt). However, when dealing with a processor being the possible issue, you always want to be sure. With that said, this is why I recommended running Memtest (the only thing left on the system that could cause these symptoms).

If you'd like to however leap for a new CPU before running Memtest given this unfortunate opportunity, that's entirely up to you.

Regards,

Patrick
 
Re: BSOD windows 7

The OP says that the processor is over-clocked which may mean that the processor has been damaged permanently due to the over-clock or is not stable at this over-clock settings. Before changing the processor, I would suggest that you revert back to the stock settings and see if the BSOD's are still happening or not?
 
Re: BSOD windows 7

You're right.

A small note, the processor is overclocked. Would reverting some of the overclock help the situation?
Click to expand...

It would definitely help if I learned to read :grin1:

I would 100% blame this on an unstable OC, yes. Your CPU is likely fine if this is the case. Undo the OC ASAP!

Regards,

Patrick
 
Re: BSOD windows 7

Patrick said:
You're right.

A small note, the processor is overclocked. Would reverting some of the overclock help the situation?
Click to expand...

It would definitely help if I learned to read :grin1:

I would 100% blame this on an unstable OC, yes. Your CPU is likely fine if this is the case. Undo the OC ASAP!

Regards,

Patrick
Click to expand...

Oh you are right with your problem. I would have taken plenty of sleep (Almost a day to be precise:thumbsup2:) if I were in your place.:grin1:
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top