BSOD - Clock Interrupt was not received - Windows 7 x64

If you've gone through the 1-5 check list for *124's I posted above and you are still crashing, that appears to be the case, yes.

Regards,

Patrick
 
Just my 2¢:

Although damage from overclocking is not unheard of, most CPU's have a built in cutoff that will prevent damage (this doesn't mean that the CPU is OK, it just means that it's not likely it was damaged by overclocking).
To test the CPU, try the free CPU stress tests here: Hardware Diagnostics
Watch the system while testing - do not leave it alone (in case the CPU's cutoff may be broken).

Overclocking not only stresses the CPU, but in turn the CPU stresses other components.
And, the tests that we run are based on normal, un-overclocked systems - so we can't predict the results that they will give when used on an overclocked system.
 
The attached DMP file is of the KERNEL_DATA_INPAGE_ERROR (7a) bug check.

This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

BugCheck 7A, {fffff6fc4006bf80, ffffffffc00000c0, 2b4728be0, fffff8800d7f0000}

ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

Looks like HDD failure, or some sort of conflict. After looking at your drivers I noticed - fttxr5_O.sys Thu Feb 15 03:15:03 2007

This is a very old driver for the Promise® FastTRAK TX4200/TX4300, which appears to be a PCI-based BUS adapter for serial ATA drives. Are you actively using this? I believe it may be playing a role in your crashes here. Remove it if you can without repurcussions. Also please go ahead and run Chkdsk (paste log afterwards) and then Seatools:

Chkdsk:
There are various ways to run Chkdsk~

Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick
 
What's weird is I installed some drivers from 2009. But I'm going to replace the PCI Sata controller card anyway.

What are some good brands for a PCI-e slot?
I'm currently looking at some Highpoint RocketRaid cards
 
Honestly, I couldn't say. I don't have much knowledge as far as PCI-e RAID cards go. I would just get one that is newer generation and has device drivers that will work with 7, 8, 8.1, etc.

Regards,

Patrick
 
Just another bug check that further supports my theory of your PCI RAID device being the culprit.

CRITICAL_OBJECT_TERMINATION (f4)

This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

EXCEPTION_CODE: (Win32) 0xbc4eb50 (197454672) - <Unable to get error code text>

This is the type of bug check you see usually when you're dealing with something in regards to your file system as far as hardware goes (HDD, SDD, RAID cards, etc).

Regards,

Patrick
 
Thanks for the PM reminder, evidently I looked at this and closed it on accident whenever that was. It's not rare for me to do that because I always have so many tabs open.

Right, so it's of the same bug check as we've seen.

Did you ever get around to replacing/removing the RAID card?

Regards,

Patrick
 
Yeah that got replaced pronto. Now have a RocketRAID 640 controller card. Operating smoothly. Support Windows 7... made sure of that!

Did this recent BSOD dump point to any particular hardware?
 
Great, was just making sure.

It's a minidump, so there's unfortunately not much I can really salvage from it other than what we've seen in other 0xF4's. If you can provide a kernel-dump + enable Driver Verifier, that would be fantastic:

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

2. Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8/8.1, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

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 - 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)
- DDI compliance checking (Windows 8)
- 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. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled, 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 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?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
 
Let me know when the kernel-dump is generated, it looks like I'll be needing it.

Regards,

Patrick
 
Generation of kernel-dumps is enabled, correct?

If so, let's just wait for the next crash. Let me know if it generates.

Regards,

Patrick
 

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

Back
Top