Error code 0x1A in Windows 7 indicates a memory management issue.
Error code 0x1A in Windows 7 indicates a memory management issue.
Here's my system specs. Windows 7-64 BIT Intel i5 3550 @ 3.3 Ghz ( NO OC ) ASUS P8Z77-M Sapphire R9-Fury Nitro ( NO OC ) Corsair Vengeance 16GB @ 1333mhz ( NO OC ) W.D Blues 1TB X2 ( STEAM / Games / Other Programs and Software ) Transcend SSD370 128GB ( OS, Google Chrome etc nothing else ) So for some weird reason, today all sudden my PC started to BSOD and I can't even see the BSOD, my PC will just freeze black screen and restart itself, I only know it's BSOD because Windows informed me when the PC restarted. The only thing I did before this happen was Defragging my two Hard Drives, I have an SSD for OS Boot Up and I used Auslogics and I been using for Years and it was fine. Nope didn't had any update with it or anything either. ( And no of course I didn't defrag my SSD ) So when it first occurred was when I was watching a video on Facebook, all sudden BSOD. At first I thought could it be my GPU Driver causing it, so I've updated it to the latest AMD ReLive 17.3.1 and no go, was just playing Wticher 3 and it BSOD on me again. ( And as usual I did a clean uninstall and update, using DDU etc blah blah blah ) I check online alot suggesting could be a dying hard drive or something or maybe RAM faulty. So I used Crystal Mark Disk Info to check all my Drives are healthy. Same for my SSD. I even did the most basic by doing a System File Check via cmd. The only thing I didn't test was using MemTest86, not yet. What do you guys think it's causing the problem ?? Could it be a dying hardware ?? I do have plans on upgrading to RyZen but not so soon, and it's so sudden... Here's the crash report I obtained using WhoCrashed. On Thu 09-Mar-17 14:33:05 GMT your computer crashed crash dump file: C:\Windows\Minidump\030917-5350-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x74080) Bugcheck code: 0x1A (0x41284, 0x1155001, 0x0, 0xFFFFF70001080000) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 09-Mar-17 14:33:05 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x41284, 0x1155001, 0x0, 0xFFFFF70001080000) Error: MEMORY_MANAGEMENT Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
If this is a one time occurrence, I wouldn't really worry about it. If it becomes more frequent, then we have a problem. Like last night I had a 0x9F bugcheck. WhoCrashed says it was a driver problem. I'm not going to lose any sleep over it unless it happens again within a week or so. If you really want to be sure though, then running MemTest wouldn't be a bad idea.
Solving RAM issues makes sense only when all software is current—video, audio, and hardware drivers. Use glary utilities to verify drivers or inspect them directly.
I didn't even update Windows or add any new software. Just performed a hard drive defrag and experienced two consecutive BSODs on the same night. It's unusual since I haven't had any before, especially not after a recent fresh install. The timing is strange because it happened twice in one evening. Now I'm planning to run MemTest86 overnight to check for issues. (I hope it doesn’t come up.) What are the typical causes of such BSODs?
I've been thinking about this lately, especially since my OS and everything is on my SSD. If my HDD fails, will it still trigger a BSOD? Also, the first BSOD happened when I was on Facebook watching a video—my Google Chrome is actually installed on my SSD. Are there other ways to check my SSD for issues? For my HDD, I usually use W.D. Memory, but for the SSD I’m only using Crystal Mark Info, Auslogic, and HW64INFO, which both show 100% health.
If you've defragmented the HDD, you might want to run "chkdsk /f" in the command prompt to see if there are any HDD issues. Just to be clear, I'm not an expert, so let me know if I'm wrong. Your English is a bit tricky sometimes!
The only aspect I didn't verify was running MemTest86, not yet. ... Has it been completed?
It's not required for your HDD to impact the system unless you're retrieving information from it.
This strange BSOD is really puzzling. It seems the issue might be related to something unexpected. I haven’t noticed the screen flicker before; it just turns black and restarts on the first occurrence. I’m running a MemTest and so far everything looks fine. I’m planning to rest tonight and see what happens tomorrow. I think taking a break from work would be wise since my PC isn’t feeling well. Hopefully I’ll get some sleep tonight.