BSOD after solving a problem by overwriting with older system image

rundwald · 14 Jan 2014

Symptoms are that at start-up the system crashed. Turning the computer on by the on/off button, plug pulling or mains recycle had no effect. Strangley, what did work was to remove the power plug from the monitor and then reinsert it (the plug was secure before the removal and reinsertion.

SFDiagnostic file is attached, but if that is defective SF Debug files are available too.

Can you help, please?

Golden · 14 Jan 2014

That zip file is incomplete. Try this instead:

1. Download this .BAT file to your desktop
2. Right-click the .BAT file and 'Run as Administrator'
3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

Download

rundwald · 15 Jan 2014

I hope this one is OK. I made the files yesterday, as I was suspicious of SFDiag. As the minidump folder is empty.there's only this.

Had another BSOD thsi morning headed Memory Management. No dump was saved. I copied error info at bottom of BSOD in case it might be useful.

Golden · 15 Jan 2014

Follow this to ensure dmp files are created, then run the .bat tool (as administrator) again when you get a BSOD.

Dump Files - Configure Windows to Create on BSOD

rundwald · 15 Jan 2014

Yet another two BSODs tonight. The first just stayed blue with no text, and no dump created. Just before the second the monitor screen text sort of squeezed itself and produced patchy text and white background. About 4-5 days back hereI had swapped from DVI-D to VGA as some text was discolored,thinking the DVI cable might be faulty. On-screen output corruption

Mini dump is attached

rundwald · 16 Jan 2014

Another this morning (UK time)

Golden · 16 Jan 2014

OK. There are a couple of things going on.

Code:

fffff880`05f8bc38  fffff880`04affcf9Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x245cf9

Code:

Name	ATI Radeon HD 4350 (Microsoft Corporation WDDM 1.1)
PNP Device ID	PCI\VEN_1002&DEV_954F&SUBSYS_03541043&REV_00\4&25CE4FBF&0&0008
Adapter Type	Not Available, ATI Technologies Inc. compatible
Adapter Description	ATI Radeon HD 4350 (Microsoft Corporation WDDM 1.1)
Adapter RAM	1.00 GB (1,073,741,824 bytes)
Installed Drivers	atidxx32,atidxx64.dll,atiumdag,atiumdva,atiumd64.dll,atiumd6a.cap,atitmm64
Driver Version	8.56.1.16
INF File	atiilhag.inf (ati2mtag_R7X section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	1920 x 1080 x 59 hertz
Bits/Pixel	32
Memory Address	0xD0000000-0xDFFFFFFF
Memory Address	0xFE9F0000-0xFE9FFFFF
I/O Port	0x0000D000-0x0000DFFF
IRQ Channel	IRQ 4294967293
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	c:\windows\system32\drivers\atikmdag.sys (8.1.1.859, 4.79 MB (5,020,672 bytes), 13/07/2009 22:59)

Your video card driver is outdated. See if an updated driver is available using this tool:
AMD Driver Autodetect

Code:

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

Code:

fffff880`07282ea8  fffff880`024b12c6Unable to load image aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
 aswMonFlt+0x22c6

Unistall Avast and replace it with MSE.

rundwald · 16 Jan 2014

Thanks!:) I've installed the new driver, and will replace AVAST. But what is the problem with it, it having given me no trouble before? How well does MSE keep its definitions utd?

Golden · 16 Jan 2014

Avast is a well know cause of BSOD's on some systems, probably related to software updates.

MSE updates its definitions several times a day.

rundwald · 22 Jan 2014

Cause finally tracked to failing hard disk