Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows Blue Screen


  • Please log in to reply
1 reply to this topic

#1 chz123

chz123

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:10 AM

Posted 25 July 2013 - 06:58 PM

Hi, I need some help with my pc. I got exactly 3 blue screens today out of nowhere. I have never had any issues up until today. Here are the .dmp files. My PC is a very old machine, custom built. Windows XP Pro, amd dualcore processor,  Asrock a780LM motherboard, 3ghz,  3.25ghz ram (g.skill 2x 2gb ram sticks), nvidia 9800GT, Corsair 500w psu...

My pc is running just fine at the moment and it has been for the past few hours, I just dont want another blue screen in the future..

 

Any help would be appreciated.

 

 

1st crash:

 

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini072513-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:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.130503-0418
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jul 25 13:55:32.656 2013 (GMT-4)
System Uptime: 0 days 5:06:12.392
Loading Kernel Symbols
...............................................................
................................................................

Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}

Probably caused by : kmixer.sys ( kmixer!FinalCopyInt32toFloat+2 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 00000000 to ab5daf72

STACK_TEXT:  
ac246d50 00000000 89ea38a8 8a004430 89ea3960 kmixer!FinalCopyInt32toFloat+0x2


STACK_COMMAND:  kb

FOLLOWUP_IP:
kmixer!FinalCopyInt32toFloat+2
ab5daf72 55              push    ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  kmixer!FinalCopyInt32toFloat+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kmixer

IMAGE_NAME:  kmixer.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  480254b3

FAILURE_BUCKET_ID:  0x7f_8_kmixer!FinalCopyInt32toFloat+2

BUCKET_ID:  0x7f_8_kmixer!FinalCopyInt32toFloat+2

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 00000000 to ab5daf72

STACK_TEXT:  
ac246d50 00000000 89ea38a8 8a004430 89ea3960 kmixer!FinalCopyInt32toFloat+0x2


STACK_COMMAND:  kb

FOLLOWUP_IP:
kmixer!FinalCopyInt32toFloat+2
ab5daf72 55              push    ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  kmixer!FinalCopyInt32toFloat+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kmixer

IMAGE_NAME:  kmixer.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  480254b3

FAILURE_BUCKET_ID:  0x7f_8_kmixer!FinalCopyInt32toFloat+2

BUCKET_ID:  0x7f_8_kmixer!FinalCopyInt32toFloat+2

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 00000000 to ab5daf72

STACK_TEXT:  
ac246d50 00000000 89ea38a8 8a004430 89ea3960 kmixer!FinalCopyInt32toFloat+0x2


STACK_COMMAND:  kb

FOLLOWUP_IP:
kmixer!FinalCopyInt32toFloat+2
ab5daf72 55              push    ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  kmixer!FinalCopyInt32toFloat+2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kmixer

IMAGE_NAME:  kmixer.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  480254b3

FAILURE_BUCKET_ID:  0x7f_8_kmixer!FinalCopyInt32toFloat+2

BUCKET_ID:  0x7f_8_kmixer!FinalCopyInt32toFloat+2

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

 

 

 

 

 

2nd crash:

 

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini072513-02.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:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.130503-0418
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jul 25 15:14:39.359 2013 (GMT-4)
System Uptime: 0 days 0:24:27.099
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 804f4d66, ab952d9c, 0}

*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
Probably caused by : aswSP.SYS ( aswSP+9ab2 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804f4d66, The address that the exception occurred at
Arg3: ab952d9c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!IopCompleteRequest+1ce
804f4d66 8b08            mov     ecx,dword ptr [eax]

TRAP_FRAME:  ab952d9c -- (.trap 0xffffffffab952d9c)
ErrCode = 00000000
eax=00000020 ebx=89defe00 ecx=80000005 edx=80000000 esi=00000000 edi=89f1e360
eip=804f4d66 esp=ab952e10 ebp=ab952e58 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!IopCompleteRequest+0x1ce:
804f4d66 8b08            mov     ecx,dword ptr [eax]  ds:0023:00000020=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  firefox.exe

IRP_ADDRESS:  89defe00

DEVICE_OBJECT: 8ae49658

LAST_CONTROL_TRANSFER:  from 804ff89f to 804f4d66

STACK_TEXT:  
ab952e58 804ff89f 89defe40 ab952ea4 ab952e98 nt!IopCompleteRequest+0x1ce
ab952ea8 806e7ef2 00000000 00000000 ab952ec0 nt!KiDeliverApc+0xb3
ab952ea8 806e7ae4 00000000 00000000 ab952ec0 hal!HalpApcInterrupt+0xc6
ab952f30 804fc557 89defe40 89defe00 00000000 hal!KeReleaseQueuedSpinLock+0x3c
ab952f50 804f1860 89defe40 89f1e360 00000000 nt!KeInsertQueueApc+0x6d
ab952f84 806597b8 89defe00 80000005 ab9530e0 nt!IopfCompleteRequest+0x1d8
ab952ff0 b7e356bb e1295440 e1291d90 ab953068 nt!IovCompleteRequest+0x9a
ab953000 b7e5d01a ab9530e0 89defe00 80000005 Ntfs!NtfsCompleteRequest+0xac
ab953010 b7e5cfd2 89defe00 ab953084 8b234c00 Ntfs!NtfsCommonQueryInformation+0x3c0
ab953068 b7e5b49c ab9530e0 89defe00 8ae49658 Ntfs!NtfsCommonQueryInformation+0x34f
ab9530cc b7e5b4d5 ab9530e0 89defe00 00000001 Ntfs!NtfsFsdDispatchSwitch+0x12a
ab9531f0 804ef1f9 8ae49658 89defe00 806e7428 Ntfs!NtfsFsdDispatchWait+0x1c
ab953200 80659128 8ae6d020 89defe00 8b234c18 nt!IopfCallDriver+0x31
ab953224 b7eef09e 89c56000 8ae1e4e8 8ae6d020 nt!IovCallDriver+0xa0
ab953250 804ef1f9 8ae6d020 89defe00 806e7428 fltmgr!FltpDispatch+0x152
ab953260 80659128 8ae1b508 8ad99040 89c56000 nt!IopfCallDriver+0x31
ab953284 b7ed9459 ab9532c0 804ef1f9 8ae1b508 nt!IovCallDriver+0xa0
ab95328c 804ef1f9 8ae1b508 89defe00 806e7428 sr!SrPassThrough+0x31
ab95329c 80659128 00000000 89defe00 89c56008 nt!IopfCallDriver+0x31
ab9532c0 b7eeee9b 8a7d3ee8 89defe00 8fdd2c18 nt!IovCallDriver+0xa0
ab9532e4 b7eef06b ab953304 8a7d3ee8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
ab95331c 804ef1f9 8a7d3ee8 89defe00 806e7428 fltmgr!FltpDispatch+0x11f
ab95332c 80659128 89defe10 89defe00 00000000 nt!IopfCallDriver+0x31
ab953350 8057ddfd 89f1e360 ab953514 e1295440 nt!IovCallDriver+0xa0
ab95337c 805825ce 8a7d3ee8 00000008 00000009 nt!IopGetFileInformation+0xcf
ab9533ec 805826d3 89f1e360 8ae8de00 00000000 nt!IopQueryNameInternal+0x1c4
ab95340c 805c4af1 89f1e360 8ae8de00 ab953500 nt!IopQueryName+0x1b
ab9534dc 805f20f0 89f1e360 ab953500 00000008 nt!ObQueryNameString+0xcd
ab953508 805f21c4 89f1e360 00000038 ab953528 nt!SeInitializeProcessAuditName+0x58
ab953530 805cd838 89c45020 ab95370c ab953750 nt!SeLocateProcessImageName+0x46
ab953734 805417e8 800034f4 0000001b e49e4838 nt!NtQueryInformationProcess+0x85e
ab953734 805009a1 800034f4 0000001b e49e4838 nt!KiSystemServicePostCall
ab9537c0 ad625ab2 800034f4 0000001b e49e4838 nt!ZwQueryInformationProcess+0x11
WARNING: Stack unwind information not available. Following frames may be wrong.
ab95380c ad625b3b 00000000 ab953aac ad627cec aswSP+0x9ab2
ab953818 ad627cec 00000cfc 8065b3d0 8fd98fe8 aswSP+0x9b3b
ab953aac ad64a91d 000003ac 00000cfc 00000001 aswSP+0xbcec
ab953ad0 ad64a9bc 000003ac 00000004 00000cfc aswSP+0x2e91d
ab953b18 805d0505 000003ac 00000cfc 00000001 aswSP+0x2e9bc
ab953c5c 805d1164 1cdfe298 001f03ff 00000000 nt!PspCreateThread+0x3b1
ab953cd4 ad5767b5 1cdfe298 001f03ff 00000000 nt!NtCreateThread+0xfc
ab953d3c 805417e8 1cdfe298 001f03ff 00000000 aswSnx+0x197b5
ab953d3c 7c90e514 1cdfe298 001f03ff 00000000 nt!KiSystemServicePostCall
1cdfe914 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
aswSP+9ab2
ad625ab2 ??              ???

SYMBOL_STACK_INDEX:  21

SYMBOL_NAME:  aswSP+9ab2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  51cc5c1b

FAILURE_BUCKET_ID:  0x8E_aswSP+9ab2

BUCKET_ID:  0x8E_aswSP+9ab2

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

 

 

 

3rd crash. This crash happened after I installed and opened GMER.. some program I found searching for blue screen help on google.

 

 

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini072513-03.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:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.130503-0418
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jul 25 15:34:52.125 2013 (GMT-4)
System Uptime: 0 days 0:19:20.874
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, 48cb5, 1, 0}

Unable to load image uxtdapod.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for uxtdapod.sys
*** ERROR: Module load completed but symbols could not be loaded for uxtdapod.sys
Probably caused by : memory_corruption ( nt!MiDeferredUnlockPages+17c )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000007, A driver has unlocked a page more times than it locked it
Arg2: 00048cb5, page frame number
Arg3: 00000001, current share count
Arg4: 00000000, 0

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


OVERLAPPED_MODULE: Address regions for 'uxtdapod' and 'kmixer.sys' overlap

BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 80522e1b to 804f9fa3

STACK_TEXT:  
aed5bb34 80522e1b 0000004e 00000007 00048cb5 nt!KeBugCheckEx+0x1b
aed5bb54 805068ae 00000000 80564d20 89b13000 nt!MiDecrementReferenceCount+0x33
aed5bb98 80548c46 8055c588 00000000 80564d20 nt!MiDeferredUnlockPages+0x17c
aed5bbc8 8054b49a 89b13000 00000000 00000000 nt!MiFreePoolPages+0xa4
aed5bc08 ad25fedc 89b13000 00000000 03f30064 nt!ExFreePoolWithTag+0x1ba
WARNING: Stack unwind information not available. Following frames may be wrong.
aed5bcf0 ad2560a6 89ea1008 aeb4eb14 03f30118 uxtdapod+0xbedc
aed5bd8c ad2563b6 ad26a640 00000000 89cc9660 uxtdapod+0x20a6
aed5bdac 805cffee ad26a640 00000000 00000000 uxtdapod+0x23b6
aed5bddc 8054620e ad25635e ad26a640 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiDeferredUnlockPages+17c
805068ae 8b55e0          mov     edx,dword ptr [ebp-20h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!MiDeferredUnlockPages+17c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  518306ed

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_7_nt!MiDeferredUnlockPages+17c

BUCKET_ID:  0x4E_7_nt!MiDeferredUnlockPages+17c

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

0: kd> lmvm nt
start    end        module name
804d7000 806e5000   nt       # (pdb symbols)          c:\symbols\ntkrpamp.pdb\6180A5D6F72B4EBB83961913DBDE7C391\ntkrpamp.pdb
    Loaded symbol image file: ntkrpamp.exe
    Mapped memory image file: c:\symbols\ntkrpamp.exe\518306ED20e000\ntkrpamp.exe
    Image path: ntkrpamp.exe
    Image name: ntkrpamp.exe
    Timestamp:        Thu May 02 20:38:05 2013 (518306ED)
    CheckSum:         001FE623
    ImageSize:        0020E000
    File version:     5.1.2600.6387
    Product version:  5.1.2600.6387
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0412.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrpamp.exe
    OriginalFilename: ntkrpamp.exe
    ProductVersion:   5.1.2600.6387
    FileVersion:      5.1.2600.6387 (xpsp_sp3_qfe.130503-0418)
    FileDescription:  NT Kernel & System
    LegalCopyright:   ⓒ Microsoft Corporation. All rights reserved.
 

 

 

 

 

PC is running fine so far after those 3 crashes...
Side Note: I uninstalled my Avast antivirus software after seeing one of its processes in the .dmp file.

 

Any ideas?


Edited by chz123, 25 July 2013 - 07:06 PM.


BC AdBot (Login to Remove)

 


#2 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:09:40 AM

Posted 25 July 2013 - 11:01 PM

Hi

 

As you noticed yourself, Avast is blamed in two dumps. Uninstalling that is the first step and you did it right. I recommend installing Microsoft Security Essentials which is better than Avast and won't cause crash like third party AV programs.

 

http://www.microsoft.com/en-in/download/details.aspx?id=5201

 

Considering the age of your PC, it is good to clean the interior with a can of compressed air . Especially clean the memory slots, CPU cooling fan and graphics card cooling fan fins.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users