Windows 10: Video card issues (from code 43 to black screen) Solved

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 20,885
    windows 10 professional version 1607 build 14393.969 64 bit
       16 Dec 2017 #11

    Please post with one drive or drop box share links:
    Share OneDrive files and folders - Office Support
      My ComputerSystem Spec

  2.    16 Dec 2017 #12

    Hope this works :)

    Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

    If this does not work, let me know and I can try running the script again.
      My ComputerSystem Spec


  3. Posts : 20,885
    windows 10 professional version 1607 build 14393.969 64 bit
       16 Dec 2017 #13

    It displays: This type of file can harm your computer.
      My ComputerSystem Spec

  4.    17 Dec 2017 #14

    My mistake, I used the wrong file. I didn't realize it sent a zip file to my desktop. Just to be sure, i ran it again. Hopefully this works, thanks for your patience.

    Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
      My ComputerSystem Spec


  5. Posts : 20,885
    windows 10 professional version 1607 build 14393.969 64 bit
       17 Dec 2017 #15

    Outsider418 ,

    There were 5 BSOD mini dump files.
    Debugging displayed 1 misbehaving hardware driver in all mini dumps.
    The bugcheck was 116
    This bugcheck is Video TDR error.

    Open administrative command prompt and copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) chkdsk /scan
    4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    5) Free space on C: so that there is 27 GB free

    6) Make sure that there is no overclocking.

    Video TDR could be caused by:
    a) Misbehaving drivers
    b) Heat
    c) Power to the card
    d) Faulty PCI-e slot
    e) Defective GPU


    Troubleshooting steps:
    a) Try later and/or earlier drivers
    b) Measure the GPU's temperatures at idle and under load
    c) Ensure the GPU is free from dust build up and that the fan is working correctly
    d) Reseat the GPU and check all connections are securely made
    e) Check PSU voltages in BIOS
    f) Try a different card in the system


    7) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.
    The computer manufacturer's web site is preferred.
    Enter the computer's serial or product number and the operating system to view available drivers.
    If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
    Official Display Driver Uninstaller DDU Download
    Display Driver Uninstaller Download version 17.0.7.2
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA

    8) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    Speccy - System Information - Free Download
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer

    9) What are the BIOS 3.3, 5 and 12 voltage values?
    What are the CPU voltage and frequency?

    Code:
    NVIDIA GeForce GTX 760    PCI\VEN_10DE&DEV_1187&SUBSYS_37693842&REV_A1\4&229165D2&0&0018    43
    nvlddmkm

    Code:
    12/16/2017 4:47 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 116
    P2: ffff8a0e537e9010
    P3: fffff8007f607914
    P4: ffffffffc0000001
    P5: 5
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\121617-12718-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-15812-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER51B0.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_d29f845217d97a49a7e1b5f297b83aaf623d5a_00000000_cab_029051aa
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 5037a3c8-d7d5-46dc-afe8-0d240a61428e
    Report Status: 4
    Hashed bucket:12/16/2017 7:09 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 116
    P2: ffff8c07cc396010
    P3: fffff80186507914
    P4: ffffffffc0000001
    P5: 5
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\121617-13015-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-18437-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5B8F.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_a6f58675612cd787a9db37a2714bf0abd74e913_00000000_cab_02905b8d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 900d7cd8-3db4-4f2a-b392-45b799960dbe
    Report Status: 4
    Hashed bucket:12/16/2017 5:05 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 116
    P2: ffffd4059233b4a0
    P3: fffff80538737914
    P4: ffffffffc0000001
    P5: 5
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\121617-13093-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-15671-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5044.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_5581ae2b1585bfddae20a7f3c7bb5bef4c1160ae_00000000_cab_02905052
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 993e3378-ae01-43bc-9039-2b42114ad7b3
    Report Status: 4
    Hashed bucket:
    Code:
    12/16/2017 4:55 PM    Windows Error Reporting    Fault bucket 0x116_TdrBCR:5:C0000001_Tdr:9_IMAGE_nvlddmkm.sys_Kepler, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 2c71ad8e-a7c9-4331-ac37-53c14748f44d
    
    Problem signature:
    P1: 116
    P2: ffff8a0e537e9010
    P3: fffff8007f607914
    P4: ffffffffc0000001
    P5: 5
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\121617-12718-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-15812-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER51B0.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_d29f845217d97a49a7e1b5f297b83aaf623d5a_00000000_cab_0a00d66a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 5037a3c8-d7d5-46dc-afe8-0d240a61428e
    Report Status: 268435456
    Hashed bucket:12/16/2017 7:51 PM    Windows Error Reporting    Fault bucket 0x116_TdrBCR:5:C0000001_Tdr:9_IMAGE_nvlddmkm.sys_Kepler, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 61deb1f8-f021-497f-a84f-d1ccb302be01
    
    Problem signature:
    P1: 116
    P2: ffff8c07cc396010
    P3: fffff80186507914
    P4: ffffffffc0000001
    P5: 5
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\121617-13015-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-18437-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5B8F.tmp.WERInternalMetadata.xml
    \\?\C:\Windows\Temp\WERE188.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_a6f58675612cd787a9db37a2714bf0abd74e913_00000000_cab_09e0e37a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 900d7cd8-3db4-4f2a-b392-45b799960dbe
    Report Status: 268435456
    Hashed bucket:12/16/2017 7:51 PM    Windows Error Reporting    Fault bucket 0x116_TdrBCR:5:C0000001_Tdr:9_IMAGE_nvlddmkm.sys_Kepler, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: e122ab7a-72ca-4616-9623-256851ff75b6
    
    Problem signature:
    P1: 116
    P2: ffffd4059233b4a0
    P3: fffff80538737914
    P4: ffffffffc0000001
    P5: 5
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\121617-13093-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-15671-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5044.tmp.WERInternalMetadata.xml
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_5581ae2b1585bfddae20a7f3c7bb5bef4c1160ae_00000000_cab_09e0bf58
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 993e3378-ae01-43bc-9039-2b42114ad7b3
    Report Status: 268435456
    Hashed bucket:12/14/2017 11:39 PM    Windows Error Reporting    Fault bucket 0x193_DxgkrnlLiveDump:804_Status_0xC000009A_Driver_nvlddmkm_failed_DdiStartDevice_dxgkrnl!DxgCreateLiveDumpWithWdLogs, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 3f4ffe8f-ff7f-4858-a894-265edd7644cc
    
    Problem signature:
    P1: 193
    P2: 804
    P3: ffffffffc000009a
    P4: 108
    P5: fffff801abcb0100
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171214-1830.dmp
    \\?\C:\WINDOWS\TEMP\WER-269359-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2910.tmp.WERInternalMetadata.xml
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_1086db7bf931bed43e819a67e4fd15b75b09b1e_00000000_cab_0b782d84\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
    \\?\C:\Windows\Temp\WER2C9B.tmp.etl
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C9A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CBA.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_1086db7bf931bed43e819a67e4fd15b75b09b1e_00000000_cab_1afa7b8b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 81141ba7-36d8-45d3-bcfc-ef4e63fd55dc
    Report Status: 268435456
    Hashed bucket:12/14/2017 11:39 PM    Windows Error Reporting    Fault bucket 0x193_DxgkrnlLiveDump:804_Status_0xC000009A_Driver_nvlddmkm_failed_DdiStartDevice_dxgkrnl!DxgCreateLiveDumpWithWdLogs, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 3fff0bb0-abe8-4d3a-95c4-20c4c310457b
    
    Problem signature:
    P1: 193
    P2: 804
    P3: ffffffffc000009a
    P4: 108
    P5: fffff801acb90100
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171214-1827.dmp
    \\?\C:\WINDOWS\TEMP\WER-107390-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC704.tmp.WERInternalMetadata.xml
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_a15867dd1dbbeb338c4ca74081308eb1ea6dd985_00000000_cab_0eddc781\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
    \\?\C:\Windows\Temp\WERC772.tmp.etl
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC771.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC782.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_a15867dd1dbbeb338c4ca74081308eb1ea6dd985_00000000_cab_1afa228e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b47bc98b-4b9a-400d-b548-ad7bb456ba4a
    Report Status: 268435456
    Hashed bucket:12/15/2017 10:12 PM    Windows Error Reporting    Fault bucket 0x193_DxgkrnlLiveDump:804_Status_0xC000009A_Driver_nvlddmkm_failed_DdiStartDevice_dxgkrnl!DxgCreateLiveDumpWithWdLogs, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 7dddbef9-0333-454f-840d-e03828ec6097
    
    Problem signature:
    P1: 193
    P2: 804
    P3: ffffffffc000009a
    P4: 108
    P5: fffff80403500100
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1712.dmp
    \\?\C:\WINDOWS\TEMP\WER-61656-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC20.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC20.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC40.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_80d5c2fa13bea4bfccaeaed49acfee9412b85b_00000000_cab_0b19685a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: af67a273-0845-4ed6-bca6-0b5c556593e9
    Report Status: 268435456
    Hashed bucket:12/15/2017 10:15 PM    Windows Error Reporting    Fault bucket 0x193_DxgkrnlLiveDump:804_Status_0xC000009A_Driver_nvlddmkm_failed_DdiStartDevice_dxgkrnl!DxgCreateLiveDumpWithWdLogs, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 92624198-3dc7-462a-8795-6a64640d4dd1
    
    Problem signature:
    P1: 193
    P2: 804
    P3: ffffffffc000009a
    P4: 108
    P5: fffff8026e0f0100
    P6: 10_0_16299
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20171215-1714.dmp
    \\?\C:\WINDOWS\TEMP\WER-57234-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF397.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF397.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF3A8.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_cb5c61d0ca9018ff95fe24d13f5a442ec16534f3_00000000_cab_1e910615
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 942e35e2-fb14-4f30-9103-86c5dc4bad6c
    Report Status: 268435456
    Hashed bucket:
    Code:
    Name    NVIDIA GeForce GTX 760PNP Device ID    PCI\VEN_10DE&DEV_1187&SUBSYS_37693842&REV_A1\4&229165D2&0&0018Adapter Type    NVIDIA, NVIDIA compatibleAdapter Description    NVIDIA GeForce GTX 760Adapter RAM    0 bytesInstalled Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvldumdx.dllDriver Version    23.21.13.8859INF File    oem0.inf (Section022 section)Color Planes    Not AvailableColor Table Entries    Not AvailableResolution    Not AvailableBits/Pixel    Not AvailableMemory Address    0xD0000000-0xF7FFFFFFMemory Address    0xE8000000-0xF1FFFFFFMemory Address    0xF0000000-0xF1FFFFFFI/O Port    0x00003000-0x00003FFFIRQ Channel    IRQ 11Driver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_c68c1eb90f6d242e\nvlddmkm.sys (23.21.13.8859, 16.24 MB (17,025,992 bytes), 12/16/2017 3:33 PM)
    Code:
    nvlddmkm nvlddmkm.sys Thu Mar 16 17:38:26 2017 (58CB13E2)
    Code:
    Event[1144]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-12-16T11:47:10.225  Event ID: 1018  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Chimera  Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.
    Code:
    Event[1369]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-12-16T12:05:13.913  Event ID: 1018  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Chimera  Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.
    Code:
    Event[1515]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2017-12-16T14:09:34.785  Event ID: 1018  Task: N/A  Level: Information  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: Chimera  Description: The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.
      My ComputerSystem Spec

  6.    17 Dec 2017 #16

    I will get started on these steps, but I will let you know what I have already tried:

    a) Try later and/or earlier drivers
    c) Ensure the GPU is free from dust build up and that the fan is working correctly
    d) Reseat the GPU and check all connections are securely made

    and I did use Display Driver Uninstaller to remove the driver completely (eventually...lol). I still had four versions of the driver exe files on my machine (I never use the GeForce experience if i can help it). Only the latest drivers worked, the others made safe mode come up. I will let you know how it goes. Fingers crossed.
      My ComputerSystem Spec


  7. Posts : 20,885
    windows 10 professional version 1607 build 14393.969 64 bit
       17 Dec 2017 #17

    Please make sure that you check "clean install"
      My ComputerSystem Spec

  8.    17 Dec 2017 #18

    SFC /Scannow:

    "Windows Resource Protection did not find any integrity violations"
      My ComputerSystem Spec

  9.    17 Dec 2017 #19

    Just for information ....
    Clean Install choice only shows up if you choose Custom Install , which you should use, and uncheck the features you don't need.

    When using DDU it should only have been run IN Safe Mode ....

    Hope you get your issues fixed, zbook is doing a great job helping you.
      My ComputersSystem Spec

  10.    17 Dec 2017 #20

    Here is the full scan from all three commands:

    Microsoft Windows [Version 10.0.16299.125](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dsm /online /cleanup-image /restorehealth'dsm' is not recognized as an internal or external command,operable program or batch file.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.125[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 493056 file records processed.File verification completed. 9041 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 31719 reparse records processed. 607026 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 31719 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 56986 data files processed.CHKDSK is verifying Usn Journal... 35245888 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 124469247 KB total disk space. 98810692 KB in 215565 files. 168712 KB in 56987 indexes. 0 KB in bad sectors. 619195 KB in use by the system. 65536 KB occupied by the log file. 24870648 KB available on disk. 4096 bytes in each allocation unit. 31117311 total allocation units on disk. 6217662 allocation units available on disk.C:\WINDOWS\system32>
      My ComputerSystem Spec


 
Page 2 of 4 FirstFirst 1234 LastLast

Related Threads
ASUS Z97-A with i5-4460 @ 3.2ghz. Win10 (latest Insider build). AMD R7-200 video card. Unpredictably, my monitor goes black except for a brief message that there is no HDMI. Usually a cold boot is required to restart, then the system runs in a...
Video Card Issues S.O.S. in Graphic Cards
Hello all.... Hope someone can steer me in the right direction. I recently bought a new video card, EVGA Gtx 950 but when I tried installing it didn't work... I think the problem may with my Gigabyte GA-P55-USB3 MB which doesn't have UEFI support. ...
Solved new video card blank screen in Graphic Cards
So, my old 670 burnt out in a weird way where it would do basic video but only if nvidia drivers werent installed, if they were installed then the system with that card was a brick. Was using a 550 while waiting on shipping, works fine but obviously...
Hey guys, I've tried downloading and installing Windows 10 via the System Update for the past 24 hours (I've tried it 5 separate times). Every time it gets to 84% overall, and 36% configuring settings, then goes to a black screen with nothing on it...
Black screen - Error code C1900101 in Installation and Upgrade
Evening all, Ive googled helplessly trying to find a fix to this problem. I dont have a problem with space, uninstalled my antivirus, fixed files in registry with Ccleaner... Ive tried getting windows 10 for the 4th time now, all I get is a black...
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 09:03.
Find Us