Question BSOD Issues... Commonly IRQL No Less Or Equal ntoskrnl....

[Ralston18]

Follow-up for the record:

I was able to use

Clear-EventLog -logname OneApp_IGCC to clear the OneApp_IGCC log.

Entries went to 0 (zero).

Worked for other logs as well. No adverse effects noted.

Also, in Event Viewer, Windows/Microsoft has set various size limits on the logs. If a log reaches its' size limit then older entries are overwritten. Log sizes are end user configurable but there are imposed limits regarding log sizes.

The current limit values are shown in Max(K).

Event Viewer related Powershell cmdlets are well documented and I found quite a number of tutorials and examples.

Bottom line being that end users can (to some extent) clear logs and/or limit log sizes.

Read first and work/experiment in a test enviornment - just in case.

 

[johnbl]

you have this installed
\system32\DRIVERS\anodlwfx.sys Fri Mar 6 02:10:08 2009

ANOD Network Security Filter Driver​

most likely this driver corrupted shared driver pool and gave the corruption back to windows to reuse. windows reused it and then later found it was corrupted (common driver bug)

I might start with just using microsoft autoruns64.exe and disable the software driver.
I would consider doing a clean install of windows since the window debugger did not like your copy of various windows files.
(just not sure if the debugger is working ok this morning with the microsoft symbol server, it did not like your crashdump)

note: driver is way too old and has known kernel memory corruption issues

 

[ubuysa]

I still think that it would be wise to test your RAM before looking elsewhere, that dump had all the hallmarks of bad RAM and nothing I've read since changes that opinion. Flaky RAM can cause all manner of curious problems.

If you have more than one stick of RAM then remove one stick and run on just one for a while - or until you get another BSOD. Then swap RAM sticks and run on just the other RAM stick for a while. This will clearly show whether one stick is flaky.

-or-

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.