BSOD at random times error 0x0000001e, 0x00000034, and 0x0000003b

Eithos · 27 Apr 2015

My computer has recently taken to blue screening seemingly at random. I recently had a virus that was cleaned up with Spyhunter 4. The system was fine for a few days then blue screened when I was away and restarted throwing the 3b error. Over the past few days the errors have become more and more common. I've checked the computer with whocrashed and got the following results:

On Mon 4/27/2015 7:52:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042715-23150-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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.

On Mon 4/27/2015 7:52:08 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x295B1)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. KMODE_EXCEPTION_NOT_HANDLED

On Mon 4/27/2015 3:25:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042615-22978-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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.

On Sun 4/26/2015 11:17:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042615-55957-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x0)
Bugcheck code: 0x34 (0x50853, 0xFFFFF880035462D8, 0xFFFFF88003545B30, 0xFFFFF80002EFE622)
Error: CACHE_MANAGER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a problem occurred in the file system's cache manager.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Fri 4/24/2015 8:00:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042415-22027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F0C622, 0xFFFFF8800C396B50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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

I ran a memory check on the system and it came up with no fatal errors and no failing hardware so I believe it's a driver error. I've included the zip file for my computer as instructed in the posting instructions. Any help with this issue is appreciated!

Edit: Uninstalled Catalyst Commmand Center and reinstalled hoping that would fix the driver errors. No such luck as new blue screen was thrown, new log uploaded with new information from whocrashed.

On Tue 4/28/2015 12:10:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042715-28938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0x4A (0x770CDF3A, 0x2, 0x0, 0xFFFFF8800672DB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 4/28/2015 12:10:48 AM 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: 0x4A (0x770CDF3A, 0x2, 0x0, 0xFFFFF8800672DB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Laith · 28 Apr 2015

Hello and Welcome to SevenForums

Run MemTest86+ for 8 passes. I know that you ran a memory test but MemTest86+ is the most accurate out there. RAM - Test with Memtest86+

Run Driver Verifier for 24 hours. Driver Verifier - Enable and Disable
Your computer may run slow but that's because Driver Verifier is running. If you crash when you start your computer after running Driver Verifier go into Safe Mode and disable it. Safe Mode

Eithos · 28 Apr 2015

Thanks, I'll run the mem test for 8 passes tonight while I sleep and turn on the drive verifier after that when I wake up.

Eithos · 28 Apr 2015

Ran Memtest86+ for 8 passes came up all clear. When I tried to start in verifier mode my computer crashed immediately without any blue screen or dump.

Laith · 29 Apr 2015

That's a auto-restart. It basically means that something is overheating in the computer. Run Speecy.
Speccy - Advanced System Information Tool

Eithos · 29 Apr 2015

I ran Snappy Driver Installer last night it found 3 missing drivers; 2 for my usb serial bus and 1 for my ethernet controller it also updated another 18 that were out of date. As of this post all my drivers and windows updates are completely up to date. I have a feeling the missing drivers were what was causing the automatic restart when in driver verification mode as my system is well cooled. I've included the speccy log as you asked.