Hey!
My previous attempts to right this failed miserably after a second crash within 45 minutes… I’ve been having an issue with Random Crashes, the last one (Just occurred a dew minutes ago) I caught. The first one of the day, my Dad caught.
Originally, my Dad speculated the Thermals of my CPU and GPU. (I have really crappy airflow). However, while running slightly hot, it’s not nearing a dangerous temperature that would initiate a crash like that.
WhoCrash has kindly given me 2 reports…
See the quotes below.
[b]On Sat 2015-04-11 12:01:32 PM GMT your computer crashed[/b] crash dump file: C:\WINDOWS\Minidump\041115-30078-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0) Bugcheck code: 0x1A (0x5300, 0xFFFFC0002A80C000, 0x1D800010000, 0xCE57734CC6240635) 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.
[b]On Sat 2015-04-11 11:37:59 AM GMT your computer crashed[/b] crash dump file: C:\WINDOWS\Minidump\041115-55890-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0) Bugcheck code: 0x50 (0xFFFFF680010C6500, 0x0, 0xFFFFF80196AFE67D, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Now, I also took a look into my Event Logs, which has referenced a few (About 5 reported) Bad Blocks within the HDD. I can guess they are Soft Bad blocks, as they shouldn’t be physically damaged.
I ALSO took a look into a few other programs, which haven’t reported anything abnormal. I don’t overclock (I can’t, actually.)
Unless some low level Windows drivers are conflicting, nothing should be triggering this as I maintain no Anti-Virus or Firewall. I keep MCShield, MBAM and Zemana around though.
I will attach logs, soon.
Thanks,
Michael