New
#1
BSODs started after installing ATI Drivers
Hey
Ive been experiencing BSODs for weeks now, here's some info.
1. it started when using windows 8.1 just after i installed new ATI drivers for my ATI x280
2. i uninstalled the ATI drivers and reverted to original windows drivers - didnt help, still BSODs
3. i removed my ATI card, got myself a new GTX 970 using Nvidia Drivers - didnt help
4. i upgraded to Windows 10 few days ago - didn't help
Apart from uploading the requested file ive been using WhoCrashed trying to figure out the culprit, it used to show the ATI sys file there, but now it shows various different ones.
here's some extra info from that software:
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 2016-03-31 5:11:48 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033116-19062-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61941, 0x4000D5F, 0xD, 0xFFFFD00022D38B00)
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.
On Thu 2016-03-31 5:11:48 PM 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 (0x61941, 0x4000D5F, 0xD, 0xFFFFD00022D38B00)
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.
On Thu 2016-03-31 12:49:55 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033116-20421-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803947BEFEC, 0xFFFFD0002AE33650, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
On Thu 2016-03-31 7:38:33 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033116-25812-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x61941, 0x1100F960, 0xD, 0xFFFFD000524A7B00)
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.
On Wed 2016-03-30 11:41:35 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033116-26125-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000!FxIoQueue::GetRequest+0x3A2EC)
Bugcheck code: 0x139 (0x3, 0xFFFFF80291C5F2B0, 0xFFFFF80291C5F208, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Wed 2016-03-30 9:09:18 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\033116-28156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0xFFFFF800CA1BB1DB, 0x2, 0x8, 0xFFFFF800CA1BB1DB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.