New
#1
Plagued by random BSoDs
For quite some time, I've been getting random BSoDs. However, I have never been able to find any pattern between them, except for the possiblilty of memory corruption going on somewhere. Already checked my RAM with memtest86+ v4.20 (which I didn't know was technically outdated) and handled the main offenders (GFX and chipset should be fully up to date, audio is on the OEM-provided version, which I know is most likely not the source of the crashes).
I've cleaned up my minidump dir a number of times, I usually get PAGE_FAULT_IN_NONPAGED_ERROR, SYSTEM_SERVICE_EXCEPTION, and the like. However, most recent from a Verifier check, SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION, searching the followup symbol name ( nt!MiCheckSpecialPoolSlop+9a ) got tons of results over to here; while the trace doesn't say much about the issue from what I can tell (everything is in the NT module), it does look like you guys know quite a bit more about the kernel architecture than I do (as well as how to use WinDbg - I'm personally a gdb guy, but that doesn't really help with this).
Due to the massive size of the current dump (1.68GB), I can't exactly provide it reasonably - 7z got it down to 115MB, but that is still quite big, and if it is more than the kernel in it, I'm not sure I can safely provide it. However, I can provide some of the stuff from WinDbg:
--SNIP--
I usually also have Saitek drivers and PPJoy also, but those both prevent Driver Verifier from working, and neither are the cause of the issues.
"EDIT": WinDbg's output, especially lmtsmn, threw this over the char limit - threw that into an attachment instead.
EDIT: Yes, I do have the MEMORY.DMP on file, and can issue WinDbg commands for it