• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Solved BSOD followed by display issues

Status
Not open for further replies.
Hi,

I have an Acer aspire V 15 laptop
V3-574-7321
Windows 10 64 bit

We use the program ‘driver easy’ and about 2-3 weeks ago and a few drivers were updated.

About a week or so later we got a BSOD, error “UCMUCSI Failure”. It did carry on working and then the same error came up 2 or 3 times. I tried running the DISM and SFC scans. It did say something was repaired but didn’t seem to make a difference and the BSOD came up again.

Then about a week later the screen went pink and Green, blurry and almost has an overlay behind what is currently on the screen, showing old things that were in the screen underneath. It almost sounds like the fan is kicking in and running harder now while it’s not doing anything.

I rolled back all the driver updates to when it was previously ok but that didn’t make a difference.

I then reset the computer and installed a fresh windows 10 64 bit but that didn’t work either.

If I plug in an external monitor, on the external monitor, the display is fine, so I think that’s telling me display driver, a display component, the screen itself or the display cable.

Like I said I have rolled back driver updates so I don’t think it’s that (although quite coincidental timing)I have stripped the pc down looking for anything obvious componente level or any loose connections especially on the display cable but I couldn’t see anything. I did unplug and reply display in and wobble the cable while plugged in and display on to see if it made the display worse or better but it didn’t make a difference.

What would be best to look at or try next? Any advice is appreciated.
 

Attachments

  • IMG_7427.jpeg
    IMG_7427.jpeg
    2.1 MB · Views: 0
  • IMG_7440.jpeg
    IMG_7440.jpeg
    1.3 MB · Views: 0
  • IMG_7454.jpeg
    IMG_7454.jpeg
    1.9 MB · Views: 0
  • IMG_7435.jpeg
    IMG_7435.jpeg
    2 MB · Views: 0
We use the program ‘driver easy’

What is commonly known as snake oil, they break your computer then try and sell you stuff to fix it.

Once Windows has been installed, you install the necessary drivers for the MB and other hardware and then leave well alone, drivers should not be allowed to auto update and you should never update any driver/s unless the new drivers are intended to resolve a specific issue that you are having, installing new drivers unnecessarily can actually cause you the very issues that any new drivers are intended to resolve and uninstalling the new drivers may not resolve the problem/s that installing the new drivers has caused.

Depending on priority it can take many months before the driver provider releases any fix and depending on the age of the hardware or software concerned they sometimes do not even bother or may have already announced an end of support.

I then reset the computer and installed a fresh windows 10 64 bit but that didn’t work either.

After installing Windows did you install the system drivers and starting with the chipset drivers first, this is paramount.

The screen issue is definitely hardware related, your own testing has already confirmed that so well done for that (y)

For the BSOD, see below;

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the Attach button, bottom left of the dialogue input box

We will move your thread to the more appropriate BSOD forum once we have any dmps to analyse.
 
  • Like
Reactions: xrobwx71
What is commonly known as snake oil, they break your computer then try and sell you stuff to fix it
Ok, I wont be using that again then.
After installing Windows did you install the system drivers and starting with the chipset drivers first, this is paramount.
Sorry, I know a little about PCs/Laptops but not that much. Basically I downloaded windows 10 64 bit from Microsoft on a USB drive, booted up the laptop into my USB and installed windows again. So no, I didn't install system drivers and chipset drivers, I didn't go that "far". I installed windows again and have left it.
The screen issue is definitely hardware related, your own testing has already confirmed that so well done for that (y)
I cant see damage to the display cable. I may see if a repair shop can run a test on the LCD panel to see if thats the issue to start off with.
For the BSOD, see below;

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the Attach button, bottom left of the dialogue input box

We will move your thread to the more appropriate BSOD forum once we have any dmps to analyse.
Thank you, I have attached the DMP files. Interestingly since I had the BSOD issues and then issues with the pink, green blurry display, I havent had a BSOD error come up again, yet.
 

Attachments

  • DMP FILES.zip
    293.5 KB · Views: 0
Please, no need for the bold text.

Both crash dmps identify the same culprit, the Qualcomm Atheros Wireless LAN device, if you have no further issues it would suggest that Windows has found and installed an appropriate driver for the device, Windows can`t do the same for newer chipsets as they come directly from the system manufacturer, see my canned info below;

Once Windows has been clean installed you must then install first the MBs chipset drivers then the storage/SATA drivers and third the graphics drivers, the drivers can either come from a disk provided by the motherboard manufacturer ** or downloaded from their site and saved to a flash drive etc, this is a must and Windows should not be allowed to check for updates before it has been done as more often than not Windows installs the wrong drivers or in the incorrect order and this can cause all sorts of problems.

The reason why this procedure is so important, the chipset is what enables the MB to be able to communicate with all the hardware + are the first drivers that Windows looks for on boot.

** For OEM computers/notebooks such as Acer, Dell, HP and Lenovo etc you must only download drivers from their support page, OEMs may sometimes redirect users to a third party site such as AMD or Nvidea to obtain the latest drivers for their GPUs, this tends to be for high end gaming notebooks and desktops though.
 
  • Like
Reactions: berger54
Status
Not open for further replies.