What's new Search

Recent content by Wildfire

W
[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL A few days later and still no crashes. Cautiously optimistic that it was either the overlock or SuperAntispyware causing the issues. I'll be putting back my slight overclock soon to see how things go then...
- Wildfire
- Post #12
- Feb 28, 2017
- Forum: BSOD Crashes, Kernel Debugging
W
[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL ElbyCDIO/AnyDVD - is from Redfox AnyDVD HD which I use to rip my DVD and Blu-rays so I can convert them for storage on my NAS. So they're necessary. I have uninstalled SuperAntispyware and as said, the slight overclock...
- Wildfire
- Post #11
- Feb 24, 2017
- Forum: BSOD Crashes, Kernel Debugging
W
[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL Actually, SuperAntispyware isn't from 2011. It's being actively maintained and the most recent release is just from a few weeks ago. And why should I remove Intel RST? I've still got two SATA HDD's and one AHCI SSD in my...
- Wildfire
- Post #9
- Feb 24, 2017
- Forum: BSOD Crashes, Kernel Debugging
W
[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL I've just switched back to non-overclocked settings. Turbo Boost multiplier settings are at automatic again, as is core voltage. Let's see how things go. :)
- Wildfire
- Post #7
- Feb 22, 2017
- Forum: BSOD Crashes, Kernel Debugging
W
[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL Thanks for your reply. Driver Verifier is enabled, I just verified it to be sure. So for some reason it wasn't triggered when the 2nd crash occured. I'm already on the latest Intel chipset drivers (v10.1.1.42). I'll...
- Wildfire
- Post #5
- Feb 22, 2017
- Forum: BSOD Crashes, Kernel Debugging
W
[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL And here's a Driver Verifier enabled minidump....
- Wildfire
- Post #3
- Feb 21, 2017
- Forum: BSOD Crashes, Kernel Debugging
W
[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Re: Windows 10 BSOD's -- CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL Also, per SFC /SCANNOW no errors in Windows system files. -- Edit: I have just noticed that enabling Driver Verifier results in Hitman Pro Alert being disabled. The HitmanPro.Alert Support Driver cannot be loaded and as a...
- Wildfire
- Post #2
- Feb 20, 2017
- Forum: BSOD Crashes, Kernel Debugging
W
[Win10] CLOCK_WATCHDOG_TIMEOUT / IRQL_NOT_LESS_OR_EQUAL

Lately, I've been getting regular BSOD's. I've seen CLOCK_WATCHDOG_TIMEOUT and IRQL_NOT_LESS_OR_EQUAL bluescreens. They seem to occur only when playing games and occasionally when exiting ZoomPlayer while it's playing a video. Heavy loads, like x264 encoding with VidCoder (Handbrake) can run...
- Wildfire
- Thread
- Feb 20, 2017
- Replies: 11
- Forum: BSOD Crashes, Kernel Debugging
W
[SOLVED] [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

The thread has already been marked as solved, but just to verify: it's now two weeks later and still no crashes. So it's absolutely 100% definitive that it was the MBAM webfilter driver. Couldn't have figured it out without this forum, so again -- many thanks!!! :rofl12::thumbsup2:
- Wildfire
- Post #15
- Feb 13, 2016
- Forum: BSOD Crashes, Kernel Debugging
W
[SOLVED] [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

Still no problems, so I'm now very confident it was indeed MBAM... a shame really, as an anti-malware program it was excellent. Perhaps I'll install it again and see if I can help the team at Malwarebytes at fixing the issue with their driver.
- Wildfire
- Post #14
- Jan 29, 2016
- Forum: BSOD Crashes, Kernel Debugging
W
[SOLVED] [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

Well, it's been a week now and still no crashes. I'll feel 100% sure when it's been a month without crashes, but for now I'd say I'm already 98% confident the problem was fixed by uninstalling MBAM. Thanks!
- Wildfire
- Post #12
- Jan 24, 2016
- Forum: BSOD Crashes, Kernel Debugging
W
[SOLVED] [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

Thanks! I'm almost positive MBAM is the cause, seeing that there are more people at this forum with MBAM and these crashes. :)
- Wildfire
- Post #10
- Jan 17, 2016
- Forum: BSOD Crashes, Kernel Debugging
W
[SOLVED] [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

Thanks for the input. As I needed my computer back to its normal performance level, I have disabled Verifier and uninstalled Malwarebytes for now. I'll try running my system like this for a week to see how it goes. I will, of course, let you know how things work out.
- Wildfire
- Post #8
- Jan 17, 2016
- Forum: BSOD Crashes, Kernel Debugging
W
[SOLVED] [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

Update: after 13.5 hours of Memtest86 (3 passes), no errors found. (your guide suggests running it for 7 to 10 passes, but unfortunately enough due to the time required for that I cannot do that -- it would mean not having access to my computer for nearly two full days)
- Wildfire
- Post #6
- Jan 17, 2016
- Forum: BSOD Crashes, Kernel Debugging
W
[SOLVED] [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

Of course, now that I *want* my system to crash, it doesn't... :) I'm sure it'll happen soon, so I'll check in here again when it does. :)
- Wildfire
- Post #4
- Jan 16, 2016
- Forum: BSOD Crashes, Kernel Debugging

Wildfire