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

Artifacts and bluescreens, unless in safe mode


  • Please log in to reply
7 replies to this topic

#1 Gelletti

Gelletti

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:58 AM

Posted 06 December 2016 - 04:41 AM

Hi there,

 

I've been having a problem while playing one particular game (XCOM). At random points it starts giving red artifacts, and a few seconds later a complete freeze occurs, then black screen, restart and bluescreen. I had fixed this a while back by updating my drivers, cleaning any dust buildup, and putting the card in a different PCIe slot. This fixed it for a while, until I got stubborn again and tried to get XCOM working. Now regular windows will not boot up, giving a bluescreen, unless I go through safe mode, which works just fine.

 

I've attached the sysnativefilecollection as requested, however I could not get the perfmon/report for some reason, it said translated "the system cannot find the path specified". I think this is because I'm in safe mode.

 

I would think that the problem lies with a defective GPU, although I don't understand why safe mode would then work without issues, and why only that one program gave problems.

 

Any suggestions are much appreciated!

 

 

 

System specs:

 

Windows 7 x64 retail bought in 2010, reinstalled in 2012 or so

All hardware bought in 2010 except for an SSD and extra RAM bought in 2012 and 2013 respectively.

 

Processor:        i7 870 2.93 GHz LGA1156 socket

Graphics card: Gigabyte GV N460OC (GTX 460)

Motherboard:    ASROCK P55 Extreme4

PSU:                 Cooler Master GX RS-750-ACAA-E3 (750 watt)

 

Desktop PC

Attached Files


Edited by Gelletti, 06 December 2016 - 04:43 AM.


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:58 AM

Posted 07 December 2016 - 07:44 AM

In most cases, a system that works in SafeMode (but not in normal mode) is experiencing a problem with a 3rd party program.

The easiest way to figure this out is by running a clean boot:  http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows

If that stops the problem, then re-enable things a few at a time until you figure out what's causing it.
Then uninstall the problem program (from Control Panel...Programs and Features).
 

While this is the best way (IMO), it may take a long time if you can't produce the problem on demand.

So, we'll also try the usual BSOD analysis/repairs if you'd like.

 

Here's the usual analysis for starters:

 

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  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.

 

Many Live Kernel Events in the WER section of the MSINFO32 report.

I'd suggest starting with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

 

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html
NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!

MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

Interestingly, I rarely see STOP 0x117 memory dumps.  Usually the only sign of them is a notification from the system tray that states that the driver has crashed and recovered.

But the rest of the dumps are STOP 0x116's  Please follow these troubleshooting suggestions:  http://www.carrona.org/VideoTDR.html

Also, please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:

To make it work you have to do BOTH of the below steps:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.


Please update these older drivers.  Links are provided in order to assist you with looking up the source of the drivers:

 

nusb3hub.sys                Thu Jan 21 22:22:18 2010 (4B5919EA)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions) Try OEM first - Drivers available at the following link require registration and a lot of research: http://www.renesas.com/supp/
http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys
 
nusb3xhc.sys                Thu Jan 21 22:22:21 2010 (4B5919ED)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions) Try OEM first - Drivers available at the following link require registration and a lot of research: http://www.renesas.com/supp/
http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys
 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Mon Dec  5 19:24:02.500 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120616-24437-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23569.amd64fre.win7sp1_ldr.161007-0600
System Uptime:0 days 0:00:31.546
*** 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+14d62c )
BugCheck 117, {fffffa80096cc180, fffff8800f18a62c, 0, 0}
BugCheck Info: VIDEO_TDR_TIMEOUT_DETECTED (117)
Arguments:
Arg1: fffffa80096cc180, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f18a62c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
BUGCHECK_STR:  0x117
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 21 09:08:07.703 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112116-24953-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23569.amd64fre.win7sp1_ldr.161007-0600
System Uptime:0 days 0:00:32.843
*** 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+14d62c )
BugCheck 116, {fffffa8009846010, fffff8800f15362c, 0, 2}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Arguments:
Arg1: fffffa8009846010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f15362c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
CPUID:        "Intel® Core™ i7 CPU         870  @ 2.93GHz"
MaxSpeed:     2930
CurrentSpeed: 2945
  BIOS Version                  P1.30
  BIOS Release Date             08/05/2010
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             P55 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 21 08:54:15.234 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\112116-22406-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23569.amd64fre.win7sp1_ldr.161007-0600
System Uptime:0 days 0:00:33.375
*** 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+14c1d0 )
BugCheck 116, {fffffa800995d010, fffff8800f1831d0, 0, 2}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Arguments:
Arg1: fffffa800995d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1831d0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
CPUID:        "Intel® Core™ i7 CPU         870  @ 2.93GHz"
MaxSpeed:     2930
CurrentSpeed: 2945
  BIOS Version                  P1.30
  BIOS Release Date             08/05/2010
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             P55 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



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 Dec  5 19:24:02.500 2016 (UTC - 5:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
ctxusbm.sys                 Mon Sep  7 14:09:28 2009 (4AA54C58)
nusb3hub.sys                Thu Jan 21 22:22:18 2010 (4B5919EA)
nusb3xhc.sys                Thu Jan 21 22:22:21 2010 (4B5919ED)
mvxxmm.sys                  Wed Mar 17 03:52:37 2010 (4BA08A45)
mv91xx.sys                  Wed Mar 17 03:53:06 2010 (4BA08A62)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
tscusb2m.sys                Fri Jun 18 13:42:21 2010 (4C1BAFFD)
tscusb2a.sys                Fri Jun 18 13:43:29 2010 (4C1BB041)
tascusb2.sys                Fri Jun 18 13:44:51 2010 (4C1BB093)
NIWinCDEmu.sys              Tue Aug  9 04:25:29 2011 (4E40EEF9)
dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)
Rt64win7.sys                Tue Feb 18 06:38:35 2014 (5303463B)
MpFilter.sys                Mon Aug  8 19:01:17 2016 (57A90F3D)
nvlddmkm.sys                Wed Nov 16 19:25:32 2016 (582CF8FC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 21 09:08:07.703 2016 (UTC - 5:00)**************************
lvrs64.sys                  Wed Jan 18 01:40:36 2012 (4F166964)
lvuvc64.sys                 Wed Jan 18 01:41:08 2012 (4F166984)
nvhda64v.sys                Thu Sep 29 09:25:06 2016 (57ED1632)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 21 08:54:15.234 2016 (UTC - 5:00)**************************
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
nvlddmkm.sys                Sun Jul 10 18:14:18 2016 (5782C8BA)


http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys
http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys
http://www.carrona.org/drivers/driver.php?id=mvxxmm.sys
http://www.carrona.org/drivers/driver.php?id=mv91xx.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
tscusb2m.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.
tscusb2a.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.
tascusb2.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=NIWinCDEmu.sys
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys


 
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 Gelletti

Gelletti
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:58 AM

Posted 08 December 2016 - 07:44 AM

Addition of Perfmon file since I've been able to get back into regular windows with the help of Usasma's cleanboot suggestion.

 

Will be working on the different diagnostic steps provided in above post.

 

Thanks for the help!

 

Also, I can't seem to find any trace of the alcohol% software on my computer, not in registry, not in other drives.

It seems I've deleted it one day, but not completely, can it still do harm in this case?

Duplexsecure did not seem to find SPTD.sys driver, so the uninstall button was greyed out.

Attached Files


Edited by Gelletti, 08 December 2016 - 07:48 AM.


#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:58 AM

Posted 10 December 2016 - 08:49 AM

The dtsoftbus01.sys driver is the DaemonTools/Alcohol % driver (DO NOT DELETE IT manually!)

If the driver is still on your system, then I'd suggest trying to reinstall the Alcohol % software, then immediately uninstall it.
That should remove the driver.  If it doesn't, it'll likely show up in the next memory dump.

If it does show up, I can suggest ways to remove it manually - but would prefer not to do it now as it's not a real "clean" solution.

 

Nothing real noteable in the Perfmon report.

 

Beyond that, we'll just wait and see if the BSOD's continue.
Good luck!

 


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.

#5 Gelletti

Gelletti
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:58 AM

Posted 27 December 2016 - 11:39 AM

Hello again!

 

I've since tried putting in different GPU's to see if that would resolve the issues. Right now I have an old 7300 LE card in there which seems to work fine.

However, I would of course like to see if I can go back to using my GTX 460, and see if it's actually the GPU that's been causing the problems.

 

I found this solution online: http://ccm.net/faq/6210-how-to-fix-an-nvlddmkm-sys-error-message

It wants me to create a new instance of the nvlddmkm.sys file, by copying it from my newest nvidia driver.

 

Since it won't allow me to copy files without some weird administrative clearance (error 0x80070522), I wanted to ask here first whether this is an idea worth pursuing.

Most files in my system32 are "last modified on" dates in 2009, so maybe "refreshing it" wouldn't be a bad idea.

 

Any advice? Some other people have said it could be a malfunctioning PSU. For a while my computer was connected to an ungrounded outlet, so maybe this has messed things up?

 

Thanks!


Edited by Gelletti, 27 December 2016 - 11:42 AM.


#6 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:58 AM

Posted 29 December 2016 - 09:07 AM

I'm of the opinion that if a card doesn't work right at default settings, then it's broken.  As such, I don't mess with replacing executables and stuff like that.  I'd post over in the Internal Hardware forums for suggestions/advice about that:    http://www.bleepingcomputer.com/forums/f/7/internal-hardware/ 

 

It seems to me that your 7300 LE card works without issues - so that should be sufficient evidence that the 460 is bad

If still uncertain, try a newer card.  If you don't have a newer one handy, you may want to purchase one from a shop that will let you return it if it's not needed (for your money back).


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.

#7 Gelletti

Gelletti
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:58 AM

Posted 05 January 2017 - 07:23 PM

Update:

 

Going on Usasma's advice, I put my card in my father's computer (incidentally he also owns a GTX 460). Immediately the same graphical glitches started occuring during boot and within Windows.

The card is broken and has to be replaced.

 

Thanks for all the help, learned some new things during the process of trying to figure this one out.



#8 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:58 AM

Posted 06 January 2017 - 06:51 AM

I'm glad to hear that you've isolated the problem.

Thanks for letting us know!


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