system
December 31, 2013, 8:28pm
1
Hi, i’ve been using free Avast 2014 for a while. I’ve been getting BSOD on startup sometimes and i think they started happening after i instaled Avast and free Comodo.
I’ve got some mini dumps and the like from ‘SF Diagnostic Tool’ if anyone knows how to read them?..
I posted them to www.sevenforums.com and he said it was a WiFi driver, which ive updated, but that Avast was showing up as being a problem too. I dont really want to switch back to Avira if i can help it.
Cheers
system
December 31, 2013, 8:30pm
2
This tool from NirSoft is helpful in determining what specifically caused it…
http://www.nirsoft.net/utils/blue_screen_view.html
system
December 31, 2013, 8:32pm
3
Yeah, i saw that in anouther post and downloaded it, but i dont understand how it works lol. I cant handle the gibberish computers come out with, it’d be way simpler to show the mini dumps to someone who actually understands all that stuff…
system
December 31, 2013, 8:52pm
4
Not that difficult…
Open the minidump with the program, and click View > HTML Report - All Items.
Post the report here in your thread.
system
December 31, 2013, 8:53pm
5
BSOD has been reported many times with this latest version… just read the subject titles. Basically there is no fix right now.
system
December 31, 2013, 9:06pm
6
Not that difficult…
Open the minidump with the program, and click View > HTML Report - All Items.
Post the report here in your thread.
I did that but it creates a table in the internet explorer, i tried selecting all the text and pasting but it looks like this, well messy lol:
Crash List
Created by using BlueScreenView
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time
123013-17253-01.dmp 30/12/2013 16:15:37 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000c0000005 fffff800
0326eac5 fffff88002d8c090 00000000
00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\123013-17253-01.dmp 4 15 7601 278,744 30/12/2013 16:21:39
112813-23618-01.dmp 28/11/2013 20:09:01 BAD_POOL_HEADER 0x00000019 0000000000000003 fffffa80
0a550010 0000000000000000 fffffa80
0a550010 USBPORT.SYS USBPORT.SYS+2d208 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\112813-23618-01.dmp 4 15 7601 319,680 28/11/2013 20:09:59
112613-34897-01.dmp 26/11/2013 11:06:29 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000c0000005 fffff800
035ae030 fffff88006d65100 00000000
00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\112613-34897-01.dmp 4 15 7601 278,744 26/11/2013 11:07:48
Ah, looks like its back to Avira then, oh joy.
system
December 31, 2013, 9:09pm
7
Life is not always “all or nothing”. Consider deconfiguring some of the Avast features if they’re causing you problems.
For example, uninstall, then reinstall and uncheck some of the “Tools” they offer. The shields are really the most important part of the product.
-Noel
system
December 31, 2013, 9:12pm
8
I installed with just file and web sheilds and left off all that other stuff.
system
December 31, 2013, 9:15pm
9
Don’t know what else I can offer other than to state that I’ve been using Avast since 2005 and I haven’t had one blue screen from it. Regardless of what some other posters may have said, it’s not a foregone conclusion it’s going to crash your system. I honestly suspect something else is doing it.
-Noel
system
December 31, 2013, 9:42pm
10
Not that difficult…
Open the minidump with the program, and click View > HTML Report - All Items.
Post the report here in your thread.
I did that but it creates a table in the internet explorer, i tried selecting all the text and pasting but it looks like this, well messy lol:
Crash List
Created by using BlueScreenView
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Crash Address Stack Address 1 Stack Address 2 Stack Address 3 Computer Name Full Path Processors Count Major Version Minor Version Dump File Size Dump File Time
123013-17253-01.dmp 30/12/2013 16:15:37 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000c0000005 fffff800
0326eac5 fffff88002d8c090 00000000
00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\123013-17253-01.dmp 4 15 7601 278,744 30/12/2013 16:21:39
112813-23618-01.dmp 28/11/2013 20:09:01 BAD_POOL_HEADER 0x00000019 0000000000000003 fffffa80
0a550010 0000000000000000 fffffa80
0a550010 USBPORT.SYS USBPORT.SYS+2d208 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\112813-23618-01.dmp 4 15 7601 319,680 28/11/2013 20:09:59
112613-34897-01.dmp 26/11/2013 11:06:29 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000c0000005 fffff800
035ae030 fffff88006d65100 00000000
00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\112613-34897-01.dmp 4 15 7601 278,744 26/11/2013 11:07:48
Ah, looks like its back to Avira then, oh joy.
You may need to use a screen capture program to convert the HTML report to a .jpg file.
The free ScreenshotCaptor works well.
When posting, click on the “Attachments and other options” link, and under the “Attach:” section, click on “Browse…” and attach the file.
system
December 31, 2013, 10:02pm
11
system
December 31, 2013, 10:09pm
12
Click on the minidump file that was created on 12/30 and expand it.
Then create the report and post it.
system
December 31, 2013, 10:22pm
13
Not sure what you mean by expand it?.. This it?..
system
December 31, 2013, 10:25pm
14
Those are the properties…you need to open the individual minidump file.
system
December 31, 2013, 10:31pm
16
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…
system
December 31, 2013, 10:45pm
17
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 fffff96000620000 fffff960
00647000 0x00027000 0x00000000
spldr.sys fffff8800163e000 fffff880
01646000 0x00008000 0x4a0858bb 11/05/2009 16:56:27
intelppm.sys fffff88004c09000 fffff880
04c1f000 0x00016000 0x4a5bc0fd 13/07/2009 23:19:25
msisadrv.sys fffff88000fbf000 fffff880
00fc9000 0x0000a000 0x4a5bc0fe 13/07/2009 23:19:26
pcw.sys fffff8800161b000 fffff880
0162c000 0x00011000 0x4a5bc0ff 13/07/2009 23:19:27
Null.SYS fffff8800446d000 fffff880
04476000 0x00009000 0x4a5bc109 13/07/2009 23:19:37
Msfs.SYS fffff880047e4000 fffff880
047ef000 0x0000b000 0x4a5bc113 13/07/2009 23:19:47
Npfs.SYS fffff880047ef000 fffff880
04800000 0x00011000 0x4a5bc114 13/07/2009 23:19:48
kbdclass.sys fffff88004f3a000 fffff880
04f49000 0x0000f000 0x4a5bc116 13/07/2009 23:19:50
mouclass.sys fffff88004fb2000 fffff880
04fc1000 0x0000f000 0x4a5bc116 13/07/2009 23:19:50
WMILIB.SYS fffff88000fb6000 fffff880
00fbf000 0x00009000 0x4a5bc117 13/07/2009 23:19:51
wd.sys fffff88001636000 fffff880
0163e000 0x00008000 0x4a5bc11b 13/07/2009 23:19:55
CLFS.SYS fffff88000c9f000 fffff880
00cfd000 0x0005e000 0x4a5bc11d 13/07/2009 23:19:57
disk.sys fffff880011e3000 fffff880
011f9000 0x00016000 0x4a5bc11d 13/07/2009 23:19:57
i8042prt.sys fffff88004f1c000 fffff880
04f3a000 0x0001e000 0x4a5bc11d 13/07/2009 23:19:57
nsiproxy.sys fffff88001be1000 fffff880
01bed000 0x0000c000 0x4a5bc15e 13/07/2009 23:21:02
dump_dumpfve.sys fffff88002adc000 fffff880
02aef000 0x00013000 0x4a5bc18f 13/07/2009 23:21:51
fastfat.SYS fffff88004a00000 fffff880
04a36000 0x00036000 0x4a5bc1f0 13/07/2009 23:23:28
mup.sys fffff88001646000 fffff880
01658000 0x00012000 0x4a5bc201 13/07/2009 23:23:45
BATTC.SYS fffff88001082000 fffff880
0108e000 0x0000c000 0x4a5bc3b5 13/07/2009 23:31:01
compbatt.sys fffff88001079000 fffff880
01082000 0x00009000 0x4a5bc3b6 13/07/2009 23:31:02
wmiacpi.sys fffff88004c00000 fffff880
04c09000 0x00009000 0x4a5bc3b6 13/07/2009 23:31:02
CmBatt.sys fffff88004ff4000 fffff880
04ff8500 0x00004500 0x4a5bc3b7 13/07/2009 23:31:03
mssmbios.sys fffff88001bed000 fffff880
01bf8000 0x0000b000 0x4a5bc3be 13/07/2009 23:31:10
fileinfo.sys fffff8800150e000 fffff880
01522000 0x00014000 0x4a5bc481 13/07/2009 23:34:25
blbdrive.sys fffff88004b0d000 fffff880
04b1e000 0x00011000 0x4a5bc4df 13/07/2009 23:35:59
discache.sys fffff88001a00000 fffff880
01a0f000 0x0000f000 0x4a5bc52e 13/07/2009 23:37:18
watchdog.sys fffff880047b9000 fffff880
047c9000 0x00010000 0x4a5bc53f 13/07/2009 23:37:35
Dxapi.sys fffff880054ee000 fffff880
054fa000 0x0000c000 0x4a5bc574 13/07/2009 23:38:28
vga.sys fffff8800447d000 fffff880
0448b000 0x0000e000 0x4a5bc587 13/07/2009 23:38:47
VIDEOPRT.SYS fffff8800448b000 fffff880
044b0000 0x00025000 0x4a5bc58b 13/07/2009 23:38:51
monitor.sys fffff880055c1000 fffff880
055cf000 0x0000e000 0x4a5bc58c 13/07/2009 23:38:52
Beep.SYS fffff88004476000 fffff880
0447d000 0x00007000 0x4a5bca8d 14/07/2009 00:00:13
swenum.sys fffff88004ff9000 fffff880
04ffa480 0x00001480 0x4a5bca92 14/07/2009 00:00:18
ksthunk.sys fffff88005466000 fffff880
0546b200 0x00005200 0x4a5bca93 14/07/2009 00:00:19
mouhid.sys fffff880055b4000 fffff880
055c1000 0x0000d000 0x4a5bca94 14/07/2009 00:00:20
crashdmp.sys fffff88002ace000 fffff880
02adc000 0x0000e000 0x4a5bcabd 14/07/2009 00:01:01
vdrvroot.sys fffff88000e00000 fffff880
00e0d000 0x0000d000 0x4a5bcadb 14/07/2009 00:01:31
vwifibus.sys fffff88004e8a000 fffff880
04e97000 0x0000d000 0x4a5bcc39 14/07/2009 00:07:21
vwififlt.sys fffff88003f8d000 fffff880
03fa3000 0x00016000 0x4a5bcc3a 14/07/2009 00:07:22
netbios.sys fffff88003fbe000 fffff880
03fcd000 0x0000f000 0x4a5bccb6 14/07/2009 00:09:26
wfplwf.sys fffff88003f5e000 fffff880
03f67000 0x00009000 0x4a5bccb6 14/07/2009 00:09:26
ndistapi.sys fffff8800ffc1000 fffff880
0ffcd000 0x0000c000 0x4a5bccd8 14/07/2009 00:10:00
raspppoe.sys fffff8800f200000 fffff880
0f21b000 0x0001b000 0x4a5bcce9 14/07/2009 00:10:17
AgileVpn.sys fffff88004c2f000 fffff880
04c45000 0x00016000 0x4a5bccf0 14/07/2009 00:10:24
rassstp.sys fffff8800f23c000 fffff880
0f256000 0x0001a000 0x4a5bccf1 14/07/2009 00:10:25
RDPCDD.sys fffff880047c9000 fffff880
047d2000 0x00009000 0x4a5bce62 14/07/2009 00:16:34
rdpencdd.sys fffff880047d2000 fffff880
047db000 0x00009000 0x4a5bce62 14/07/2009 00:16:34
TSDDD.dll fffff960005f0000 fffff960
005fa000 0x0000a000 0x4a5bce62 14/07/2009 00:16:34
rdprefmp.sys fffff880047db000 fffff880
047e4000 0x00009000 0x4a5bce63 14/07/2009 00:16:35
PSHED.dll fffff88000c8b000 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 fffff88005571000 fffff880
05583100 0x00012100 0x4a848f49 13/08/2009 22:10:17
HECIx64.sys fffff880071e9000 fffff880
071fa000 0x00011000 0x4ab293e8 17/09/2009 19:54:16
Impcd.sys fffff88004fc1000 fffff880
04fe6180 0x00025180 0x4ae6090d 26/10/2009 20:39:41
amdxata.sys fffff880014b7000 fffff880
014c2000 0x0000b000 0x4ba3a3ca 19/03/2010 16:18:18
dump_iaStor.sys fffff880044b0000 fffff880
046ba000 0x0020a000 0x4bc49f60 13/04/2010 16:44:16
iaStor.sys fffff880012ad000 fffff880
014b7000 0x0020a000 0x4bc49f60 13/04/2010 16:44:16
AtiHdmi.sys fffff88004aa5000 fffff880
04ac8000 0x00023000 0x4be289e7 06/05/2010 09:20:39
stwrt64.sys fffff8800546c000 fffff880
054ee000 0x00082000 0x4c1ad6e6 18/06/2010 02:16:06
igdpmd64.sys fffff8800666c000 fffff880
0708a6e0 0x00a1e6e0 0x4c509ccc 28/07/2010 21:10:36
hwpolicy.sys fffff8800128b000 fffff880
01294000 0x00009000 0x4ce7927e 20/11/2010 09:18:54
pci.sys fffff88000fc9000 fffff880
00ffc000 0x00033000 0x4ce7928f 20/11/2010 09:19:11
ACPI.sys fffff88000f5f000 fffff880
00fb6000 0x00057000 0x4ce79294 20/11/2010 09:19:16
cdrom.sys fffff880046dc000 fffff880
04706000 0x0002a000 0x4ce79298 20/11/2010 09:19:20
mountmgr.sys fffff8800108e000 fffff880
010a8000 0x0001a000 0x4ce79299 20/11/2010 09:19:21
system
December 31, 2013, 10:45pm
18
CLASSPNP.SYS fffff88001a2c000 fffff880
01a5c000 0x00030000 0x4ce7929b 20/11/2010 09:19:23
fltmgr.sys fffff880014c2000 fffff880
0150e000 0x0004c000 0x4ce7929c 20/11/2010 09:19:24
volmgr.sys fffff88000e22000 fffff880
00e37000 0x00015000 0x4ce792a0 20/11/2010 09:19:28
volsnap.sys fffff88000e37000 fffff880
00e83000 0x0004c000 0x4ce792c8 20/11/2010 09:20:08
volmgrx.sys fffff8800101d000 fffff880
01079000 0x0005c000 0x4ce792eb 20/11/2010 09:20:43
tdx.sys fffff88001bb2000 fffff880
01bd4000 0x00022000 0x4ce79332 20/11/2010 09:21:54
msrpc.sys fffff88001522000 fffff880
01580000 0x0005e000 0x4ce79334 20/11/2010 09:21:56
TDI.SYS fffff88001bd4000 fffff880
01be1000 0x0000d000 0x4ce7933e 20/11/2010 09:22:06
netbt.sys fffff88003f19000 fffff880
03f5e000 0x00045000 0x4ce79386 20/11/2010 09:23:18
udfs.sys fffff88002a79000 fffff880
02ace000 0x00055000 0x4ce79433 20/11/2010 09:26:11
dfsc.sys fffff88004aef000 fffff880
04b0d000 0x0001e000 0x4ce79447 20/11/2010 09:26:31
rdbss.sys fffff88003e14000 fffff880
03e65000 0x00051000 0x4ce79497 20/11/2010 09:27:51
rdyboost.sys fffff88000dbd000 fffff880
00df7000 0x0003a000 0x4ce7982e 20/11/2010 09:43:10
CompositeBus.sys fffff88004c1f000 fffff880
04c2f000 0x00010000 0x4ce7a3ed 20/11/2010 10:33:17
ks.sys fffff8800f256000 fffff880
0f299000 0x00043000 0x4ce7a3f3 20/11/2010 10:33:23
HDAudBus.sys fffff880071c5000 fffff880
071e9000 0x00024000 0x4ce7a65e 20/11/2010 10:43:42
hidusb.sys fffff88005584000 fffff880
05592000 0x0000e000 0x4ce7a665 20/11/2010 10:43:49
WinUSB.sys fffff880054fa000 fffff880
0550b000 0x00011000 0x4ce7a66c 20/11/2010 10:43:56
umbus.sys fffff8800f299000 fffff880
0f2ab000 0x00012000 0x4ce7a695 20/11/2010 10:44:37
tunnel.sys fffff88004b1e000 fffff880
04b44000 0x00026000 0x4ce7a846 20/11/2010 10:51:50
pacer.sys fffff88003f67000 fffff880
03f8d000 0x00026000 0x4ce7a862 20/11/2010 10:52:18
NDProxy.SYS fffff88004a90000 fffff880
04aa5000 0x00015000 0x4ce7a864 20/11/2010 10:52:20
raspptp.sys fffff8800f21b000 fffff880
0f23c000 0x00021000 0x4ce7a86f 20/11/2010 10:52:31
ndiswan.sys fffff8800ffcd000 fffff880
0fffc000 0x0002f000 0x4ce7a870 20/11/2010 10:52:32
rasl2tp.sys fffff8800ff9d000 fffff880
0ffc1000 0x00024000 0x4ce7a872 20/11/2010 10:52:34
wanarp.sys fffff88003fcd000 fffff880
03fe8000 0x0001b000 0x4ce7a874 20/11/2010 10:52:36
termdd.sys fffff88003fe8000 fffff880
03ffc000 0x00014000 0x4ce7ab0c 20/11/2010 11:03:40
hal.dll fffff800037e6000 fffff800
0382f000 0x00049000 0x4ce7c669 20/11/2010 13:00:25
mcupdate_GenuineIntel.dll fffff88000c3c000 fffff880
00c8b000 0x0004f000 0x4ce7c737 20/11/2010 13:03:51
CI.dll fffff88000cfd000 fffff880
00dbd000 0x000c0000 0x4ce7c944 20/11/2010 13:12:36
kdcom.dll fffff80000bb8000 fffff800
00bc2000 0x0000a000 0x4d4d8061 05/02/2011 16:52:49
USBSTOR.SYS fffff88005556000 fffff880
05571000 0x0001b000 0x4d79a6fc 11/03/2011 04:37:16
USBD.SYS fffff88004fb0000 fffff880
04fb1f00 0x00001f00 0x4d8c0bfb 25/03/2011 03:28:59
usbehci.sys fffff88006600000 fffff880
06611000 0x00011000 0x4d8c0c00 25/03/2011 03:29:04
USBPORT.SYS fffff88006611000 fffff880
06667000 0x00056000 0x4d8c0c08 25/03/2011 03:29:12
usbccgp.sys fffff8800550b000 fffff880
05528000 0x0001d000 0x4d8c0c0a 25/03/2011 03:29:14
usbhub.sys fffff88004a36000 fffff880
04a90000 0x0005a000 0x4d8c0c15 25/03/2011 03:29:25
Accelerometer.sys fffff88004fe7000 fffff880
04ff4000 0x0000d000 0x4dcd7ca6 13/05/2011 18:47:02
hpdskflt.sys fffff88001294000 fffff880
0129e000 0x0000a000 0x4dcd7ca6 13/05/2011 18:47:02
Rt64win7.sys fffff88004e97000 fffff880
04f1c000 0x00085000 0x4df1baab 10/06/2011 06:33:15
SASKUTIL64.SYS fffff88003e00000 fffff880
03e0a000 0x0000a000 0x4e1cb5d1 12/07/2011 21:00:01
SASDIFSV64.SYS fffff88003e0a000 fffff880
03e14000 0x0000a000 0x4e28b024 21/07/2011 23:03:00
SynTP.sys fffff88004f49000 fffff880
04fb0000 0x00067000 0x4e979fcc 14/10/2011 02:34:52
Fs_Rec.sys fffff8800162c000 fffff880
01636000 0x0000a000 0x4f4eefd2 01/03/2012 03:41:06
partmgr.sys fffff88000e0d000 fffff880
00e22000 0x00015000 0x4f641bc1 17/03/2012 05:06:09
WDFLDR.SYS fffff88000f4f000 fffff880
00f5f000 0x00010000 0x5010ab70 26/07/2012 02:29:04
cng.sys fffff88001580000 fffff880
015f2000 0x00072000 0x50194fb7 01/08/2012 15:48:07
NETIO.SYS fffff88001200000 fffff880
01260000 0x00060000 0x5034f6a0 22/08/2012 15:11:28
ndis.sys fffff880010a8000 fffff880
0119a000 0x000f2000 0x5034f6b2 22/08/2012 15:11:46
netr28x.sys fffff88004c46000 fffff880
04e8a000 0x00244000 0x50b5699a 28/11/2012 01:32:10
fwpkclnt.sys fffff8800119a000 fffff880
011e3000 0x00049000 0x50e4f5c8 03/01/2013 03:06:48
fvevol.sys fffff88000c00000 fffff880
00c3a000 0x0003a000 0x5100a65c 24/01/2013 03:11:24
dxgmms1.sys fffff8800717f000 fffff880
071c5000 0x00046000 0x5164dc13 10/04/2013 03:27:15
Ntfs.sys fffff8800165d000 fffff880
017ff000 0x001a2000 0x5167f5fc 12/04/2013 11:54:36
Wdf01000.sys fffff88000e8d000 fffff880
00f4f000 0x000c2000 0x51c51641 22/06/2013 03:13:05
HIDPARSE.SYS fffff880055ab000 fffff880
055b3080 0x00008080 0x51d3a2f0 03/07/2013 04:05:04
HIDCLASS.SYS fffff88005592000 fffff880
055ab000 0x00019000 0x51d3a2f1 03/07/2013 04:05:05
usbvideo.sys fffff88005528000 fffff880
05555400 0x0002d400 0x51dfdd5e 12/07/2013 10:41:34
dxgkrnl.sys fffff8800708b000 fffff880
0717f000 0x000f4000 0x51fa153d 01/08/2013 07:58:53
ntoskrnl.exe ntoskrnl.exe+75169 fffff80003201000 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 fffff88002846000 fffff880
02a79000 0x00233000 0x5229cdcf 06/09/2013 12:42:55
tcpip.sys fffff88001801000 fffff880
01a00000 0x001ff000 0x522bced8 08/09/2013 01:11:52
cmderd.sys fffff880046d3000 fffff880
046dc000 0x00009000 0x524168b4 24/09/2013 10:25:56
inspect.sys fffff88003fa3000 fffff880
03fbe000 0x0001b000 0x524168bb 24/09/2013 10:26:03
cmdhlp.sys fffff88003f0c000 fffff880
03f19000 0x0000d000 0x524168bd 24/09/2013 10:26:05
cmdguard.sys fffff88004706000 fffff880
047b9000 0x000b3000 0x52416910 24/09/2013 10:27:28
ksecdd.sys fffff88001600000 fffff880
0161b000 0x0001b000 0x52423660 25/09/2013 01:03:28
ksecpkg.sys fffff88001260000 fffff880
0128b000 0x0002b000 0x52423a47 25/09/2013 01:20:07
afd.sys fffff88003e69000 fffff880
03ef2000 0x00089000 0x52462c33 28/09/2013 01:09:07
portcls.sys fffff88005407000 fffff880
05444000 0x0003d000 0x524e1b82 04/10/2013 01:36:02
drmk.sys fffff88005444000 fffff880
05466000 0x00022000 0x524e24fe 04/10/2013 02:16:30
aswRvrt.sys fffff88001a91000 fffff880
01aa4000 0x00013000 0x524e72ea 04/10/2013 07:48:58
aswRdr2.sys fffff88003ef2000 fffff880
03f0c000 0x0001a000 0x5257dce9 11/10/2013 11:11:37
win32k.sys fffff96000050000 fffff960
00367000 0x00317000 0x52705fba 30/10/2013 01:24:10
atikmpag.sys fffff88004b44000 fffff880
04be3000 0x0009f000 0x528f7074 22/11/2013 14:55:48
atikmdag.sys fffff8800f2af000 fffff880
0ff9d000 0x00cee000 0x528f7d85 22/11/2013 15:51:33
aswVmm.sys fffff88001a5c000 fffff880
01a91000 0x00035000 0x52a56b93 09/12/2013 07:04:51
aswSP.sys fffff88004400000 fffff880
0446d000 0x0006d000 0x52a56cc2 09/12/2013 07:09:54
aswSnx.sys fffff88001ab2000 fffff880
01bb2000 0x00100000 0x52af7edf 16/12/2013 22:29:51
system
December 31, 2013, 11:02pm
19
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…
Do a repair of Avast and uninstall the Sandbox tool if it was installed. Reboot and see if the blue screen happens.
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.
Run a Memory Diagnostic. CDD.DLL has been implicated in blue screens related to bad RAM, so let’s make sure RAM is OK.
system
December 31, 2013, 11:17pm
20
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?..