MiniDump after BSOD

Hi friends,

Recently I installed a new motherboard (MSI for CPU 478), new RAM (1gb DDR2) and a new Hard Disk (160gb sata) on a computer. I also installed a fresh version of windows xp. Everything worked fine for only 2 weeks....

Since then, the computer shutdown after (let's say) 15mins. When I restart it right after this crash it doesn't power on. I have to remove the plug from the wall socket and put it back again. then it works. To solve this I remove the CPU, clean the fan (which was both not new) and put them back. I also replace the powersupply with a new one. From that, the computer no more shutdown unexpectedly. Thanks GOD

But things are still going wrong. Now the computer restarts at random. I've attached the minidump files. Can you please decrypt the files and tell me what is going wrong with the pc please?

Considering the BSOD I suspect Avast to be the cause of the restarts, but I need conformation from professionals like you guys FYI, I uninstall and reinstall Avast.

Do you think hardwares are also causing trouble?


Thnx a lot for your help.

Minidump files (zip)

Code:

http://www.sendspace.com/file/g2j0wz

 

Thnx for your reply.

Here are the 3 minidump files.

Minidump 13/09/09
Opened log file 'c:debuglog.txt'

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\minidump\Mini091309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: D:\WINDOWS;D:\WINDOWS\system32;D:\WINDOWS\system32\drivers
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Sun Sep 13 14:49:57.125 2009 (GMT+4)
System Uptime: 0 days 0:08:54.811
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
.........
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000C5, {30000004, 2, 1, 805525a1}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : aswMon2.SYS ( aswMon2+438f )

Followup: MachineOwner
---------

1: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 30000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 805525a1, address which referenced memory

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information.If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: aswMon2

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a8147fe

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt+7b5a1
805525a1 894804 mov dword ptr [eax+4],ecx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from a8ceb38f to 805525a1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f780641c a8ceb38f 00000000 00000001 41764d6e nt+0x7b5a1
f7806470 a8ceb4ac e2834858 8560c008 8560c008 aswMon2+0x438f
f78068c0 a8ceb65b a8cf02e8 8560c008 e1461008 aswMon2+0x44ac
f7806918 a8ced29c e1461008 00000000 a8cf02e4 aswMon2+0x465b
f7806a2c a8ced82e 85613800 85613628 f7806a63 aswMon2+0x629c
f7806a64 a8ce783c 858cbbc0 00613628 804e19ee aswMon2+0x682e
f7806b60 8056e063 86368c08 00000000 856b4a08 aswMon2+0x83c
f7806bd8 805715e8 00000000 f7806c18 00000040 nt+0x97063
f7806c2c 8057f4c3 00000000 00000000 00000001 nt+0x9a5e8
f7806ca8 8057f592 0052e194 00100001 0052e138 nt+0xa84c3
f7806d04 8057f740 0052e194 00100001 0052e138 nt+0xa8592
f7806d44 804ddf0f 0052e194 00100001 0052e138 nt+0xa8740
f7806d64 7c90eb94 badb0d00 0052e114 7cd3f393 nt+0x6f0f
f7806d68 badb0d00 0052e114 7cd3f393 1b103821 0x7c90eb94
f7806d6c 0052e114 7cd3f393 1b103821 00000000 0xbadb0d00
f7806d70 7cd3f393 1b103821 00000000 00000000 0x52e114
f7806d74 1b103821 00000000 00000000 00000000 0x7cd3f393
f7806d78 00000000 00000000 00000000 00000000 0x1b103821


STACK_COMMAND: kb

FOLLOWUP_IP:
aswMon2+438f
a8ceb38f 8945e4 mov dword ptr [ebp-1Ch],eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: aswMon2+438f

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: aswMon2.SYS

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

eax=30000000 ebx=8056b9c0 ecx=8056c218 edx=00000101 esi=00000000 edi=000001ff
eip=805525a1 esp=f78063c8 ebp=f780641c iopl=0 nv up ei pl nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010217
nt+0x7b5a1:
805525a1 894804 mov dword ptr [eax+4],ecx ds:0023:30000004=????????
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
f780641c a8ceb38f 00000000 00000001 41764d6e nt+0x7b5a1
f7806470 a8ceb4ac e2834858 8560c008 8560c008 aswMon2+0x438f
f78068c0 a8ceb65b a8cf02e8 8560c008 e1461008 aswMon2+0x44ac
f7806918 a8ced29c e1461008 00000000 a8cf02e4 aswMon2+0x465b
f7806a2c a8ced82e 85613800 85613628 f7806a63 aswMon2+0x629c
f7806a64 a8ce783c 858cbbc0 00613628 804e19ee aswMon2+0x682e
f7806b60 8056e063 86368c08 00000000 856b4a08 aswMon2+0x83c
f7806bd8 805715e8 00000000 f7806c18 00000040 nt+0x97063
f7806c2c 8057f4c3 00000000 00000000 00000001 nt+0x9a5e8
f7806ca8 8057f592 0052e194 00100001 0052e138 nt+0xa84c3
f7806d04 8057f740 0052e194 00100001 0052e138 nt+0xa8592
f7806d44 804ddf0f 0052e194 00100001 0052e138 nt+0xa8740
f7806d64 7c90eb94 badb0d00 0052e114 7cd3f393 nt+0x6f0f
f7806d68 badb0d00 0052e114 7cd3f393 1b103821 0x7c90eb94
f7806d6c 0052e114 7cd3f393 1b103821 00000000 0xbadb0d00
f7806d70 7cd3f393 1b103821 00000000 00000000 0x52e114
f7806d74 1b103821 00000000 00000000 00000000 0x7cd3f393
f7806d78 00000000 00000000 00000000 00000000 0x1b103821
start end module name
804d7000 80701000 nt ntoskrnl.exe Wed Aug 04 10:18:18 2004 (41107FAA)
80701000 80721d00 hal hal.dll Wed Aug 04 09:59:09 2004 (41107B2D)
a80a8000 a80d1f00 kmixer kmixer.sys Wed Aug 04 10:07:46 2004 (41107D32)
a846a000 a84aa380 HTTP HTTP.sys Wed Aug 04 10:00:09 2004 (41107B69)
a84df000 a84e2b20 aswRdr aswRdr.SYS Mon Aug 17 20:04:27 2009 (4A897F8B)
a87a3000 a87f5180 srv srv.sys Wed Aug 04 10:14:44 2004 (41107ED4)
a8a75000 a8aa1400 mrxdav mrxdav.sys Wed Aug 04 10:00:49 2004 (41107B91)
a8aa2000 a8ab6400 wdmaud wdmaud.sys Wed Aug 04 10:15:03 2004 (41107EE7)
a8bd7000 a8be5d80 sysaudio sysaudio.sys Wed Aug 04 10:15:54 2004 (41107F1A)
a8ce7000 a8cfc580 aswMon2 aswMon2.SYS Tue Aug 11 14:29:18 2009 (4A8147FE)
a8f09000 a8f0c280 ndisuio ndisuio.sys Wed Aug 04 10:03:10 2004 (41107C1E)
a901d000 a9034480 dump_atapi dump_atapi.sys Wed Aug 04 09:59:41 2004 (41107B4D)
a905d000 a907e000 aswSP aswSP.SYS Tue Aug 11 14:28:30 2009 (4A8147CE)
a907e000 a90ec380 mrxsmb mrxsmb.sys Wed Aug 04 10:15:14 2004 (41107EF2)
a90ed000 a9118180 rdbss rdbss.sys Wed Aug 04 10:20:05 2004 (41108015)
a9119000 a913ad00 afd afd.sys Wed Aug 04 10:14:13 2004 (41107EB5)
a913b000 a9162c00 netbt netbt.sys Wed Aug 04 10:14:36 2004 (41107ECC)
a9163000 a9183f00 ipnat ipnat.sys Wed Aug 04 10:04:48 2004 (41107C80)
a9184000 a91dba80 tcpip tcpip.sys Wed Aug 04 10:14:39 2004 (41107ECF)
a91dc000 a91ee400 ipsec ipsec.sys Wed Aug 04 10:14:27 2004 (41107EC3)
aa24b000 aa24d900 Dxapi Dxapi.sys Sat Aug 18 00:53:19 2001 (3B7D843F)
aa2ff000 aa320700 portcls portcls.sys Tue Mar 16 22:58:17 2004 (40574E49)
aa321000 aa7c0000 RtkHDAud RtkHDAud.sys Thu Feb 14 13:04:00 2008 (47B40400)
bf000000 bf011580 dxg dxg.sys Wed Aug 04 10:00:51 2004 (41107B93)
bf012000 bf024000 igxprd32 igxprd32.dll Wed Dec 19 23:32:11 2007 (476971BB)
bf024000 bf04f000 igxpgd32 igxpgd32.dll Wed Dec 19 23:32:11 2007 (476971BB)
bf04f000 bf1e6c00 igxpdv32 igxpdv32.DLL Wed Dec 19 23:32:19 2007 (476971C3)
bf1e7000 bf47a000 igxpdx32 igxpdx32.DLL Wed Dec 19 23:32:14 2007 (476971BE)
bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 10:17:30 2004 (41107F7A)
f6c3b000 f6c6e200 update update.sys Wed Aug 04 09:58:32 2004 (41107B08)
f6c6f000 f6c9f100 rdpdr rdpdr.sys Wed Aug 04 10:01:10 2004 (41107BA6)
f6ca0000 f6cb0e00 psched psched.sys Wed Aug 04 10:04:16 2004 (41107C60)
f6cc1000 f6cc3280 rasacd rasacd.sys Sat Aug 18 00:55:39 2001 (3B7D84CB)
f6cd9000 f6cef680 ndiswan ndiswan.sys Wed Aug 04 10:14:30 2004 (41107EC6)
f6cf0000 f6d12680 ks ks.sys Wed Aug 04 10:15:20 2004 (41107EF8)
f6d13000 f6d26900 parport parport.sys Wed Aug 04 09:59:04 2004 (41107B28)
f6d27000 f6d45ec0 Mtlmnt5 Mtlmnt5.sys Wed Jan 28 16:54:43 2004 (4017B113)
f6d46000 f6da8de0 slntamr slntamr.sys Wed Jan 28 17:15:32 2004 (4017B5F4)
f6da9000 f6dcbe80 USBPORT USBPORT.SYS Wed Aug 04 10:08:34 2004 (41107D62)
f6dcc000 f6de5d80 Rtenicxp Rtenicxp.sys Thu Jan 03 18:10:16 2008 (477CECC8)
f6de6000 f6e0b000 HDAudBus HDAudBus.sys Sat Jan 08 05:07:15 2005 (41DF3243)
f6e0b000 f6e1e780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 10:07:04 2004 (41107D08)
f6e1f000 f73b45e0 igxpmp32 igxpmp32.sys Wed Dec 19 23:32:10 2007 (476971BA)
f73fd000 f7417580 Mup Mup.sys Wed Aug 04 10:15:20 2004 (41107EF8)
f7418000 f7444a80 NDIS NDIS.sys Wed Aug 04 10:14:27 2004 (41107EC3)
f7445000 f74d1480 Ntfs Ntfs.sys Wed Aug 04 10:15:06 2004 (41107EEA)
f74d2000 f74e8780 KSecDD KSecDD.sys Wed Aug 04 09:59:45 2004 (41107B51)
f74e9000 f74faf00 sr sr.sys Wed Aug 04 10:06:22 2004 (41107CDE)
f74fb000 f7519780 fltMgr fltMgr.sys Wed Aug 04 10:01:17 2004 (41107BAD)
f751a000 f7531480 atapi atapi.sys Wed Aug 04 09:59:41 2004 (41107B4D)
f7532000 f7557700 dmio dmio.sys Wed Aug 04 10:07:13 2004 (41107D11)
f7558000 f7576880 ftdisk ftdisk.sys Sat Aug 18 00:52:41 2001 (3B7D8419)
f7577000 f7587a80 pci pci.sys Wed Aug 04 10:07:45 2004 (41107D31)
f7588000 f75b5d80 ACPI ACPI.sys Wed Aug 04 10:07:35 2004 (41107D27)
f75d7000 f75dfc00 isapnp isapnp.sys Sat Aug 18 00:58:01 2001 (3B7D8559)
f75e7000 f75f1500 MountMgr MountMgr.sys Wed Aug 04 09:58:29 2004 (41107B05)
f75f7000 f7603c80 VolSnap VolSnap.sys Wed Aug 04 10:00:14 2004 (41107B6E)
f7607000 f760fe00 disk disk.sys Wed Aug 04 09:59:53 2004 (41107B59)
f7617000 f7623200 CLASSPNP CLASSPNP.SYS Wed Aug 04 10:14:26 2004 (41107EC2)
f7657000 f765fd00 intelppm intelppm.sys Wed Aug 04 09:59:19 2004 (41107B37)
f7667000 f7676d80 serial serial.sys Wed Aug 04 10:15:51 2004 (41107F17)
f7677000 f7683e00 i8042prt i8042prt.sys Wed Aug 04 10:14:36 2004 (41107ECC)
f7687000 f7693180 cdrom cdrom.sys Wed Aug 04 09:59:52 2004 (41107B58)
f7697000 f76a5080 redbook redbook.sys Wed Aug 04 09:59:34 2004 (41107B46)
f76a7000 f76b1380 imapi imapi.sys Wed Aug 04 10:00:12 2004 (41107B6C)
f76b7000 f76c3880 rasl2tp rasl2tp.sys Wed Aug 04 10:14:21 2004 (41107EBD)
f76c7000 f76d1200 raspppoe raspppoe.sys Wed Aug 04 10:05:06 2004 (41107C92)
f76d7000 f76e2d00 raspptp raspptp.sys Wed Aug 04 10:14:26 2004 (41107EC2)
f76e7000 f76ef900 msgpc msgpc.sys Wed Aug 04 10:04:11 2004 (41107C5B)
f76f7000 f7700f00 termdd termdd.sys Wed Aug 04 09:58:52 2004 (41107B1C)
f7707000 f7710480 NDProxy NDProxy.SYS Sat Aug 18 00:55:30 2001 (3B7D84C2)
f7727000 f7735b80 drmk drmk.sys Wed Aug 04 10:07:54 2004 (41107D3A)
f7737000 f7745100 usbhub usbhub.sys Wed Aug 04 10:08:40 2004 (41107D68)
f7757000 f77612c0 aswTdi aswTdi.SYS Mon Aug 17 20:04:38 2009 (4A897F96)
f7767000 f776f700 wanarp wanarp.sys Wed Aug 04 10:04:57 2004 (41107C89)
f7777000 f777f700 netbios netbios.sys Wed Aug 04 10:03:19 2004 (41107C27)
f7787000 f778f880 Fips Fips.SYS Sat Aug 18 05:31:49 2001 (3B7DC585)
f77a7000 f77b5780 usbaudio usbaudio.sys Wed Aug 04 10:07:52 2004 (41107D38)
f77b7000 f77c6900 Cdfs Cdfs.SYS Wed Aug 04 10:14:09 2004 (41107EB1)
f7857000 f785d200 PCIIDEX PCIIDEX.SYS Wed Aug 04 09:59:40 2004 (41107B4C)
f785f000 f7863900 PartMgr PartMgr.sys Sat Aug 18 05:32:23 2001 (3B7DC5A7)
f786f000 f7876b80 usbccgp usbccgp.sys Wed Aug 04 10:08:45 2004 (41107D6D)
f78a7000 f78ac000 usbuhci usbuhci.sys Wed Aug 04 10:08:34 2004 (41107D62)
f78af000 f78b5800 usbehci usbehci.sys Wed Aug 04 10:08:34 2004 (41107D62)
f78c7000 f78ce580 Modem Modem.SYS Wed Aug 04 10:08:04 2004 (41107D44)
f78cf000 f78d7000 aswFsBlk aswFsBlk.sys Tue Aug 11 14:28:20 2009 (4A8147C4)
f78df000 f78e0000 fdc fdc.sys unavailable (00000000)
f78e7000 f78ed000 kbdclass kbdclass.sys Wed Aug 04 09:58:32 2004 (41107B08)
f78ef000 f78f4a00 mouclass mouclass.sys Wed Aug 04 09:58:32 2004 (41107B08)
f78ff000 f7903500 watchdog watchdog.sys Wed Aug 04 10:07:32 2004 (41107D24)
f791f000 f7923880 TDI TDI.SYS Wed Aug 04 10:07:47 2004 (41107D33)
f792f000 f7933580 ptilink ptilink.sys Sat Aug 18 00:49:53 2001 (3B7D8371)
f793f000 f7943080 raspti raspti.sys Sat Aug 18 00:55:32 2001 (3B7D84C4)
f795f000 f7964000 flpydisk flpydisk.sys Wed Aug 04 09:59:24 2004 (41107B3C)
f7977000 f797c200 vga vga.sys Wed Aug 04 10:07:06 2004 (41107D0A)
f7987000 f798ba80 Msfs Msfs.SYS Wed Aug 04 10:00:37 2004 (41107B85)
f7997000 f799e880 Npfs Npfs.SYS Wed Aug 04 10:00:38 2004 (41107B86)
f79cf000 f79d3a80 Aavmker4 Aavmker4.SYS Mon Aug 17 20:03:20 2009 (4A897F48)
f79e7000 f79ea000 BOOTVID BOOTVID.dll Sat Aug 18 00:49:09 2001 (3B7D8345)
f79eb000 f79ee580 RecAgent RecAgent.sys Tue Jan 13 17:03:28 2004 (4003ECA0)
f7a7b000 f7a7e360 SlWdmSup SlWdmSup.sys Wed Jan 28 16:20:42 2004 (4017A91A)
f7a87000 f7a8ac80 serenum serenum.sys Wed Aug 04 09:59:06 2004 (41107B2A)
f7a9f000 f7aa2f00 MODEMCSA MODEMCSA.sys Sat Aug 18 00:57:37 2001 (3B7D8541)
f7aa3000 f7aa5580 ndistapi ndistapi.sys Sat Aug 18 00:55:29 2001 (3B7D84C1)
f7ac3000 f7ac6c80 mssmbios mssmbios.sys Wed Aug 04 10:07:47 2004 (41107D33)
f7ad7000 f7ad8b80 kdcom kdcom.dll Sat Aug 18 00:49:10 2001 (3B7D8346)
f7ad9000 f7ada100 WMILIB WMILIB.SYS Sat Aug 18 01:07:23 2001 (3B7D878B)
f7adb000 f7adc700 dmload dmload.sys Sat Aug 18 00:58:15 2001 (3B7D8567)
f7ae3000 f7ae4100 swenum swenum.sys Wed Aug 04 09:58:41 2004 (41107B11)
f7aed000 f7aee280 USBD USBD.SYS Sat Aug 18 01:02:58 2001 (3B7D8682)
f7af1000 f7af2f00 Fs_Rec Fs_Rec.SYS Sat Aug 18 00:49:37 2001 (3B7D8361)
f7af5000 f7af6080 Beep Beep.SYS Sat Aug 18 00:47:33 2001 (3B7D82E5)
f7af9000 f7afa080 mnmdd mnmdd.SYS Sat Aug 18 00:57:28 2001 (3B7D8538)
f7afd000 f7afe080 RDPCDD RDPCDD.sys Sat Aug 18 00:46:56 2001 (3B7D82C0)
f7b05000 f7b06100 dump_WMILIB dump_WMILIB.SYS Sat Aug 18 01:07:23 2001 (3B7D878B)
f7b8f000 f7b90a80 ParVdm ParVdm.SYS Sat Aug 18 00:49:49 2001 (3B7D836D)
f7b9f000 f7b9fd00 pciide pciide.sys Sat Aug 18 00:51:49 2001 (3B7D83E5)
f7bcc000 f7bccd00 dxgthk dxgthk.sys Sat Aug 18 00:53:12 2001 (3B7D8438)
f7c5a000 f7c5ac00 audstub audstub.sys Sat Aug 18 00:59:40 2001 (3B7D85BC)
f7c9d000 f7c9db80 Null Null.SYS Sat Aug 18 00:47:39 2001 (3B7D82EB)

Unloaded modules:
a80a8000 a80d2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a8a00000 a8a2a000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7cef000 f7cf0000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a8a2a000 a8a4d000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a8da5000 a8db2000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a8bb7000 a8bc5000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b75000 f7b77000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f796f000 f7974000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f6cc9000 f6ccc000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:debuglog.txt

 

Ok. I better read the rules then.

Yes. I carefully followed the instructions.

I unistalled and reinstall Avast. But I think I will completely remove it, just for testing.

If not asking too much, do you think Avast can cause the computer to shutdown? Every articles I read concerning this issue, they all are talking about sudden restart. How can I know if my hardwares are faulty. Noting that I tested the RAM using memtest and result was "Pass" with no errors.

 

Thnx a lot for all your replies PeteC.

I removed avast and testing it. Hope it will be fine now.