BSOD when starting Chrome or Mozilla Thunderbird

thecrows · 25 Dec 2015

Hi.
I've had my Acer 8935 laptop from new (bought in Jan 2010).
It came with windows Vista and an upgrade to Windows 7 (2 CDs directly from ACER - one with windows, second with dedicated drivers for my Laptop)
I have been re-installing the system regurarly (usually every 12-18 months).
I have recently upgraded to Windows 10, but changed my mind after a couple of days (lots of drivers compatibility issues) so I went back to Windows 7.
Again, I have installed it from CDs supplied by Acer.

Now from time to time my laptop just freezes, screen goes black or blue, then it turns to the R - G- B screens and shuts itself down.
It happens usually when I try to open Google Chrome (or new tab in that browser) and when I open Mozilla thunderbird.
Issue does not always occur. I would say that it happens more often when the computer is cold, just woke up from sleep mode.
Please find a zip file attached, containing report generated by DM Log collector.
Please help...
Pav

**axe0** · 26 Dec 2015

There are a few very important files missing, run the dm log collector again and upload a new zip.

thecrows · 26 Dec 2015

I have just created another report, this time in safe mode.
Please find attached below.

**axe0** · 26 Dec 2015

Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from your manufacturer Acer. Be sure to ONLY install the drivers using custom/advanced options.
Attachment 378619

Code:

*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
0: kd> lmvm atikmpag
start    end        module name
9263b000 9265a000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Tue Jun 30 23:08:48 2009 (4A4A7EE0)
    CheckSum:         0001C3EE
    ImageSize:        0001F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm atipmdag
start    end        module name
92e04000 9332b000   atipmdag T (no symbols)           
    Loaded symbol image file: atipmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atipmdag.sys
    Image name: atipmdag.sys
    Timestamp:        Wed Jul 01 00:23:28 2009 (4A4A9060)
    CheckSum:         004D91FF
    ImageSize:        00527000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


1: kd> k
ChildEBP RetAddr  
8ccba520 92ef3e59 nt!KiTrap00+0x8b
WARNING: Stack unwind information not available. Following frames may be wrong.
8ccba590 8ccba618 atipmdag+0x2bbe59
8ccba598 92ef3305 0x8ccba618
8ccba600 92df7dc1 atipmdag+0x2bb305
8ccba628 92df4244 atipmdag+0x1bfdc1
8ccba640 92c3b68c atipmdag+0x1bc244
8ccba650 92c59402 atipmdag+0x368c
8ccba66c 92ec623d atipmdag+0x21402
8ccba6c0 92ed1bbe atipmdag+0x28e23d
8ccba6e0 92ee6ba1 atipmdag+0x299bbe
8ccba708 92ed5615 atipmdag+0x2aeba1
8ccba718 92ed091a atipmdag+0x29d615
8ccba73c 92ed0acf atipmdag+0x29891a
8ccba760 92eca434 atipmdag+0x298acf
8ccba780 92eef27a atipmdag+0x292434
8ccba7a4 92eef58d atipmdag+0x2b727a
8ccba7f0 92eed3bb atipmdag+0x2b758d
8ccba800 92ecdec0 atipmdag+0x2b53bb
8ccba81c 92ec4bbf atipmdag+0x295ec0
8ccba830 92ec4bfb atipmdag+0x28cbbf
8ccba84c 92ec117e atipmdag+0x28cbfb
8ccba8cc 92ec21d8 atipmdag+0x28917e
8ccba8fc 92c68485 atipmdag+0x28a1d8
8ccba920 92c68ed6 atipmdag+0x30485
8ccba95c 92c68fce atipmdag+0x30ed6
8ccba97c 92c46161 atipmdag+0x30fce
8ccba99c 92c4a35f atipmdag+0xe161
8ccba9ac 92c47207 atipmdag+0x1235f
8ccba9c4 9282b232 atipmdag+0xf207
8ccba9d8 940bee3d atikmpag+0x4232
8ccba9fc 940bed7e dxgkrnl!DXGADAPTER::DdiResetFromTimeout+0x42
8ccbaa24 940bea33 dxgkrnl!DXGADAPTER::PrepareToReset+0xdb
8ccbaa40 940fb92c dxgkrnl!TdrIsRecoveryRequired+0x14e
8ccbaab8 94122d55 dxgmms1!VidSchiReportHwHang+0x3c0
8ccbaae4 94125f58 dxgmms1!VidSchWaitForCompletionEvent+0x16f
8ccbab64 9412665b dxgmms1!VidSchiWaitForCompletePreemption+0x54
8ccbabdc 94126fd1 dxgmms1!VidSchiSendToExecutionQueueWithWait+0x10f
8ccbad18 94127279 dxgmms1!VidSchiSubmitRenderCommand+0x809
8ccbad28 94127516 dxgmms1!VidSchiSubmitQueueCommand+0x61
8ccbad3c 941275bd dxgmms1!VidSchiRun_PriorityTable+0x24
8ccbad50 8301a221 dxgmms1!VidSchiWorkerThread+0x7f
8ccbad90 82ebf439 nt!PspSystemThreadStartup+0x9e
00000000 00000000 nt!KiThreadStartup+0x19

thecrows · 26 Dec 2015

Thanks for your prompt response and a word of advice.
However, after removing all AMD drivers and reinstalling them from ACER CD, same issues still occur.
Please find recent reports attached below.

**axe0** · 26 Dec 2015

If there are BIOS updates present on the site of Acer, update the BIOS.

Code:

BIOS Version:              Phoenix Technologies LTD V1.3206, 14/08/2009

thecrows · 26 Dec 2015

I have just updated it to the latest available version from Acer website (2011/08/09).
My laptop froze again straight after that, in exactly the same manner.
please find report files attached.

thecrows · 01 Jan 2016

Hi,
I think I have found the root cause of the problem (however - still don't know how to fix it).
I found in BIOS a way to control the switchable graphics.
There are three options available:
- integrated - only integrated card is in use
- discrete - only high performance graphic card is in use
- switchable - where the operating system (or the user via the operating system) decides which card to use
My laptop works perfectly fine on integrated and on discrete, but as soon as I change BIOS settings back to switchable mode - I get BSOD when using Chrome, thunderbird etc..
Any thoughts on which BIOS/Card drivers I should use to eliminate the problem ?
As I already said in my thread:
Since I bought the laptop in 2010 I have been reisntalling Windows every 12-18 months from the CDs provided by ACER.
It's been working perfectly for years.

Since I have intalled Windows 10, then went back to windows 7 (using the same ACER cds) it started to play up.

Any ideas on what WINDOWS 10 could have done to my laptop that would cause such issues ?