Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

PC freeze/BSOD when switching scenes in games


  • Please log in to reply
3 replies to this topic

#1 Alwynig

Alwynig

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:41 AM

Posted 02 January 2017 - 10:13 AM

Hi, since some time I'm experiencing my PC freezing and eventually (after almost exactly 2 minutes) BSOD with message DPC_WATCHDOG_VIOLATION.

 

This exclusively happens when I'm playing video games where I load a savegame, switch scenes, open the map or do other heavy (video) memory-related things.

 

What I'm noticing is that when a scene switch happens so to say, it stutters for a short time and that stuttering can lead to a complete freeze, or it can stop and continue working fine. It simply means I need to be super careful when doing this and not do it too fast too frequent. But, of course, this is not supposed to be...

 

My initial thoughts were that it was with my graphical card, and considering I was looking into upgrading I bought a new one. Strangely enough the issue did not happen for about a week and then returned, albeit less frequently.

  • Windows 10 Pro 64 bit OEM (although I purchased it)
  • 3 months old hardware
  • 3 months old OS installation
     
  • All hardware has stock voltages/clocks, did not overclock anything at any time
  • CPU: Intel Core i7-6700K
  • RAM: 16 GB DDR3 Kingston HyperX Fury 2.666 MHz (2x8)
  • Mobo: Asus Z170 PRO GAMING
  • GFX: MSI GeForce GTX 1080 Gaming X 8G
  • PSU: EVGA SuperNova 1000 G2
  • Built it myself
  • Desktop tower

I ran memtest86+ 4.20 and it passed without errors.

I also ran FurMark for a while (30 mins) and it did not cause a crash (GPU load does not seem to be the cause)

 

Find attached SysnativeFileCollectionApp and perfmon output.

 

Thank you in advance :)

Attached Files


Edited by Alwynig, 02 January 2017 - 01:47 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:41 AM

Posted 03 January 2017 - 03:05 PM

Ahhhh - the first memory dump of the new year!

 

Unfortunately it appears that the system has pirated software.
Please get a legitimate copy installed and we'll be glad to help.

Here's suggestions on how to ensure that your version is legitimate:  http://windows.microsoft.com/en-us/windows/genuine

Please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

As a courtesy, I will offer an analysis of your issues using the reports you provided.
I will not answer any questions about the analysis until the system is made legitimate.
If you do make it legitimate, please submit a new set of reports for us to check.

Just FYI, sometimes the owner won't know about this.  So here's 2 scenarios that might ring a bell:
- if they had a "friend" help with the computer - and the "friend" installed a pirated copy.
- or they used a copy that they had from another OEM computer.  The OEM license is tied to the hardware that it came from - so you can't just use it on another system (that means that it's pirated).

And here's the analysis:

 

 

You should run Memtest for at least 3 passes

When running Furmark you should also monitor the temps and look for when they stabilize.  Also look for any other issues while testing (screen problems, artifacts, etc)?

 

Your UEFI/BIOS (version 2003) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

I don't know how many Windows Update hotfixes are installed.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Not many errors in the other reports.  Please run these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

 

The memory dumps all point at video errors.

1)  Download a fresh set of the latest video drivers, uninstall the current drivers, then install the freshly downloaded drivers.

2)  If that doesn't help, then start hardware diagnostics on the video card:  http://www.carrona.org/hwdiag.html
Start with the video tests, but complete all of them - just in case.

3)  If the problems continue, you can try this procedure to rule out different hardware components:  http://www.carrona.org/strpdown.html

 

You may also want to run Driver Verifier according to these instructions (please remember that I will not respond unless the system is made legitimate):  http://www.carrona.org/verifier.html

 

Please uninstall the MSI OC (Overclock) Kit as it contains a driver that is known to cause BSOD's on some Windows systems ( NTIOLib_X64.sys )

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Jan  2 09:38:49.020 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\010217-7968-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 18:11:12.437
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :nvlddmkm.sys ( nvlddmkm+f368d )
BugCheck 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 30 20:06:21.586 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\123116-5609-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:1 days 9:05:00.406
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 28 15:36:12.169 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\122816-5421-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 6:19:45.562
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :nvlddmkm.sys ( nvlddmkm+f368d )
BugCheck 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 27 21:17:44.830 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\122816-5578-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 0:22:30.844
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :nvlddmkm.sys ( nvlddmkm+f368d )
BugCheck 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 27 20:36:29.282 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\122816-5906-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
System Uptime:0 days 0:58:30.047
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :nvlddmkm.sys ( nvlddmkm+fd311 )
BugCheck 133, {1, 1e00, 0, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  2003
  BIOS Release Date             09/19/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170 PRO GAMING
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Jan  2 09:38:49.020 2017 (UTC - 5:00)**************************
npf.sys                     Thu Feb 28 20:31:24 2013 (513004EC)
I2cHkBurn.sys               Mon Feb 17 20:34:54 2014 (5302B8BE)
iaStorAV.sys                Thu Feb 19 07:08:39 2015 (54E5D247)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
ndisrfl.sys                 Thu Jul  9 13:06:23 2015 (559EAA0F)
e1d65x64.sys                Thu Aug 13 05:14:29 2015 (55CC5FF5)
BazisVirtualCDBus.sys       Sat Sep 26 22:51:28 2015 (560759B0)
NTIOLib_X64.sys             Tue Apr 12 03:04:16 2016 (570C9DF0)
mbae64.sys                  Fri Apr 29 06:10:09 2016 (57233301)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
RTKVHD64.sys                Wed Aug  3 07:54:55 2016 (57A1DB8F)
aswRvrt.sys                 Thu Aug 18 10:12:01 2016 (57B5C231)
aswRdr2.sys                 Thu Aug 18 10:12:58 2016 (57B5C26A)
aswMonFlt.sys               Thu Aug 18 10:30:14 2016 (57B5C676)
aswNetSec.sys               Thu Aug 18 10:33:44 2016 (57B5C748)
aswStm.sys                  Thu Aug 18 10:36:29 2016 (57B5C7ED)
aswSnx.sys                  Mon Sep 12 08:37:08 2016 (57D6A174)
aswSP.sys                   Mon Sep 12 08:59:01 2016 (57D6A695)
TeeDriverW8x64.sys          Thu Sep 15 13:08:03 2016 (57DAD573)
mbam.sys                    Wed Sep 28 11:45:44 2016 (57EBE5A8)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
aswVmm.sys                  Thu Oct  6 05:26:20 2016 (57F618BC)
farflt.sys                  Wed Nov  2 10:29:12 2016 (5819F838)
MBAMSwissArmy.sys           Wed Nov  9 09:21:05 2016 (582330D1)
mwac.sys                    Thu Nov 17 20:02:05 2016 (582E530D)
MBAMChameleon.sys           Sat Nov 19 14:13:08 2016 (5830A444)
nvlddmkm.sys                Sun Dec 11 13:13:24 2016 (584D9744)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 30 20:06:21.586 2016 (UTC - 5:00)**************************
cpuz140_x64.sys             Wed Oct  5 05:53:07 2016 (57F4CD83)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 27 20:36:29.282 2016 (UTC - 5:00)**************************
TeeDriverW8x64.sys          Mon Mar 28 14:59:41 2016 (56F97F1D)
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
nvlddmkm.sys                Fri Sep 16 18:21:27 2016 (57DC7067)


http://www.carrona.org/drivers/driver.php?id=npf.sys
I2cHkBurn.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=iaStorAV.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=ndisrfl.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=BazisVirtualCDBus.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=mbae64.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
aswNetSec.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
farflt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=MBAMChameleon.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
cpuz140_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys



XXXXX
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Alwynig

Alwynig
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:41 AM

Posted 03 January 2017 - 05:13 PM

Hi, thank you for your extensive reply.

 

After the installation of Windows several actions were performed to reduce Microsoft's intrusiveness in my privacy (several "apps" removed and services disabled). That may have effected the genuineness, but I'll need to look into that.

For your information, in my country we can purchase OEM Windows licenses in many stores as normal consumers, for less than a retail license.

 

When running Furmark the temperature stabilized under the recommended maximum temperature (I will need to look up what it was exactly).

 

My previous card was not an MSI and I did not have their program installed, but even then the problem occured so I'm not sure of it's relevancy to my problem. I only installed it to control (disable) the LEDs on the card. But I will remove and it see if it helps.

 

I will also execute all the suggested steps and hopefully get back to you tomorrow, otherwise on Friday or Saturday (time constraint, unfortunately).

 

Hopefully a simple driver reinstall will fix my entire issue :). Would it help if I ran Guru3D's Display Driver Uninstaller?

 

Thanks!



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:41 AM

Posted 05 January 2017 - 09:27 AM

As you have asked for a response even though I said I won't respond - I am unsubscribing from this topic (so I won't be bothered by any further attempts to ask questions).

In case you do become legal after that, then you'll have to send me a Private Message to get me to look at your topic.
Should you use the Private Message to contact me again, without having become legal, I will report that to the Forum Staff - and I will block you from contacting me.

XXXXX


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users