Windows 10: BSODs started after installing ATI Drivers

  1.    31 Mar 2016 #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.
      My ComputerSystem Spec


  2. Posts : 1,643
    Microsoft Windows 10 Home
       31 Mar 2016 #2

    Hi @INORMOUS

    The dumps are not indicating to display (specially ATI) related issue. Those are mainly memory related issue.
    You are using single channel memory; whereas your motherboard supports dual channel.

    Try one thing. Use the RAM as dual channel. Either in first and third (both black) slots or in second and fourth (both blue) DIMM slots. Different Channel number, same DIMM number. As shown in the picture below.
    See how it goes. Let us know.
    _______________________________________________________
    Code:
    BugCheck 1A, {61941, 4000d5f, d, ffffd00022d38b00}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+105aa )
    
    Followup:     MachineOwner
    ---------
    Code:
    BugCheck 3B, {c0000005, fffff803947befec, ffffd0002ae33650, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!_C_specific_handler+1c )
    
    Followup:     MachineOwner
    ---------
    Code:
    BugCheck 1A, {61941, 1100f960, d, ffffd000524a7b00}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+105aa )
    
    Followup:     MachineOwner
    ---------
    Code:
      Device Locator                ChannelB-DIMM1
      Bank Locator                  BANK 3
      Speed                         1600MHz
      Manufacturer                  Kingston
    ----------------------------------------------------------
      Device Locator                ChannelB-DIMM0
      Bank Locator                  BANK 2
      Speed                         1600MHz
      Manufacturer                  Kingston
      My ComputerSystem Spec

  3.    31 Mar 2016 #3

    did it
    gonna wait 24 and see if im not getting any more BSODs
    ill be back with updates if i do.
      My ComputerSystem Spec


 

Related Threads
Much as I hoped the W10 upgrade experience would be a smooth one, in true Windows fashion it's been a disaster. I've experienced multiple BSODs since install day, each with a different bug check string and no clear source (to my...
Recently i installed Mac OS X skinpack from https://skinpacks.com/download/windows-7/mac-os-x-skin-pack/ this website. The work fine until restart my system. When i restart my system, the windows 10 become stretched. So i try to uninstall the...
Windows Update not installing drivers in Drivers and Hardware
So I just performed a clean install and after running windows update it failed to install some drivers. Not sure which drivers I need now since I thought windows is supposed to install the right ones on its own. 31005310103100731008
So I just upgraded from Windows 7 to Windows 10 on my Dell Inspiron N7110 and now I'm having issues with all of my drivers not being recognized. My screen resolution is stuck in 1280x720 and its only recognizing Microsoft Basic Display Adapter. I...
Installing AMD Drivers.... in Drivers and Hardware
edit: alwrite so Windows detected my GPU drivers properly, and the main reason I wanted to install AMD's drivers was for CCC so I can enable overscan. Did that by going to the the Apps folder, and the CCC2 folder, and the "core" folder inside to get...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:58.
Find Us