Recent content by cwsink

Excellent news! Thank you for the update. Is the old CPU a candidate for RMA with Intel?

Sounds good. Please let us know either way after what you'd consider sufficient time to know one way or the other. Good luck!

The crash happened on logical core 0 rather than 8, though, so.... yay?

Okay, let's see if that made a difference. Interestingly, the system uptime for the latest crash shows: so I'm guessing the computer was shutdown before the CPU was removed and then replaced such that the system state was saved to disk in a hibernate state rather than a full shutdown. So, it...

With as many BSODs as you've had it wouldn't surprise me if you had corrupted system files. Did you run SFC before the latest crash or after?

Thank you, @EggShell. Do you happen to know if waiting on a spin lock is considered "work" when it comes to event tracing data? The graphs suggest not but I haven't been able to find anything that says whether it does or not. I think part of the confusion when looking at DPC_WATCHDOG_VIOLATION...

I hope so, too. Thank you for keeping us updated.

@EggShell - Thank you for your thoughts. Your comment narrowed my focus. !running -t on the memory.dmp linked in this reply shows only core 8 as not running the core's idle thread at the time of the bugcheck. The only threads that show up when running the !ready extension shows: 8: kd> !ready...

Please do let us know how it goes. Good luck!

The latest dump file crashed on core 8 so it doesn't appear to have been disabled.

It looks like the driver gna.sys was updated but I don't see any other 3rd party driver loading that is newer than those in the earlier dump files. That doesn't seem to have made any difference, unfortunately. The bugcheck codes are all in the set of those which can happen with faulty memory...

No worries and will do.

Also, have you gone through the drivers on your motherboard product support page?

I wouldn't run it overnight. I was curious to see if the tool would run in safe mode and whether or not it would crash but there are quite a few differences between safe mode and normal mode. Power management is basically turned off in safe mode and that seems to be where issues can show up in...

Does msconfig show Normal startup selected in the General tab dialog? Have you manually disabled any services or is everything default? It's weird but I don't think it has anything to do with the original problem. My guess is there's some dependency for ctfmon.exe that isn't being satisfied in...