A clock interrupt was not received on a secondary processor within the allocated time interval.

[AcidXenon]

Recently (last two weeks), finished my first ever PC build. Did the usual install Windows 7, every other program and games I wanted and everything was good. I had reinstalled Windows 7 over another version, causing it to create the "Windows.old" file in C: drive.

All has been fine up until the last couple of days, when I have received three BSOD errors all within the last two days. All three of them had the same error as in the title. The first one I ignored like it says to, then the second one happened today, and after restarting the PC it happened almost immediately again. After reading through various forums and digging up as much as I can, I went through to update all drivers on all software and devices found on my PC. All were up to date, and I am currently deleting the "Windows.old" folder located in C:.

All parts except the hard drive were purchased brand new from Amazon. Some users on other forums suspected that it was a faulty CPU, and whilst I hope this is not the case, I am still within Amazon's return period so it is an option if all else fails.

Parts used are as follows;
Intel i5 6600k
EVGA GTX 1070
ASUS Z170-A Motherboard
Corsair Vengeance 8GB DDR4 RAM

 

[johnbl]

most often I see this on windows 7 when a USB wireless driver is attempting to install over and over on one core while another core is waiting to use the device. The second core times out and calls the bugcheck.

you would have to provide a kernel memory dump to see if this is the case.

to fix it you would install the usb wireless driver and remove the default one that windows provides.

 

[AcidXenon]

most often I see this on windows 7 when a USB wireless driver is attempting to install over and over on one core while another core is waiting to use the device. The second core times out and calls the bugcheck.

you would have to provide a kernel memory dump to see if this is the case.

to fix it you would install the usb wireless driver and remove the default one that windows provides.

I am using a wireless headset, is that what you mean by USB wireless driver? Also, how do I upload the kernel dump here. Best to use something like mediafire, or is there a way to link it in the post directly.

 

[johnbl]

you would have to copy the memory dump to the server like mediafire, share the files and post the link.
for usb problems generally you would need a kernel memory dump rather than a mini memory dump.
kernel memory dump shows the state of all of the CPU cores and what was running at the time of the bugcheck.
a mini memory dump will only show the stack of the actual core that called the bugcheck.

generally for windows 7 this error is often caused by one particular USB wireless thumb ethernet network driver. (rather than a wireless bluetooth driver that most headsets would use)

most often I see this on windows 7 when a USB wireless driver is attempting to install over and over on one core while another core is waiting to use the device. The second core times out and calls the bugcheck.

you would have to provide a kernel memory dump to see if this is the case.

to fix it you would install the usb wireless driver and remove the default one that windows provides.

I am using a wireless headset, is that what you mean by USB wireless driver? Also, how do I upload the kernel dump here. Best to use something like mediafire, or is there a way to link it in the post directly.

 

[AcidXenon]

you would have to copy the memory dump to the server like mediafire, share the files and post the link.
for usb problems generally you would need a kernel memory dump rather than a mini memory dump.
kernel memory dump shows the state of all of the CPU cores and what was running at the time of the bugcheck.
a mini memory dump will only show the stack of the actual core that called the bugcheck.

generally for windows 7 this error is often caused by one particular USB wireless thumb ethernet network driver. (rather than a wireless bluetooth driver that most headsets would use)

most often I see this on windows 7 when a USB wireless driver is attempting to install over and over on one core while another core is waiting to use the device. The second core times out and calls the bugcheck.

you would have to provide a kernel memory dump to see if this is the case.

to fix it you would install the usb wireless driver and remove the default one that windows provides.

I am using a wireless headset, is that what you mean by USB wireless driver? Also, how do I upload the kernel dump here. Best to use something like mediafire, or is there a way to link it in the post directly.

Here is the kernel dump. https://www.mediafire.com/?q7dmgb0wcoqdo73
Thanks for the help so far.

 

[johnbl]

memory dump was too corrupted to be read by the debugger.

-you might want to update your sata drivers for your motherboard, maybe put your drive data cable on a different SATA controller or port.

-I would look to make sure you are not running something that modifies how files are stored.
(special disk software)

-you might want to run some utility to test your drive.

very hard to tell where the problem might be since the memory dump is corrupted I could not read anything from the dump except the system uptime which was 20 minutes.

you might google "how to force a memory dump using the keyboard"
you set a registry key, then use the keyboard to force a memory dump while the system is working. I might be able to read it and see if you have some issue before your system actually bugchecks.

 

[AcidXenon]

Most recent kernel dump. Think the last one was corrupted because I didn't let the memory dump finish before I started my PC. Here is new link

http://www.mediafire.com/file/q7dmgb0wcoqdo73/MEMORY.DMP

 

[AcidXenon]

memory dump was too corrupted to be read by the debugger.

-you might want to update your sata drivers for your motherboard, maybe put your drive data cable on a different SATA controller or port.

-I would look to make sure you are not running something that modifies how files are stored.
(special disk software)

-you might want to run some utility to test your drive.

very hard to tell where the problem might be since the memory dump is corrupted I could not read anything from the dump except the system uptime which was 20 minutes.

you might google "how to force a memory dump using the keyboard"
you set a registry key, then use the keyboard to force a memory dump while the system is working. I might be able to read it and see if you have some issue before your system actually bugchecks.

Been updating BIOS and performing CPU diagnostics. CPU passed fine, but have had another BSOD after updating BIOS. FIrst had a "SYSTEM_SERVICE_EXCEPTION" BSOD followed by the original one. Here is most recent kernel dump from BSOD- https://www.mediafire.com/?2x8530m68nmdh6n

 

[johnbl]

your system reports that you have only bank 0 with 4gb ram installed.
you should make sure this is correct. Sometimes you could have a second bank that is not seated correctly. if you only have one bank, you should consider adding a second, it would reduce a lot of the paging to the storage.
memory was CMK8GX4M2B3000C15 Corsair@ 2133MHz



- you might also remove
C:\Windows\system32\drivers\IOMap64.sys Wed Oct 22 17:52:12 2014
these tweak utilities often cause timing problems that can lead to timeouts.

debugger shows that pooltag ismc is using a large amount of nonpaged pool
this tag belongs to the intel storage driver.
I would update the driver from https://downloadcenter.intel.com/
or you motherboard vendor website.

you might also want to run crystaldiskinfo.exe on your storage drive and look at the smart data to see if the drive is having problems.

since the function that did not respond was in virtual memory, I would turn off the system virtual memory, reboot,unhide the c:\pagefile.sys and delete it. Then turn the virtual memory back on to create a new c:\pagefile.sys (make sure it is large enough) (this assumes you had a bad spot on your disk where your pagefile.sys was located and the storage driver did not handle the error correctly)

Guess you could also have malware in your storage driver, in which case you would want to start cmd.exe as an admin and run
sfc.exe /scannow
on windows 8.x and above you can also run
dism.exe /online /cleanup-image /restorehealth
but on windows 7 you would have to do the repair with a windows disk

---------
debugger also reports you have 12 modifications of your windows kernel
and 36 errors of your win32k kernel.
(happens on window 7 when something patches the kernel to modifiy functions)
on windows 10, it assumes these changes are virus attacks and just bugchecks the system.)

looks like the last function called was to delete a virtual address, it never completed and lead to the bugcheck, all the cpu cores were waiting for it to complete.


----------
you have a failed install of
"USB\ASMEDIAROOT_Hub\5&1b46e37c&0&0"
Asmedia USB 3.0 driver
\SystemRoot\system32\DRIVERS\asmtxhci.sys Fri Oct 7 00:25:29 2016

i would go to here: https://www.asus.com/us/Motherboards/Z170-A/HelpDesk_Download/
and make sure I installed the windows 7 64 bit USB drivers and chipset drivers. In any case, fix the install of the asmedia Usb hub driver or disable it in bios to prevent the bugcheck. (new driver should fix the problem (in theory))

machine info:
BIOS Version 2202
BIOS Release Date 09/19/2016
Manufacturer ASUSTeK COMPUTER INC.
Product Z170-A
Version Rev 1.xx
Processor Version Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 8300MHz
Current Speed 3500MHz

 

[AcidXenon]

Would performing a complete fresh install of Windows fix this? Or is it likely to happen again and just better off going through what you have recommended. Thank you for taking the time to do this.

 

[AcidXenon]

Also, i have 8gb ram across 2 slots as one stick was not fully seated.

 

[johnbl]

better to fix the problems as you would have to install the updates for the motherboard after the install anyway.
A clean install would only fix the problem with old drivers that were carried over from a old windows version.
Also, sometimes the motherboard vendors don't provide the updates you need and you have to go to the chip vendor to get the updated drivers. (intel in this case)

Would performing a complete fresh install of Windows fix this? Or is it likely to happen again and just better off going through what you have recommended. Thank you for taking the time to do this.

 

[AcidXenon]

better to fix the problems as you would have to install the updates for the motherboard after the install anyway.
A clean install would only fix the problem with old drivers that were carried over from a old windows version.
Also, sometimes the motherboard vendors don't provide the updates you need and you have to go to the chip vendor to get the updated drivers. (intel in this case)

Would performing a complete fresh install of Windows fix this? Or is it likely to happen again and just better off going through what you have recommended. Thank you for taking the time to do this.

Just finished going through all the fixes you suggested. I will let you know tomorrow what the situation is. Thanks again. <3

 

[AcidXenon]

better to fix the problems as you would have to install the updates for the motherboard after the install anyway.
A clean install would only fix the problem with old drivers that were carried over from a old windows version.
Also, sometimes the motherboard vendors don't provide the updates you need and you have to go to the chip vendor to get the updated drivers. (intel in this case)

Would performing a complete fresh install of Windows fix this? Or is it likely to happen again and just better off going through what you have recommended. Thank you for taking the time to do this.

It has already blue screened again. I am trying to install the ASmediaUSB3.0 drivers from the website, yet nothing seems to happen when I run them. It asks if I want to allow it to make changes, and if I trust it but nothing happens after that. All other drivers for chipset and USB installed fine. It might just be me being really stupid, I am getting to the edge with this PC at the moment. It seems to be running slow on certain games aswell now, but I would rather fix this issue first and get it over and done with.

 

[johnbl]

usb problems can make the whole system run slow. basically you can get into a loop where a driver tries to install over and over, or hundreds of thousands of USB errors are occuring but they are not enough to crash the system.

you can run usbview.exe and sometimes it will indicate of errors.
it comes with the windows DDK as sample source code but some people put it up on the web.
I get it from here:
http://www.uwe-sieber.de/usbtreeview_e.html

sounds like a bad driver build for ASmediaUSB3.0
if the driver fails to install, then you will get a bugcheck a few minutes later.
I would unplug everything from your asmedia usb 3.0 ports and try the install again. if that fails I would try a older build or see if the motheroboard vendor knows what the problem is. (usb 3 drivers will have to match your BIOS build and the revision of your motherboard. Certain UBS chips might also require firmware updates to work with new driver builds. this happens when vendors release their chips before the usb spec was finalized. Or when the BIOS gets a update to usb 3.1 specifications but the vendor does not update the drivers.

better to fix the problems as you would have to install the updates for the motherboard after the install anyway.
A clean install would only fix the problem with old drivers that were carried over from a old windows version.
Also, sometimes the motherboard vendors don't provide the updates you need and you have to go to the chip vendor to get the updated drivers. (intel in this case)

Would performing a complete fresh install of Windows fix this? Or is it likely to happen again and just better off going through what you have recommended. Thank you for taking the time to do this.

It has already blue screened again. I am trying to install the ASmediaUSB3.0 drivers from the website, yet nothing seems to happen when I run them. It asks if I want to allow it to make changes, and if I trust it but nothing happens after that. All other drivers for chipset and USB installed fine. It might just be me being really stupid, I am getting to the edge with this PC at the moment. It seems to be running slow on certain games aswell now, but I would rather fix this issue first and get it over and done with.

 

[AcidXenon]

I ran the USBTREEVIEW.exe and it showed no issues with any USB ports. It also showed I have nothing plugged into my ASMedia ports either. I downloaded the beta version of the ASMedia drivers and that installed fine. Is there anyway to test if this has fixed the problem, or do I just have to wait and see if the system BSOD's again?
Since I began going through all the actions you suggested, the BSOD's do seem to be less frequent.

 

[johnbl]

you have to wait, windows loads drivers in a different order on each boot. if you have a driver corrupting data in memory it will corrupt something different on each boot. if it corrupts something you are not actively using then the system will stay up for much longer. Generally, you will know in a week or two if the problem is fixed.
time, and reboots will tell.

I ran the USBTREEVIEW.exe and it showed no issues with any USB ports. It also showed I have nothing plugged into my ASMedia ports either. I downloaded the beta version of the ASMedia drivers and that installed fine. Is there anyway to test if this has fixed the problem, or do I just have to wait and see if the system BSOD's again?
Since I began going through all the actions you suggested, the BSOD's do seem to be less frequent.

 

[AcidXenon]

It has BSOD again. On the blue screen, does the "dumping memory" bit have to reach 100 to complete? It always seems to pause indefinitely at around 50. Would it be worth uploading another kernel dump for you to have a look at?

 

[AcidXenon]

I did use the program "Driver Booster" in order to gain all the necessary drivers when I first built my PC. I am going through it now and there seems to be a lot of duplicate drivers. Most often showing that they are not connected to the system aswell. qq

 

[AcidXenon]

Would you discourage me from totally wiping my hard drive and beginning completely from scratch on a fresh install of Windows 7? I have seen in other threads with the same issue that it is a suggested fix. I think if I were to do it, I would not use a third party program to install drivers, just take the time instead to do it all manually.

 

[johnbl]

the third party driver update programs are not a good idea any more.
it used to be that microsoft would charge vendors $20,000 dollars to test their drivers. They did not want to pay that so they just shipped them with their chips. Problem is that there are bugs in the logic of the chips and they modify the drivers to fix the problems. These driver installers just grab the current drivers from a lot of different vendors website but they don't track the chip versions so you never know if you have the correct version for your motherboard.

You may find it helpful to wipe and reinstall the OS and all of the motherboard drivers and see if that helps. you may just have a asmedia driver compiled for a different motherboard chip version. Generally, you could also disable plug and play, uninstall the driver using this method:https://technet.microsoft.com/en-us/library/cc730875(v=ws.11).aspx
then install the correct one for your motherboard. Then re enable plug and play.

otherwise, if you uninstall the driver, plug and play puts it back in a few seconds later.

Would you discourage me from totally wiping my hard drive and beginning completely from scratch on a fresh install of Windows 7? I have seen in other threads with the same issue that it is a suggested fix. I think if I were to do it, I would not use a third party program to install drivers, just take the time instead to do it all manually.

 

[AcidXenon]

Hi again. So, I did a complete fresh install of Windows 7 on a brand new SSD and HDD. All was fine for 2 day's, and yet again the PC has bluescreened with the same error. The dump physical memory to disc has been on 35 now for roughly 5 minutes. Do I need to let it reach 100 before restarting so as to not corrupt the dump file? Is there any simple fixes I can try here, or will I be better off getting someone else to look at it. Is it possible the mobo or some other component is faulty, and is there any easy way to test it??