BSOD - Clock Interrupt was not received - Windows 7 x64

Uninstall Afterburner temporarily - you can reinstall it after the system has been stabilized.
 
Another BSOD. And this was while my computer was not logged in.
"A process or thread crucial to system operation has unexpectedly exited or been terminated."

Here's the memory dump link.
 
Code: 
[COLOR=#ff0000]BugCheck F4[/COLOR], {[COLOR=#0000ff]3[/COLOR], [COLOR=#008000]fffffa800c0f9320[/COLOR], fffffa800c0f9600, fffff8000378f980}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Code: 
[COLOR=#008000]!process fffffa800c0f9320 3[/COLOR]
GetPointerFromAddress: unable to read from fffff800036c2000
PROCESS fffffa800c0f9320
    SessionId: none  Cid: 0250    Peb: 7fffffdf000  ParentCid: 0208
    DirBase: 2b0061000  ObjectTable: fffff8a0036b63a0  HandleCount: <Data Not Accessible>
    Image: wininit.exe
    VadRoot fffffa800c1f3f70 Vads 62 Clone 0 Private 613. Modified 95. Locked 2.
    DeviceMap fffff8a000006090
    Token                             fffff8a0036bd060
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
    ElapsedTime                       00:00:00.000
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         96928
    QuotaPoolUsage[NonPagedPool]      9976
    Working Set Sizes (now,min,max)  (1431, 50, 345) (5724KB, 200KB, 1380KB)
    PeakWorkingSetSize                1431
    VirtualSize                       45 Mb
    PeakVirtualSize                   49 Mb
    PageFaultCount                    1802
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      723

Code: 
6: kd> [COLOR=#008000]!dpx[/COLOR]
Start memory scan  : 0xfffff88002eda0f8 ($csp)
End memory scan    : 0xfffff88002edb000 (Stack Base)

               rax : 0xfffff88002eda188 : 0xfffff80003743594 : nt!NtTerminateProcess+0x284
               rsp : 0xfffff88002eda0f8 : 0xfffff80003818e42 : nt!PspCatchCriticalBreak+0x92
               rbp : 0xfffff8000378f980 :  !da ""Terminating critical process 0x%p (%s).""
               rsi : 0xfffffa800c0f9600 :  !da "wininit.exe"
                r9 : 0xfffffa800c0f9600 :  !da "wininit.exe"
               r11 : 0xfffff88002eda1f8 : 0xfffff800034877d3 : nt!KiSystemServiceCopyEnd+0x13
0xfffff88002eda0f8 : 0xfffff80003818e42 : nt!PspCatchCriticalBreak+0x92
0xfffff88002eda118 : 0xfffffa800c0f9600 :  !da "wininit.exe"
0xfffff88002eda120 : 0xfffff8000378f980 :  !da ""Terminating critical process 0x%p (%s).""
0xfffff88002eda188 : 0xfffff80003743594 : nt!NtTerminateProcess+0x284
0xfffff88002eda1f8 : 0xfffff800034877d3 : nt!KiSystemServiceCopyEnd+0x13
0xfffff88002eda368 : 0xfffff80003483d90 : nt!KiServiceLinkage
0xfffff88002eda3d8 : 0xfffff880012cb785 : [COLOR=#ff0000]fltmgr!FltpFreeIrpCtrl+0x145[/COLOR] <<< Related to [URL="http://msdn.microsoft.com/en-us/library/windows/hardware/ff548670%28v=vs.85%29.aspx"]IRP_MJ_FILE_SYSTEM_CONTROL[/URL]?
0xfffff88002eda690 : 0xfffff88002eda848 : 0xfffff800036c5ac0 : nt!MmFreePageListHead
0xfffff88002eda698 : 0xfffff88001459764 : [COLOR=#ff0000]Ntfs!NtfsFsdRead+0x2d4[/COLOR]
0xfffff88002eda7c8 : 0xfffff80003497b26 : nt!MiInsertPageInFreeOrZeroedList+0x186
0xfffff88002eda848 : 0xfffff800036c5ac0 : nt!MmFreePageListHead
0xfffff88002eda868 : 0xfffff800034b0025 : nt!RtlGetExtendedContextLength+0x19
0xfffff88002eda970 : 0xfffff800034c3404 : nt!KiDispatchException+0x348
0xfffff88002edaa38 : 0xfffff80003487bc2 : nt!KiExceptionDispatch+0xc2
0xfffff88002edaa60 : 0xfffffa800c0f9601 :  !da "ininit.exe"
0xfffff88002edac18 : 0xfffff8000348673a : nt!KiPageFault+0x23a
0xfffff88002edac20 : 0x0000000000000001 :  Trap @ fffff88002edac20

The Ntfs!NtfsFsdRead+0x2d4 seems to be used with a file system driver to read from a file object. It's not documented, so I'm basing my assumption around some code posted on ReactOS.

It does seem related to the storage stack, or the at least the file system.

Which hard drive diagnostic tests have you taken? Do you have a SSD?
 
Which hard drive diagnostic tests have you taken? Do you have a SSD?
Click to expand...

I've used HD Tune Pro 5.50
And yes I have an OCZ Vertex 3 120GB SSD

I also have a SATA controller PCI card - Promise FastTrak TX4310.... unsure if this helps
 
Have you checked you have the latest firmware for your SSD, and checked you have the latest SATA and chipset drivers?
 
In addition to BlueRobot's recommendations, I would use Seatools as opposed to HDTune for testing a hard disk:

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
 
x BlueRobot said:
Have you checked you have the latest firmware for your SSD, and checked you have the latest SATA and chipset drivers?
Click to expand...

I'm sure there are new firmware drivers for my SSD however it is my primary OS drive. Don't I need to run like Linux in Virtual memory to then update the firmware?
Mobo is ASUS P6T Deluxe V2... there have been no new drivers for a while.
 
SSD should always be at latest firmware. If that means having to back up your data and run an image or clean install, you definitely should. *F4 bug checks when an SSD is present in the system are usually always caused by the firmware needing to be updated.

Regards,

Patrick
 
OK cheers for that. Will look at getting that sorted.

BTW, there were no more BSOD's after running driver verifier after I had removed my Razer mouse and drivers. :-(
Now using generic mouse, this sucks.
 
How long ago did you remove the drivers + mouse? If it has been a few days, it was likely a combination of the two (more than likely the drivers as opposed to the mouse itself). Razer drivers have always been crap, but not too long ago they started shoving their drivers and updates through a software called Synapse which should win an award for being the most troublesome software out there.

Regards,

Patrick
 
I ran the verifier yesterday. It picked up that the file "Lachesis.sys" was the cause.
Removed drivers, software & mouse.
Ran verifier again.... no more BSOD's.

Is it possible to have the Lachesis mouse work without the Razer drivers?
 
Yes, definitely. I use mine without the drivers. Just plug it in and it'll use the generic Windows drivers. Don't install Razer's drivers from Windows Update or the Razer website.

Regards,

Patrick
 
Have OC'd the CPU to 3.8GHz now as well. It seems good at the moment.
Click to expand...

I would not do this, especially directly after dealing with BSOD issues. Drop the system to stock settings and let it go for a week or so. If you don't crash, you know the Razer drivers were likely the cause of the crashes, and then you can consider it solved and go about overclocking or whatever you desire. If you overclock now, if it's unstable, you will BSOD and come back here and we'll be running in circles.

Regards,

Patrick
 
Last edited:
Hi,

Nothing new, *124 BSOD with an internal CPU timer error on Processor 0 and Cache Bank 5. Is the system overclocked, or did you follow my advice of keeping it stock? I cannot check speeds:

Code: 
5: kd> !sysinfo cpuspeed
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

Regards,

Patrick
 

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

Back
Top