Multiple BSODs on computer after getting a new graphics card.

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 10
       #1

    Multiple BSODs on computer after getting a new graphics card.


    I recently had an extensive issue with graphics drivers and windows updater removing them and eventually i just decided to upgrade my graphics card, which fixed the issue i was having. Since then I have had multiple different BSODS in the past week that will happen every couple of hours, Memory management being the only reoccurring one but others have popped up. I am unsure if the new video card is related or not. I have attempted to update all of my drivers, run a memory diagnostic scan, a chkdsk scan, sfc scan, and scan for malware all with no results. I am unsure of the next steps to take to determine what is causing my system to have stop errors. I ran the log collector and attached it below, any help would be much appreciated.
    Attachment 220584
      My Computer


  2. Posts : 12,801
    Windows 11 Pro
       #2

    Hello Piehead and welcome to the forums. What card was your old card? Let me make a suggestion. Download the latest graphics driver for your card ( Latest NVIDIA GeForce Graphics Drivers for Windows 10 - Windows 10 Forums ) Also download Display Driver Uninstaller ( Display Driver Uninstaller (DDU) V17.0.9.1 Released. - Wagnardsoft Forum ) Run DDU in safe mode and remove all drivers and reboot into normal mode. Install the new drivers you just downloaded. When you install them select custom install. Make sure the 'Clean Install' box is checked. Then only install the Display Driver and PhysX, nothing else. See if that makes a difference.

    If your old card was an AMD card, you need to clean out all of the old AMD drivers before doing the above. AMD and Nvidia drivers typically don't get along very well.
      My Computer


  3. Posts : 8
    Windows 10
    Thread Starter
       #3

    My old card was an Nvidia GTX 960 not AMD. Also i did try to normally update my display drivers, but i will attempted to uninstall and clean install now as well as instructed. I will update again if I have another system crash.
      My Computer


  4. Posts : 12,801
    Windows 11 Pro
       #4

    OK, great! Sometimes that helps a lot. Start off clean. I don't work BSODs, so maybe someone else will come along to help there if this doesn't work for you.
      My Computer


  5. Posts : 8
    Windows 10
    Thread Starter
       #5

    BSOD persists


    Unfortunately after uninstalling and clean installing as you said I did have another BSOD hours later. I attached the new logs below Attachment 220633
      My Computer


  6. Posts : 12,801
    Windows 11 Pro
       #6

    Sorry, I hoped it would help. Maybe @Ztruker or @zbook can help.
      My Computer


  7. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #7

    The zip you attached the 2nd time is the same as the first zip you attached. Check again or re-run Beta log collector and generate a new zip file to upload.
      My Computers


  8. Posts : 8
    Windows 10
    Thread Starter
       #8

    New logs


    Oops sorry about that, here is the new file after that crash.Attachment 220652
      My Computer


  9. Posts : 41,452
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    1) There was one misbehaving hardware driver identified in the mini dump debugging: Nvidia GPU nvlddmkm.sys

    2) Turn off Windows updates of non-Microsoft drivers:
    Enable or Disable Driver Updates in Windows Update in Windows 10 | Tutorials

    All drivers should be installed from the computer or motherboard manufacturer's website.

    If a driver is needed that is not displayed then install from the component manufacturer's websites: Intel, AMD, Nvidia, Killer Networks, Realtek, etc.

    3) Uninstall any driver installed using Driver Easy

    4) If you are unable to identify the drivers then perform a system restore to a date before the software and drivers were installed

    5) sometimes a clean install is needed in case a system restore point is unavailable

    6) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

    7) re-install the Nvidia GPU driver from the Nvidia website

    8) make sure the driver is a different version from: 25.21.14.1735

    9) make sure that you check the clean install box and if available install the physx driver.

    Display Driver Uninstaller Download version 18.0.0.4 (or newer version if available)
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA
    Download Display Driver Uninstaller - MajorGeeks

    10) If the Nvidia GPU driver is involved in another BSOD then the hardware will need to be checked

    11) See if you can find a friend, neighbor, relative, or local computer store to swap the Nvidia GPU card.

    12) Perform two tests:
    a) test a new card in the problematic computer
    b) test the card from the problematic computer in another computer

    13) Turn off Windows fast startup:

    Turn On or Off Fast Startup in Windows 10 | Tutorials

    Code:
    4: kd> .time
    Debug session time: Fri Jan 11 13:49:50.801 2019 (UTC - 6:00)
    System Uptime: 0 days 0:35:41.495
    4: kd> .bugcheck
    Bugcheck code 1000007E
    Arguments ffffffff`c0000005 fffff802`d18a0bd1 ffff9688`f8922a28 ffff9688`f8922270

    Code:
    1/11/2019 7:55 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff802d18a0bd1
    P4: ffff9688f8922a28
    P5: ffff9688f8922270
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\011119-29171-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-277859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB17A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB19A.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB245.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB275.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_c049c549288956a7716ecab171cee3cc1d4f8fc_00000000_cab_035cb283
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b46e2a71-362f-4230-b9c0-a4c5392f9528
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    1/9/2019 8:00 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 61941
    P3: 7ffe03c0
    P4: d
    P5: fffff58a05fbfb00
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010919-29562-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-257125-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER466B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER468C.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4708.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4728.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_e63e7ef127c2cf97fe865c954aa9a767f4e278_00000000_cab_037c4737
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 66b61241-5a1d-4eaf-b59e-b71feb142561
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    1/9/2019 8:16 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: d1
    P2: ffffdf096efe5ad0
    P3: 2
    P4: 0
    P5: fffff804b4071058
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010919-31796-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-231859-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF212.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF222.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF27F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF290.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_9f2bbad5257e342adbab82e74e222a43e9f0edc1_00000000_cab_0367f28f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: feb715e6-050e-4b43-9fb9-b096f65b7b62
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    1/9/2019 8:49 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: ef
    P2: ffff9b87af1b1080
    P3: 0
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010919-30906-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-237859-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FD.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50E.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57B.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_ef_1aee65f99918448d7cde28315643065812bff_00000000_cab_0360057a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 13e1aec7-4805-467d-95ec-4543d95035f7
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    Code:
    1/9/2019 8:01 PM	Windows Error Reporting	Fault bucket 0x1a_61941_ANALYSIS_INCONCLUSIVE!unknown_function, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 5457cd1b-eaa7-46f7-8016-c61df9542176
    
    Problem signature:
    P1: 1a
    P2: 61941
    P3: 7ffe03c0
    P4: d
    P5: fffff58a05fbfb00
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010919-29562-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-257125-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER466B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER468C.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4708.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4728.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_e63e7ef127c2cf97fe865c954aa9a767f4e278_00000000_cab_2c5c8912
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 66b61241-5a1d-4eaf-b59e-b71feb142561
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    Code:
    1/9/2019 8:49 PM	Windows Error Reporting	Fault bucket ACCESS_VIOLATION_services.exe_BUGCHECK_CRITICAL_PROCESS_c0000005_nt!PspCatchCriticalBreak, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 3d9a4fcb-2394-4138-a55a-05bef5b8300a
    
    Problem signature:
    P1: ef
    P2: ffff9b87af1b1080
    P3: 0
    P4: 0
    P5: 0
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010919-30906-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-237859-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FD.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50E.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57B.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_ef_1aee65f99918448d7cde28315643065812bff_00000000_cab_2ef869e2
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 13e1aec7-4805-467d-95ec-4543d95035f7
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    1/11/2019 7:56 PM	Windows Error Reporting	Fault bucket AV_nvlddmkm!mapNext_IMPL, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 9caf3f81-7b4c-4dbb-8c53-e6b8d0ec5929
    
    Problem signature:
    P1: 1000007e
    P2: ffffffffc0000005
    P3: fffff802d18a0bd1
    P4: ffff9688f8922a28
    P5: ffff9688f8922270
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\011119-29171-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-277859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB17A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB19A.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB245.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB275.tmp.txt
    \\?\C:\Windows\Temp\WER1872.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_c049c549288956a7716ecab171cee3cc1d4f8fc_00000000_cab_16d51f18
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b46e2a71-362f-4230-b9c0-a4c5392f9528
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    1/9/2019 8:17 PM	Windows Error Reporting	Fault bucket AV_UsbHub3!HUBMISC_ControlTransfer, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 9499c6cf-0555-41c3-92df-ccd1c263c52c
    
    Problem signature:
    P1: d1
    P2: ffffdf096efe5ad0
    P3: 2
    P4: 0
    P5: fffff804b4071058
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010919-31796-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-231859-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF212.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF222.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF27F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF290.tmp.txt
    \\?\C:\Windows\Temp\WER33BF.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_9f2bbad5257e342adbab82e74e222a43e9f0edc1_00000000_cab_2e48972b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: feb715e6-050e-4b43-9fb9-b096f65b7b62
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    Code:
    Name	NVIDIA GeForce GTX 1060 6GB
    PNP Device ID	PCI\VEN_10DE&DEV_1C03&SUBSYS_62673842&REV_A1\4&3834D97&0&0008
    Adapter Type	GeForce GTX 1060 6GB, NVIDIA compatible
    Adapter Description	NVIDIA GeForce GTX 1060 6GB
    Adapter RAM	(1,048,576) bytes
    Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvldumdx.dll
    Driver Version	25.21.14.1735
    INF File	oem3.inf (Section108 section)
    Color Planes	Not Available
    Color Table Entries	4294967296
    Resolution	1920 x 1080 x 60 hertz
    Bits/Pixel	32
    Memory Address	0xF6000000-0xF6FFFFFF
    Memory Address	0xE0000000-0xEFFFFFFF
    Memory Address	0xF0000000-0xF1FFFFFF
    I/O Port	0x0000E000-0x0000E07F
    IRQ Channel	IRQ 16
    I/O Port	0x000003B0-0x000003BB
    I/O Port	0x000003C0-0x000003DF
    Memory Address	0xA0000-0xBFFFF
    Driver	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_e7b3660b4830c245\nvlddmkm.sys (25.21.14.1735, 19.48 MB (20,424,640 bytes), 1/11/2019 2:20 PM)
      My Computer


  10. Posts : 8
    Windows 10
    Thread Starter
       #10

    Thanks you so much for the continued aid. I have restored my system and once again uninstalled and reinstalled my graphics card. Hopefully no more BSODs but if they do happen I will update. Luckily this graphics card is new and if it is faulty I should be able to send it back.
      My Computer


 

  Related Discussions
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 11:16.
Find Us




Windows 10 Forums