Author Topic: Getting BSOD, and told that Avast could be causing them.  (Read 10247 times)

0 Members and 1 Guest are viewing this topic.

jwoods301

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #15 on: December 31, 2013, 11:31:15 PM »
How? lol

When you start the program, it should show you a list of minidump files in the upper pane. Click on an individual minidump file, and the lower pane should show a list of processes.

It should look like this...

« Last Edit: December 31, 2013, 11:37:03 PM by jwoods301 »

orgonotic

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #16 on: December 31, 2013, 11:45:24 PM »
There must be a simpler way than doing screenshots?.. - it would take about 12 to show all that properly.

Crash List

Created by using BlueScreenView
Filename  Address In Stack  From Address  To Address  Size  Time Stamp  Time String  Product Name  File Description  File Version  Company  Full Path 
cdd.dll   fffff960`00620000 fffff960`00647000 0x00027000 0x00000000             
spldr.sys   fffff880`0163e000 fffff880`01646000 0x00008000 0x4a0858bb 11/05/2009 16:56:27           
intelppm.sys   fffff880`04c09000 fffff880`04c1f000 0x00016000 0x4a5bc0fd 13/07/2009 23:19:25           
msisadrv.sys   fffff880`00fbf000 fffff880`00fc9000 0x0000a000 0x4a5bc0fe 13/07/2009 23:19:26           
pcw.sys   fffff880`0161b000 fffff880`0162c000 0x00011000 0x4a5bc0ff 13/07/2009 23:19:27           
Null.SYS   fffff880`0446d000 fffff880`04476000 0x00009000 0x4a5bc109 13/07/2009 23:19:37           
Msfs.SYS   fffff880`047e4000 fffff880`047ef000 0x0000b000 0x4a5bc113 13/07/2009 23:19:47           
Npfs.SYS   fffff880`047ef000 fffff880`04800000 0x00011000 0x4a5bc114 13/07/2009 23:19:48           
kbdclass.sys   fffff880`04f3a000 fffff880`04f49000 0x0000f000 0x4a5bc116 13/07/2009 23:19:50           
mouclass.sys   fffff880`04fb2000 fffff880`04fc1000 0x0000f000 0x4a5bc116 13/07/2009 23:19:50           
WMILIB.SYS   fffff880`00fb6000 fffff880`00fbf000 0x00009000 0x4a5bc117 13/07/2009 23:19:51           
wd.sys   fffff880`01636000 fffff880`0163e000 0x00008000 0x4a5bc11b 13/07/2009 23:19:55           
CLFS.SYS   fffff880`00c9f000 fffff880`00cfd000 0x0005e000 0x4a5bc11d 13/07/2009 23:19:57           
disk.sys   fffff880`011e3000 fffff880`011f9000 0x00016000 0x4a5bc11d 13/07/2009 23:19:57           
i8042prt.sys   fffff880`04f1c000 fffff880`04f3a000 0x0001e000 0x4a5bc11d 13/07/2009 23:19:57           
nsiproxy.sys   fffff880`01be1000 fffff880`01bed000 0x0000c000 0x4a5bc15e 13/07/2009 23:21:02           
dump_dumpfve.sys   fffff880`02adc000 fffff880`02aef000 0x00013000 0x4a5bc18f 13/07/2009 23:21:51           
fastfat.SYS   fffff880`04a00000 fffff880`04a36000 0x00036000 0x4a5bc1f0 13/07/2009 23:23:28           
mup.sys   fffff880`01646000 fffff880`01658000 0x00012000 0x4a5bc201 13/07/2009 23:23:45           
BATTC.SYS   fffff880`01082000 fffff880`0108e000 0x0000c000 0x4a5bc3b5 13/07/2009 23:31:01           
compbatt.sys   fffff880`01079000 fffff880`01082000 0x00009000 0x4a5bc3b6 13/07/2009 23:31:02           
wmiacpi.sys   fffff880`04c00000 fffff880`04c09000 0x00009000 0x4a5bc3b6 13/07/2009 23:31:02           
CmBatt.sys   fffff880`04ff4000 fffff880`04ff8500 0x00004500 0x4a5bc3b7 13/07/2009 23:31:03           
mssmbios.sys   fffff880`01bed000 fffff880`01bf8000 0x0000b000 0x4a5bc3be 13/07/2009 23:31:10           
fileinfo.sys   fffff880`0150e000 fffff880`01522000 0x00014000 0x4a5bc481 13/07/2009 23:34:25           
blbdrive.sys   fffff880`04b0d000 fffff880`04b1e000 0x00011000 0x4a5bc4df 13/07/2009 23:35:59           
discache.sys   fffff880`01a00000 fffff880`01a0f000 0x0000f000 0x4a5bc52e 13/07/2009 23:37:18           
watchdog.sys   fffff880`047b9000 fffff880`047c9000 0x00010000 0x4a5bc53f 13/07/2009 23:37:35           
Dxapi.sys   fffff880`054ee000 fffff880`054fa000 0x0000c000 0x4a5bc574 13/07/2009 23:38:28           
vga.sys   fffff880`0447d000 fffff880`0448b000 0x0000e000 0x4a5bc587 13/07/2009 23:38:47           
VIDEOPRT.SYS   fffff880`0448b000 fffff880`044b0000 0x00025000 0x4a5bc58b 13/07/2009 23:38:51           
monitor.sys   fffff880`055c1000 fffff880`055cf000 0x0000e000 0x4a5bc58c 13/07/2009 23:38:52           
Beep.SYS   fffff880`04476000 fffff880`0447d000 0x00007000 0x4a5bca8d 14/07/2009 00:00:13           
swenum.sys   fffff880`04ff9000 fffff880`04ffa480 0x00001480 0x4a5bca92 14/07/2009 00:00:18           
ksthunk.sys   fffff880`05466000 fffff880`0546b200 0x00005200 0x4a5bca93 14/07/2009 00:00:19           
mouhid.sys   fffff880`055b4000 fffff880`055c1000 0x0000d000 0x4a5bca94 14/07/2009 00:00:20           
crashdmp.sys   fffff880`02ace000 fffff880`02adc000 0x0000e000 0x4a5bcabd 14/07/2009 00:01:01           
vdrvroot.sys   fffff880`00e00000 fffff880`00e0d000 0x0000d000 0x4a5bcadb 14/07/2009 00:01:31           
vwifibus.sys   fffff880`04e8a000 fffff880`04e97000 0x0000d000 0x4a5bcc39 14/07/2009 00:07:21           
vwififlt.sys   fffff880`03f8d000 fffff880`03fa3000 0x00016000 0x4a5bcc3a 14/07/2009 00:07:22           
netbios.sys   fffff880`03fbe000 fffff880`03fcd000 0x0000f000 0x4a5bccb6 14/07/2009 00:09:26           
wfplwf.sys   fffff880`03f5e000 fffff880`03f67000 0x00009000 0x4a5bccb6 14/07/2009 00:09:26           
ndistapi.sys   fffff880`0ffc1000 fffff880`0ffcd000 0x0000c000 0x4a5bccd8 14/07/2009 00:10:00           
raspppoe.sys   fffff880`0f200000 fffff880`0f21b000 0x0001b000 0x4a5bcce9 14/07/2009 00:10:17           
AgileVpn.sys   fffff880`04c2f000 fffff880`04c45000 0x00016000 0x4a5bccf0 14/07/2009 00:10:24           
rassstp.sys   fffff880`0f23c000 fffff880`0f256000 0x0001a000 0x4a5bccf1 14/07/2009 00:10:25           
RDPCDD.sys   fffff880`047c9000 fffff880`047d2000 0x00009000 0x4a5bce62 14/07/2009 00:16:34           
rdpencdd.sys   fffff880`047d2000 fffff880`047db000 0x00009000 0x4a5bce62 14/07/2009 00:16:34           
TSDDD.dll   fffff960`005f0000 fffff960`005fa000 0x0000a000 0x4a5bce62 14/07/2009 00:16:34           
rdprefmp.sys   fffff880`047db000 fffff880`047e4000 0x00009000 0x4a5bce63 14/07/2009 00:16:35           
PSHED.dll   fffff880`00c8b000 fffff880`00c9f000 0x00014000 0x4a5be027 14/07/2009 01:32:23 Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\PSHED.dll 
xusb21.sys   fffff880`05571000 fffff880`05583100 0x00012100 0x4a848f49 13/08/2009 22:10:17           
HECIx64.sys   fffff880`071e9000 fffff880`071fa000 0x00011000 0x4ab293e8 17/09/2009 19:54:16           
Impcd.sys   fffff880`04fc1000 fffff880`04fe6180 0x00025180 0x4ae6090d 26/10/2009 20:39:41           
amdxata.sys   fffff880`014b7000 fffff880`014c2000 0x0000b000 0x4ba3a3ca 19/03/2010 16:18:18           
dump_iaStor.sys   fffff880`044b0000 fffff880`046ba000 0x0020a000 0x4bc49f60 13/04/2010 16:44:16           
iaStor.sys   fffff880`012ad000 fffff880`014b7000 0x0020a000 0x4bc49f60 13/04/2010 16:44:16           
AtiHdmi.sys   fffff880`04aa5000 fffff880`04ac8000 0x00023000 0x4be289e7 06/05/2010 09:20:39           
stwrt64.sys   fffff880`0546c000 fffff880`054ee000 0x00082000 0x4c1ad6e6 18/06/2010 02:16:06           
igdpmd64.sys   fffff880`0666c000 fffff880`0708a6e0 0x00a1e6e0 0x4c509ccc 28/07/2010 21:10:36           
hwpolicy.sys   fffff880`0128b000 fffff880`01294000 0x00009000 0x4ce7927e 20/11/2010 09:18:54           
pci.sys   fffff880`00fc9000 fffff880`00ffc000 0x00033000 0x4ce7928f 20/11/2010 09:19:11           
ACPI.sys   fffff880`00f5f000 fffff880`00fb6000 0x00057000 0x4ce79294 20/11/2010 09:19:16           
cdrom.sys   fffff880`046dc000 fffff880`04706000 0x0002a000 0x4ce79298 20/11/2010 09:19:20           
mountmgr.sys   fffff880`0108e000 fffff880`010a8000 0x0001a000 0x4ce79299 20/11/2010 09:19:21           

orgonotic

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #17 on: December 31, 2013, 11:45:48 PM »

CLASSPNP.SYS   fffff880`01a2c000 fffff880`01a5c000 0x00030000 0x4ce7929b 20/11/2010 09:19:23           
fltmgr.sys   fffff880`014c2000 fffff880`0150e000 0x0004c000 0x4ce7929c 20/11/2010 09:19:24           
volmgr.sys   fffff880`00e22000 fffff880`00e37000 0x00015000 0x4ce792a0 20/11/2010 09:19:28           
volsnap.sys   fffff880`00e37000 fffff880`00e83000 0x0004c000 0x4ce792c8 20/11/2010 09:20:08           
volmgrx.sys   fffff880`0101d000 fffff880`01079000 0x0005c000 0x4ce792eb 20/11/2010 09:20:43           
tdx.sys   fffff880`01bb2000 fffff880`01bd4000 0x00022000 0x4ce79332 20/11/2010 09:21:54           
msrpc.sys   fffff880`01522000 fffff880`01580000 0x0005e000 0x4ce79334 20/11/2010 09:21:56           
TDI.SYS   fffff880`01bd4000 fffff880`01be1000 0x0000d000 0x4ce7933e 20/11/2010 09:22:06           
netbt.sys   fffff880`03f19000 fffff880`03f5e000 0x00045000 0x4ce79386 20/11/2010 09:23:18           
udfs.sys   fffff880`02a79000 fffff880`02ace000 0x00055000 0x4ce79433 20/11/2010 09:26:11           
dfsc.sys   fffff880`04aef000 fffff880`04b0d000 0x0001e000 0x4ce79447 20/11/2010 09:26:31           
rdbss.sys   fffff880`03e14000 fffff880`03e65000 0x00051000 0x4ce79497 20/11/2010 09:27:51           
rdyboost.sys   fffff880`00dbd000 fffff880`00df7000 0x0003a000 0x4ce7982e 20/11/2010 09:43:10           
CompositeBus.sys   fffff880`04c1f000 fffff880`04c2f000 0x00010000 0x4ce7a3ed 20/11/2010 10:33:17           
ks.sys   fffff880`0f256000 fffff880`0f299000 0x00043000 0x4ce7a3f3 20/11/2010 10:33:23           
HDAudBus.sys   fffff880`071c5000 fffff880`071e9000 0x00024000 0x4ce7a65e 20/11/2010 10:43:42           
hidusb.sys   fffff880`05584000 fffff880`05592000 0x0000e000 0x4ce7a665 20/11/2010 10:43:49           
WinUSB.sys   fffff880`054fa000 fffff880`0550b000 0x00011000 0x4ce7a66c 20/11/2010 10:43:56           
umbus.sys   fffff880`0f299000 fffff880`0f2ab000 0x00012000 0x4ce7a695 20/11/2010 10:44:37           
tunnel.sys   fffff880`04b1e000 fffff880`04b44000 0x00026000 0x4ce7a846 20/11/2010 10:51:50           
pacer.sys   fffff880`03f67000 fffff880`03f8d000 0x00026000 0x4ce7a862 20/11/2010 10:52:18           
NDProxy.SYS   fffff880`04a90000 fffff880`04aa5000 0x00015000 0x4ce7a864 20/11/2010 10:52:20           
raspptp.sys   fffff880`0f21b000 fffff880`0f23c000 0x00021000 0x4ce7a86f 20/11/2010 10:52:31           
ndiswan.sys   fffff880`0ffcd000 fffff880`0fffc000 0x0002f000 0x4ce7a870 20/11/2010 10:52:32           
rasl2tp.sys   fffff880`0ff9d000 fffff880`0ffc1000 0x00024000 0x4ce7a872 20/11/2010 10:52:34           
wanarp.sys   fffff880`03fcd000 fffff880`03fe8000 0x0001b000 0x4ce7a874 20/11/2010 10:52:36           
termdd.sys   fffff880`03fe8000 fffff880`03ffc000 0x00014000 0x4ce7ab0c 20/11/2010 11:03:40           
hal.dll   fffff800`037e6000 fffff800`0382f000 0x00049000 0x4ce7c669 20/11/2010 13:00:25           
mcupdate_GenuineIntel.dll   fffff880`00c3c000 fffff880`00c8b000 0x0004f000 0x4ce7c737 20/11/2010 13:03:51           
CI.dll   fffff880`00cfd000 fffff880`00dbd000 0x000c0000 0x4ce7c944 20/11/2010 13:12:36           
kdcom.dll   fffff800`00bb8000 fffff800`00bc2000 0x0000a000 0x4d4d8061 05/02/2011 16:52:49           
USBSTOR.SYS   fffff880`05556000 fffff880`05571000 0x0001b000 0x4d79a6fc 11/03/2011 04:37:16           
USBD.SYS   fffff880`04fb0000 fffff880`04fb1f00 0x00001f00 0x4d8c0bfb 25/03/2011 03:28:59           
usbehci.sys   fffff880`06600000 fffff880`06611000 0x00011000 0x4d8c0c00 25/03/2011 03:29:04           
USBPORT.SYS   fffff880`06611000 fffff880`06667000 0x00056000 0x4d8c0c08 25/03/2011 03:29:12           
usbccgp.sys   fffff880`0550b000 fffff880`05528000 0x0001d000 0x4d8c0c0a 25/03/2011 03:29:14           
usbhub.sys   fffff880`04a36000 fffff880`04a90000 0x0005a000 0x4d8c0c15 25/03/2011 03:29:25           
Accelerometer.sys   fffff880`04fe7000 fffff880`04ff4000 0x0000d000 0x4dcd7ca6 13/05/2011 18:47:02           
hpdskflt.sys   fffff880`01294000 fffff880`0129e000 0x0000a000 0x4dcd7ca6 13/05/2011 18:47:02           
Rt64win7.sys   fffff880`04e97000 fffff880`04f1c000 0x00085000 0x4df1baab 10/06/2011 06:33:15           
SASKUTIL64.SYS   fffff880`03e00000 fffff880`03e0a000 0x0000a000 0x4e1cb5d1 12/07/2011 21:00:01           
SASDIFSV64.SYS   fffff880`03e0a000 fffff880`03e14000 0x0000a000 0x4e28b024 21/07/2011 23:03:00           
SynTP.sys   fffff880`04f49000 fffff880`04fb0000 0x00067000 0x4e979fcc 14/10/2011 02:34:52           
Fs_Rec.sys   fffff880`0162c000 fffff880`01636000 0x0000a000 0x4f4eefd2 01/03/2012 03:41:06           
partmgr.sys   fffff880`00e0d000 fffff880`00e22000 0x00015000 0x4f641bc1 17/03/2012 05:06:09           
WDFLDR.SYS   fffff880`00f4f000 fffff880`00f5f000 0x00010000 0x5010ab70 26/07/2012 02:29:04           
cng.sys   fffff880`01580000 fffff880`015f2000 0x00072000 0x50194fb7 01/08/2012 15:48:07           
NETIO.SYS   fffff880`01200000 fffff880`01260000 0x00060000 0x5034f6a0 22/08/2012 15:11:28           
ndis.sys   fffff880`010a8000 fffff880`0119a000 0x000f2000 0x5034f6b2 22/08/2012 15:11:46           
netr28x.sys   fffff880`04c46000 fffff880`04e8a000 0x00244000 0x50b5699a 28/11/2012 01:32:10           
fwpkclnt.sys   fffff880`0119a000 fffff880`011e3000 0x00049000 0x50e4f5c8 03/01/2013 03:06:48           
fvevol.sys   fffff880`00c00000 fffff880`00c3a000 0x0003a000 0x5100a65c 24/01/2013 03:11:24           
dxgmms1.sys   fffff880`0717f000 fffff880`071c5000 0x00046000 0x5164dc13 10/04/2013 03:27:15           
Ntfs.sys   fffff880`0165d000 fffff880`017ff000 0x001a2000 0x5167f5fc 12/04/2013 11:54:36           
Wdf01000.sys   fffff880`00e8d000 fffff880`00f4f000 0x000c2000 0x51c51641 22/06/2013 03:13:05           
HIDPARSE.SYS   fffff880`055ab000 fffff880`055b3080 0x00008080 0x51d3a2f0 03/07/2013 04:05:04           
HIDCLASS.SYS   fffff880`05592000 fffff880`055ab000 0x00019000 0x51d3a2f1 03/07/2013 04:05:05           
usbvideo.sys   fffff880`05528000 fffff880`05555400 0x0002d400 0x51dfdd5e 12/07/2013 10:41:34           
dxgkrnl.sys   fffff880`0708b000 fffff880`0717f000 0x000f4000 0x51fa153d 01/08/2013 07:58:53           
ntoskrnl.exe ntoskrnl.exe+75169 fffff800`03201000 fffff800`037e6000 0x005e5000 0x521ea035 29/08/2013 01:13:25 Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.18247 (win7sp1_gdr.130828-1532) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe 
netr28ux.sys   fffff880`02846000 fffff880`02a79000 0x00233000 0x5229cdcf 06/09/2013 12:42:55           
tcpip.sys   fffff880`01801000 fffff880`01a00000 0x001ff000 0x522bced8 08/09/2013 01:11:52           
cmderd.sys   fffff880`046d3000 fffff880`046dc000 0x00009000 0x524168b4 24/09/2013 10:25:56           
inspect.sys   fffff880`03fa3000 fffff880`03fbe000 0x0001b000 0x524168bb 24/09/2013 10:26:03           
cmdhlp.sys   fffff880`03f0c000 fffff880`03f19000 0x0000d000 0x524168bd 24/09/2013 10:26:05           
cmdguard.sys   fffff880`04706000 fffff880`047b9000 0x000b3000 0x52416910 24/09/2013 10:27:28           
ksecdd.sys   fffff880`01600000 fffff880`0161b000 0x0001b000 0x52423660 25/09/2013 01:03:28           
ksecpkg.sys   fffff880`01260000 fffff880`0128b000 0x0002b000 0x52423a47 25/09/2013 01:20:07           
afd.sys   fffff880`03e69000 fffff880`03ef2000 0x00089000 0x52462c33 28/09/2013 01:09:07           
portcls.sys   fffff880`05407000 fffff880`05444000 0x0003d000 0x524e1b82 04/10/2013 01:36:02           
drmk.sys   fffff880`05444000 fffff880`05466000 0x00022000 0x524e24fe 04/10/2013 02:16:30           
aswRvrt.sys   fffff880`01a91000 fffff880`01aa4000 0x00013000 0x524e72ea 04/10/2013 07:48:58           
aswRdr2.sys   fffff880`03ef2000 fffff880`03f0c000 0x0001a000 0x5257dce9 11/10/2013 11:11:37           
win32k.sys   fffff960`00050000 fffff960`00367000 0x00317000 0x52705fba 30/10/2013 01:24:10           
atikmpag.sys   fffff880`04b44000 fffff880`04be3000 0x0009f000 0x528f7074 22/11/2013 14:55:48           
atikmdag.sys   fffff880`0f2af000 fffff880`0ff9d000 0x00cee000 0x528f7d85 22/11/2013 15:51:33           
aswVmm.sys   fffff880`01a5c000 fffff880`01a91000 0x00035000 0x52a56b93 09/12/2013 07:04:51           
aswSP.sys   fffff880`04400000 fffff880`0446d000 0x0006d000 0x52a56cc2 09/12/2013 07:09:54           
aswSnx.sys   fffff880`01ab2000 fffff880`01bb2000 0x00100000 0x52af7edf 16/12/2013 22:29:51           


jwoods301

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #18 on: January 01, 2014, 12:02:13 AM »
If you generate the HTML report from the single minidump file, you would only have to do one screen capture...

That said, there are a few things I would like you to try...

1. Do a repair of Avast and uninstall the Sandbox tool if it was installed. Reboot and see if the blue screen happens.

2. Right-click on Command Prompt, select Run as Administrator, type in SFC /SCANNNOW at the prompt, and hit Enter. See if any errors are reported and fixed.

3. Run a Memory Diagnostic. CDD.DLL has been implicated in blue screens related to bad RAM, so let's make sure RAM is OK.
« Last Edit: January 01, 2014, 12:12:29 AM by jwoods301 »

orgonotic

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #19 on: January 01, 2014, 12:17:54 AM »
That wall of text is from one file - i noticed on your screenshot it says 'mini' at the start of the name and mine dosent - maybe they are dump files not mini dump? I dunno - this is why its far easier to give someone the files and sort it out becasue i havent got a clue what im doing lol. Cant i just attatch the dump and mini dump files here?... I tried to attach a zip of what the SF_Diagnostic_Tool churned out but it wont acept zip - what if i rename the .dmps to .txt?..

orgonotic

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #20 on: January 01, 2014, 12:26:19 AM »
If you generate the HTML report from the single minidump file, you would only have to do one screen capture...

That said, there are a few things I would like you to try...

1. Do a repair of Avast and uninstall the Sandbox tool if it was installed. Reboot and see if the blue screen happens.

2. Right-click on Command Prompt, select Run as Administrator, type in SFC /SCANNNOW at the prompt, and hit Enter. See if any errors are reported and fixed.

3. Run a Memory Diagnostic. CDD.DLL has been implicated in blue screens related to bad RAM, so let's make sure RAM is OK.

OK, i'l do a complete reinstall - cleaning it off first with the uninstaller thing. I havent got sandbox installed - (thats only paid for version init?). It was 3 weeks between the last 2 BSOD so it could take a long time to really know if anything fixes it. Il do the scannow and memory check later, its doing my head in just thinking about it at the moment :D Cheers for the help though.

jwoods301

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #21 on: January 01, 2014, 12:34:27 AM »
If you generate the HTML report from the single minidump file, you would only have to do one screen capture...

That said, there are a few things I would like you to try...

1. Do a repair of Avast and uninstall the Sandbox tool if it was installed. Reboot and see if the blue screen happens.

2. Right-click on Command Prompt, select Run as Administrator, type in SFC /SCANNNOW at the prompt, and hit Enter. See if any errors are reported and fixed.

3. Run a Memory Diagnostic. CDD.DLL has been implicated in blue screens related to bad RAM, so let's make sure RAM is OK.

OK, i'l do a complete reinstall - cleaning it off first with the uninstaller thing. I havent got sandbox installed - (thats only paid for version init?). It was 3 weeks between the last 2 BSOD so it could take a long time to really know if anything fixes it. Il do the scannow and memory check later, its doing my head in just thinking about it at the moment :D Cheers for the help though.

Thanks for your patience in getting the minidump file information.

Try a repair first before doing a clean re-install.

These issues can be time-consuming to track down.

The problem is that if Avast can't re-create these issues, and no one posts any information and just re-installs, the bug(s) never get fixed.

Let us know how it goes.

dprout69

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #22 on: January 01, 2014, 01:29:25 AM »
If you generate the HTML report from the single minidump file, you would only have to do one screen capture...

That said, there are a few things I would like you to try...

1. Do a repair of Avast and uninstall the Sandbox tool if it was installed. Reboot and see if the blue screen happens.

2. Right-click on Command Prompt, select Run as Administrator, type in SFC /SCANNNOW at the prompt, and hit Enter. See if any errors are reported and fixed.

3. Run a Memory Diagnostic. CDD.DLL has been implicated in blue screens related to bad RAM, so let's make sure RAM is OK.

OK, i'l do a complete reinstall - cleaning it off first with the uninstaller thing. I havent got sandbox installed - (thats only paid for version init?). It was 3 weeks between the last 2 BSOD so it could take a long time to really know if anything fixes it. Il do the scannow and memory check later, its doing my head in just thinking about it at the moment :D Cheers for the help though.

Thanks for your patience in getting the minidump file information.

Try a repair first before doing a clean re-install.

These issues can be time-consuming to track down.

The problem is that if Avast can't re-create these issues, and no one posts any information and just re-installs, the bug(s) never get fixed.

Let us know how it goes.

I didn't do a reinstall... it just kinda went away.  The only pattern I've seen is that people deselect all custom options when installing and that seems to cause it.  I have no clue why mine seemingly stopped.

orgonotic

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #23 on: January 01, 2014, 01:37:16 AM »
I did a repair. Scannow came back clean - so did the memory check.
Guess i have to wait a month and see if any more bsod lol.

orgonotic

  • Guest
Re: Getting BSOD, and told that Avast could be causing them.
« Reply #24 on: January 04, 2014, 10:13:03 PM »
Well i didnt have to wait a month lol..
2 more BSOD after doing a system image restore. Posted dumps to windows forum and:

"The bugchecks are almost the the same, one is showing a COMODO Sandbox Driver along
with an Avast driver and the other is showing only a COMODO Firewall Driver."

Think I'm done with Avast (And Comodo) until they can fix this BSOD problem. Not good - theres no way Avira is as effective as Avast and Comodo together - not even close.