Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

[inevu]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

I appreciate the offer but I no longer need the BIOS. ASRock customer support was very cool to deal with and snail mailed me a replacement BIOS ROM. Took about a week or so to get it, but I couldn't wait so I bought an ASUS Z77 mobo locally and had the machine back up the same day. The ASRock Z68 board sold quickly on craigslist, and the new owner must be happy with it, as I haven't heard back from him.

Hey luggerz! I have a question... could you tell me exactly what you told customer support in order to get the replacement BIOS ROM? I have exactly your same problem but I dont know how to tell my story. You have no idea how grateful I would be if you could tell me! Thank you so much!

[luggerz]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

could you tell me exactly what you told customer support in order to get the replacement BIOS ROM?

I just emailed them my complete HW and OS setup, when I bought the board, what BIOS I was running before, what I was doing to brick the system and what all I tried to recover it. They wanted the serial number off the board and a purchase receipt, but other than that was pretty painless. hope this helps!

[trenzterra]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

Hi, I just updated my Z68 Extreme 4 to the BETA 2.23 BIOS but am reporting in with the same issue.

I didn't notice this problem until recently when I decided to use the iGPU by itself, since there is no Virtu on Windows 8.

I was previously using 2.20 BIOS. I have no issues when using my discrete HD5850 card. It seems to happen most oftenly halfway through a Flash video.

This is my bugcheck result:

************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 780, 0, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+1bc )

Followup: MachineOwner
---------

2: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000000780, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: firefox.exe

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff8022ae5719b to fffff8022acfe340

STACK_TEXT:
fffff880`29697c88 fffff802`2ae5719b : 00000000`00000133 00000000`00000001 00000000`00000780 00000000`00000000 : nt!KeBugCheckEx
fffff880`29697c90 fffff802`2ad29011 : 00000000`00000002 fffff880`0145e180 fffff880`29697e40 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13ca8
fffff880`29697d10 fffff802`2ad29e97 : ffffffff`ffd0d9a0 fffffa80`06c0020c fffff880`29697e40 fffffff6`00000002 : nt!KeUpdateRunTime+0x51
fffff880`29697d40 fffff802`2ac39eca : ffffffff`ffd0d9a0 fffffa80`06c0020c 00000000`ba572c49 00000000`00000000 : nt!KeUpdateTime+0x3f9
fffff880`29697f30 fffff802`2acf77ee : 0000000c`9c755048 00000000`46e7efe2 fffffa80`06c00210 00000000`000000e1 : hal!HalpTimerClockInterrupt+0x86
fffff880`29697f60 fffff802`2ad6b401 : 00000000`00000000 00000000`00000008 00000000`014c5000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x1ce
fffff880`296980f0 fffff802`2adb5573 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0xf6
fffff880`29698140 fffff802`2ad7054b : fffffa80`00000000 00000000`00000000 00000000`00000001 fffffa80`062db520 : nt!MiChangePageAttributeBatch+0xdf
fffff880`296981b0 fffff802`2ad46e97 : fffff8a0`00000002 0000007f`0000007f 00000000`00000000 00000000`0020f3c6 : nt!MiGetZeroedPages+0x2c7
fffff880`29698230 fffff802`2ad67c50 : 00000000`00000001 00000000`031d0000 fffff880`296986b1 00000000`00000000 : nt!MiResolveDemandZeroFault+0x967
fffff880`29698350 fffff802`2ad47d62 : fffff880`296985c8 00000000`031d0000 fffff680`00018e80 fffffa80`0b16cb68 : nt!MiResolveProtoPteFault+0x5b0
fffff880`296983f0 fffff802`2ad38a28 : fffffa80`0ab78b00 00000000`00000000 fffff880`296986b1 fffff880`29698590 : nt!MiDispatchFault+0x272
fffff880`29698530 fffff802`2ad5086a : 00000000`00000001 ffffffff`ffffffff ffff881c`7c344700 fffff880`296986b1 : nt!MmAccessFault+0x288
fffff880`29698670 fffff802`2ad5032e : 00000000`00000000 fffffa80`0ab78b00 fffffa80`0af02480 fffff802`2af0dc00 : nt!MiProbeLeafFrame+0x24a
fffff880`29698770 fffff880`03a863ec : 00000000`00000001 fffff880`29698800 00000000`00000000 00000000`031d0000 : nt!MmProbeAndLockPages+0x14e
fffff880`29698830 fffff880`03a6df0e : fffff8a0`0427c010 00000000`00000000 fffffa80`0af6b6b0 00000000`00000002 : dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+0x1bc
fffff880`296988e0 fffff880`03a4dc9d : 00000000`31a0c000 00000000`0000c000 fffff8a0`05713990 fffffa80`07011e10 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0xa9a
fffff880`29698e90 fffff880`03899b6f : fffff880`0146c001 fffff880`29698f70 fffff880`29699901 fffffa80`0b16c600 : dxgmms1!VidMmReferenceDmaBuffer+0x55
fffff880`29698ef0 fffff880`0389af5a : fffff8a0`0298c000 fffff880`29699b80 fffff8a0`027b7210 00000000`0095fdb0 : dxgkrnl!DXGCONTEXT::Render+0x20f
fffff880`296997f0 fffff802`2acfd353 : fffffa80`0ab78b00 fffffa80`0ab78b00 00000000`00a50000 fffff880`29699b00 : dxgkrnl!DxgkRender+0x26a
fffff880`29699b00 00000000`771cc90a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0095e048 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771cc90a


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+1bc
fffff880`03a863ec 90 nop

SYMBOL_STACK_INDEX: f

SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+1bc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 505ab2a9

BUCKET_ID_FUNC_OFFSET: 1bc

FAILURE_BUCKET_ID: 0x133_ISR_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockP ages

BUCKET_ID: 0x133_ISR_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockP ages

Followup: MachineOwner

On both occasions where it BSODs this is the error message I get. Other times, it just freezes up and I can do nothing, except to hold the power button down for 4s and restart. Pressing the reset button doesn't work in either case.

[TWAD]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

I have the same Mboard as you with BIOS 2.30 and I am getting the same BSOD. Did you find a fix?

Hi, I just updated my Z68 Extreme 4 to the BETA 2.23 BIOS but am reporting in with the same issue.

I didn't notice this problem until recently when I decided to use the iGPU by itself, since there is no Virtu on Windows 8.

I was previously using 2.20 BIOS. I have no issues when using my discrete HD5850 card. It seems to happen most oftenly halfway through a Flash video.

This is my bugcheck result:



On both occasions where it BSODs this is the error message I get. Other times, it just freezes up and I can do nothing, except to hold the power button down for 4s and restart. Pressing the reset button doesn't work in either case.

[trenzterra]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

I have the same Mboard as you with BIOS 2.30 and I am getting the same BSOD. Did you find a fix?

Nope I did not. The only solution so far is to set a fixed voltage which the 2.20A BIOS did by default.

[trenzterra]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

Just tested the new 2.21A BIOS which the same symptoms occured as well. Strange thing is that it is still reproducible even with a fixed voltage of 1.165V.

[trenzterra]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

I just did more testing and I think the fixed voltage setting is a little broken in the new BIOS. Sometimes when I set a fixed voltage, it runs at auto voltage instead (according to CPU-Z)...

[trenzterra]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

The weird bug I'm experiencing is as follows:

When I set to auto voltage and save and exit; then if I set the voltage to 1.165V and save and exit, the voltage 1.165V shows in BIOS but a check in CPU-Z still shows auto voltage being used. To solve the problem, I must set to another fixed voltage (e.g. 1.16V) before moving back to 1.165V.

Setting to auto voltage and then setting a fixed voltage other than 1.165V doesn't have this issue.

Not a big problem, but thought I might just highlight it.

Overall, I'm still disappointed that it's two years on without any meaningful fix from ASRock yet. And another thing that pisses me off is that Lucid Virtu doesn't seem inclined to support Windows 8 at all (which is the main reason why I need to use IGP in the first place, for QuickSync transcoding).

[vs17]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

I too recently started experiencing BSOD after beginning to use the IGPU to hook up to multiple monitors in addition to my graphics card, same as Trenzterra.

Im currently playing around with the LLC levels but am planning to try a fixed voltage of 1.19 soon if that does not help. I've also seen occasional recommendations of disabling Active State Power Management for your storage devices, and am exploring that option now.

Has anyone made any progress on the Idle BSODs? I've been reading this entire forum but have yet to find a consensus on the proper way to resolve it (1.19 fixed voltage from front page is best?)

[rene38]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

Hi Folks,

I have an Asrock Z68 extreme 4 mother board since August 2011, and since the very beginning, I experience the same BSOD problem you described. I tried many things without any success until these last days.

The problem was mainly blue screen with the same kind of message you mentioned:
“A problem has been detected and Windows has been shut down to prevent damage to your computer
…
If problems continue, disable or remove any newly installed hardware or software.
…
Technical information:
*** Stop: 0x00000101 (0x0000000000000019,0x0000000000000000,0xFFFFF8800 09B3180,0x0000000000000004)
“

Sometimes, the problem was also a frozen screen, requesting me to push on the reset button. I noticed that it might happen just after a mouse action. But it happened also just hearing music, especially Web music. The worst case was when updating my GPS, with systematic 2 or 3 crashes during the long download.

During these 2 past years, I always updated the Bios version every time there was a new one (I am currently using the Bios version P2.20 dated on 2012/06/29). I also noticed that the problem was more frequent with a warm ambient temperature (summer period), as it is the case now. I recently had many crashes because of this. I then was able to make many trials. They consisted in removing one by one my peripherals (USB or PCI), or inactivating one by one the internal ones.

I did not try anything about the CPU OC or Core voltage, confident that the error message was giving useful information (“…disable or remove any newly installed hardware or software”). I did not want to use any OC, thinking that it could be worse.

I finally found this:
When I disabled the mother board Broadcom LAN chipset by the Bios, and replaced it by an old “Fast Ethernet RTL8139/810x” IDE card that I have, the problem disappeared. It is confirmed after 2 days of continuous usage at a warm ambient temperature, while I previously had several crashes per day (2 or 3 these last days before the change).
Is there a problem about the Broadcom LAN chipset implemented on this Asrock mother board?
I don’t know. Anyway, I have fixed my problem, and I just wanted to share this result with the community.

“Warm” regards from France.
Rene

[gordoncanada]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

Thank you for your post. This confirms my own experience. I sent my first Extreme 4 back to the manufacturer because of blue screens. Using the second board, I got one or two blue screens, but the onboard LAN did not work. I replaced it with a PCI LAN card and the internet worked. I continued to get intermittent blue screens until I turned the onboard LAN off in the BIOS. I did not bother sending the board back; they told me it was checked at the factory and had been in perfect condition when it left the factory. I figured it was such an easy fix it wasn't worth taking the computer apart again and waiting for another RMA. It has been two years now and the computer has not given me another blue screen. Yes, I think it is safe to say that at least some Extreme 4's had a bug in the LAN chipset.
Glad you finally got your computer going again.
Thanks again, Gordon

[vs17]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

Thanks for your idea. I have tried everything mentioned in this thread so far as well as my own tweaking, but continued to have intermittent blue screens with the extreme 4 board. It was often reproducable by using the onboard HDMI output at the same time as my video card, but would occur at all sorts of random times. I have just gone into the bios and disabled the onboard LAN, which I wasn't using anyway. I'll report back in a month or when the next blue screen triggers. Here's hoping this works.

In the future, I will likely go back to an ASUS or Gigabyte board. I gave ASRock a chance with this latest board based off of some good reviews online, but have been disappointed with the various problems I've experienced and the support they have received.

[gordoncanada]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

I hope this finally licks the problem for you. I look forward to hearing about your success!
Good luck, Gord

[rene38]

Re: Asrock Z68 extreme 4 : BSOD A clock interrupt was not received ---

Hi everybody.

I posted my findings in July2013. This BIOS LAN disabling looked to improve the situation, but after one month of observation, I still had few blue screens, even if it was less than before.

I then decided to force the BIOS CPU voltage to 1.19v, as mentioned several times. It was mid of August 2013.
After a month, no more blue screen.

I then decided to restore the BIOS LAN enabling. We are end of December, and I had no blue screen at all since the CPU voltage change to 1.19v.
It means 4 months without any blue screen.
In my case, the CPU voltage change to 1.19v was the solution.

I don't understand why this is not a default BIOS setup, since this is the official Asrock solution.

Merry Christmas to everybody.
Rene