BSOD PROBLEM, error code 0x00000109 (normal use/gaming)

philc43 said:

Here you go: https://downloadcenter.intel.com/

Thank you very much

philc43 said:

Here you go: https://downloadcenter.intel.com/

my pc just crashed again but with a new error code: CLOCK_WATCHDOG_TIMEOUT

The clock watchdog timeout can only be debugged with a kernel memory dump. The logs tell me that this file cannot be found:

C:\Windows\MEMORY.DMP was not found

You will need to change the settings to enable kernel dumps to be saved. Use the following tutorial and set it to Automatic memory dump: Configure Windows 10 to Create Minidump on BSOD and then you will need to wait for another crash to capture the dump file and share by uploading it to OneDrive and posting a link to it. (The file will be too large to upload here).

philc43 said:

The clock watchdog timeout can only be debugged with a kernel memory dump. The logs tell me that this file cannot be found:

C:\Windows\MEMORY.DMP was not found

You will need to change the settings to enable kernel dumps to be saved. Use the following tutorial and set it to Automatic memory dump: Configure Windows 10 to Create Minidump on BSOD and then you will need to wait for another crash to capture the dump file and share by uploading it to OneDrive and posting a link to it. (The file will be too large to upload here).

ok thank you

philc43 said:

The clock watchdog timeout can only be debugged with a kernel memory dump. The logs tell me that this file cannot be found:

C:\Windows\MEMORY.DMP was not found

You will need to change the settings to enable kernel dumps to be saved. Use the following tutorial and set it to Automatic memory dump: Configure Windows 10 to Create Minidump on BSOD and then you will need to wait for another crash to capture the dump file and share by uploading it to OneDrive and posting a link to it. (The file will be too large to upload here).

my pc crashed again

ERROR CODE : CRITICAL STRUCTURE CORRUPTION

This is the MEMORY.DMP file link:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

This is back to the previous type of BSOD so we will need to wait to see if you get the Clock Watchdog error again.

Did you have any luck trying to find a new iastora.sys driver? It looks the same one to me according to the logs.

philc43 said:

This is back to the previous type of BSOD so we will need to wait to see if you get the Clock Watchdog error again.

Did you have any luck trying to find a new iastora.sys driver? It looks the same one to me according to the logs.

I have just reinstalled windows10 and the iastora.sys driver has been deleted I don't know how, and the PC crashed again.

I forgot to tell you that when i upgraded from win7 to win10 the cpu usage was always 100% i don't know why

philc43 said:

This is back to the previous type of BSOD so we will need to wait to see if you get the Clock Watchdog error again.

Did you have any luck trying to find a new iastora.sys driver? It looks the same one to me according to the logs.

is it normal???

If you mean is the CPU at 100% normal, the answer is no. It will often be at 100% for short periods while certain processes are running but it should return to abour 3% during idle periods.

In Task Manager if you click on the CPU header in the table it will sort the processes according to CPU usage. You can then see what is using the CPU.

philc43 said:

If you mean is the CPU at 100% normal, the answer is no. It will often be at 100% for short periods while certain processes are running but it should return to abour 3% during idle periods.

In Task Manager if you click on the CPU header in the table it will sort the processes according to CPU usage. You can then see what is using the CPU.

And should i run driver verifier again??