*** WARNING: Check Image - Checksum mismatch - Dump: 0x23298, File: 0x26bf9 - W:\Symbols\crashdmp.sys\F69BF9371e000\crashdmp.sys
Your issue sounds different from mine, because I can pretty much do everything, but when the PC feels like hitting me with a BSOD, it just does. I can install Windows, I can run programs, I can boot into BIOS and past BIOS, but it just sporadically hits me with a BSOD whenever it wants. I'd suggest opening a new thread so you can get specific assistance and suggestions? You'd need to provide more details as well.As an added bonus, i can't wake the system if it goes to sleep. The mouse and keyboard don't work unless I did a hard restart which yields more BSOD errors until windows starts. Cannot update windows. They won't install. When I type in the search bar, it randomly disappears after a couple seconds so I have to type very fast and click on a result before it drops out. I can't run installers for the keyboard or mouse drivers. When I open edge, I get random "page cannot be displayed" I refresh and it's fine. If I play a game, BSOD. Remember, I replaced EVERYTHING! I even tried another clean install of windows from my own usb and it wouldn't install. This was after a complete format and deleting the partitions. Looks like I'll be replacing everything again.
Thanks. Your issues were the only thing similar to mine that I have found. They started like yours and they persisted as I started replacing hardware. Now EVERYTHING is new and the same issues are even more abundant. I really have no idea what to do as I can't even diagnose anything without a freeze up and constant BSOD errors. This was a perfectly working machine until a few weeks ago. Now I have 2 rigs both with the same issues, the oldest rig less than 1 year old and the newest is brand new. I tried EVERY fix suggested. Nothing is working....Why does no one ever tell you when you run the Memory Diagnostics to pick the EXTENDED option? I was just running it on default settings before and it always passed, but now I found a discussion where it was specifically stated to press F1 once the diagnostics start and pick the Extended option, and if the test freezes on 21% for more than 2 hours, the memory is the issue. Lo and behold I ran this and it's been frozen on pass 1 of 2 at exactly 21% for like 5 hours now. Does this FINALLY determine the RAM is the issue? If so, I'm ordering a new set immediately and replacing it.
Your issue sounds different from mine, because I can pretty much do everything, but when the PC feels like hitting me with a BSOD, it just does. I can install Windows, I can run programs, I can boot into BIOS and past BIOS, but it just sporadically hits me with a BSOD whenever it wants. I'd suggest opening a new thread so you can get specific assistance and suggestions? You'd need to provide more details as well.
Total Commander? Uhhh I don't think so, it's been bluescreeening even before I manage to install TCMD. Unless my MB is literally saving every previous installation of Windows on its hardware and then pulling the software out of its ass, if that's even possible, and then it results in some incompatibilities with later reinstallations, TCMD itself can't be the culprit. That would've been just 1 random instance of it.i looked at memory.dmp from sept 17
any chance your copy of TOTALCMD64.EXE is leaking non paged pool?
(i would remove the tool or do a find string on klog (I will look up the proper command))
I am not sure who owns this entry
KLOG 66 21483344 18 2731424 UNKNOWN pooltag 'KLOG', please update pooltag.txt
pooltag= KLOG
edit: https://mskb.pkisolutions.com/kb/298102#:~:text=More Information 1 Click Start, point to Search,,for example, C:\WINNT\system32\drivers, and then click Search Now.
22: kd> !poolused /t 10 4
........................
Sorting by Paged Pool Consumed
NonPaged Paged
Tag Allocs Used Allocs Used
MmSt 0 0 6573 28695328 Mm section object prototype ptes , Binary: nt!mm
MmRe 0 0 1853 18653920 ASLR relocation blocks , Binary: nt!mm
CM25 0 0 3092 14446592 Internal Configuration manager allocations , Binary: nt!cm
Ntff 20 7360 8503 11972224 FCB_DATA , Binary: ntfs.sys
FMfn 4 1216 22418 9598144 NAME_CACHE_NODE structure , Binary: fltmgr.sys
RX00 78 54464 15 6922656 ATI video driver
MINI 2330 13172512 1184 5913856 UNKNOWN pooltag 'MINI', please update pooltag.txt
Vi54 0 0 696 5701632 Video memory manager PTE array , Binary: dxgmms2.sys
RvaL 0 0 1692 5191664 UNKNOWN pooltag 'RvaL', please update pooltag.txt
MPsc 0 0 6264 4710528 UNKNOWN pooltag 'MPsc', please update pooltag.txt
Toke 0 0 2411 4320960 Token objects , Binary: nt!se
KLOG 66 21483344 18 2731424 UNKNOWN pooltag 'KLOG', please update pooltag.txt
NtfF 0 0 1664 2662400 FCB_INDEX , Binary: ntfs.sys
CM16 0 0 540 2641920 Internal Configuration manager allocations , Binary: nt!cm
hibr 1 64 1 2281472 UNKNOWN pooltag 'hibr', please update pooltag.txt
SW09 10 7456 2 2105344 Software Bus Enumerator
TOTAL 225349 433522848 244481 172889312
there was also a memory leak reported from rt640x64.sysTotal Commander? Uhhh I don't think so, it's been bluescreeening even before I manage to install TCMD. Unless my MB is literally saving every previous installation of Windows on its hardware and then pulling the software out of its ass, if that's even possible, and then it results in some incompatibilities with later reinstallations, TCMD itself can't be the culprit. That would've been just 1 random instance of it.
What else could those issues point to? I'm pretty convinced it's hardware at this point, but it could be remnants of software in some way that don't clear even when I fully reset everything? Like I said, my MB literally defaulted its RGB settings from way back when I first used RGB Fusion a year ago, even after clearing CMOS.