BSODs Bad_pool_caller and Clock_watchdog_timeout Win7 64bit

JMH said:

You say

- System is 1 month old
- Install is 1 month old

I would suggest it might be quicker & neater to do a
Clean Install Windows 7

BTW
Please fill in your System Specs.
Attachment 190246

I agree with this. Backup any important user files first following the backup steps for user files in Backup User and System Files. In step 9. choose not to include a system image of drives (uncheck the box).

I edited my system details. I recently updated some drivers. If I continue to get the crashes then I will do as you say and re-install windows 7.

Thanks for your help.

Thank you for the System Specs.
It allows us to assist you in a more efficient way.

Please feel free to ask further questions.
Keep in touch re what happens there too.
Good luck & Happy New Year.

I'll let you know what happens for sure.

Fingers crossed for a satisfactory outcome.

Ok, I updated some of the drivers. I also switched about MSE for Panda Cloud antivirus. I just got a BSOD. The Clock timeout one. Should I try re-installing windows?

robertheadley said:

Ok, I updated some of the drivers. I also switched about MSE for Panda Cloud antivirus. I just got a BSOD. The Clock timeout one. Should I try re-installing windows?

hile I would not have switched from MSE to panda (especially cloud) a clock watchdog isnt usually caused by that

Are you by chance overclocking anything?

I am not, However I have read that it might be a problem with the power stepping on the motherboard and it not providing enough voltage. Again, this is just what I have read in my searches, it seems a lot of people with this motherboard are getting this same BSOD. I am not overclocking.

robertheadley said:

I am not, However I have read that it might be a problem with the power stepping on the motherboard and it not providing enough voltage. Again, this is just what I have read in my searches, it seems a lot of people with this motherboard are getting this same BSOD. I am not overclocking.

If it might be an issue specific to your mobo you should contact them for the most up to date information.

Might be a BIOS update, but I am unsure.