Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD


  • Please log in to reply

#1
kingciph

kingciph

    New Member

  • Member
  • Pip
  • 2 posts
My cpu keeps crashing.
Ran Who Crashed and got this report:



--------------------------------------------------------------------------------
Welcome to WhoCrashed Home Edition 2.10
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.

This program does post-mortem crash dump analysis with the single click of a button.


To obtain technical support visit www.resplendence.com/support

To check if a newer version of this program is available, click here.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.


--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Tue 10/19/2010 4:39:38 PM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x8055A721, 0xF3058B34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101910-05.dmp



On Tue 10/19/2010 4:07:38 PM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x8055A76A, 0xF354AB40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101910-04.dmp



On Tue 10/19/2010 4:04:49 PM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0xFFFFFFFE, 0x1, 0x8055A774, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101910-03.dmp



On Tue 10/19/2010 1:12:53 PM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x10000050 (0xB0629EA8, 0x1, 0x8055A777, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101910-02.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Tue 10/19/2010 9:53:23 AM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x10000050 (0xB062CD2E, 0x1, 0x8055A777, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101910-01.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Mon 10/18/2010 4:26:49 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x8055A76A, 0xF36B3B34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101810-01.dmp



On Sun 10/17/2010 6:09:24 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8055A78A, 0xF3CF6B30, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101710-04.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 10/17/2010 5:52:55 PM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8055A77A, 0xF420CB3C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101710-03.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Sun 10/17/2010 4:07:43 PM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x1000008E (0xC000001D, 0x8055A751, 0xF1EFAB40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101710-02.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Sun 10/17/2010 5:45:24 AM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x10000050 (0xA062DA1E, 0x1, 0x8055A777, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101710-01.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Sat 10/16/2010 12:04:36 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x8055A76A, 0xF2C19B40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101610-04.dmp



On Sat 10/16/2010 6:52:38 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xA8632832, 0x1, 0x8055A727, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101610-03.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 10/16/2010 6:46:37 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xFFFFFF1E, 0x1, 0x8055A72F, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101610-02.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 10/16/2010 6:38:29 AM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x10000050 (0xFFDF81C7, 0x1, 0x8055A773, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101610-01.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Fri 10/15/2010 9:09:27 AM your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0xB86046AA, 0x1, 0x8055A777, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101510-02.dmp



On Fri 10/15/2010 4:05:11 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8055A774, 0xF2AE1B34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101510-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 10/13/2010 11:35:33 PM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x10000050 (0xB0B87193, 0x0, 0x8055A777, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101310-01.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Tue 10/12/2010 3:43:18 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x10000050 (0x886046C7, 0x1, 0x8055A787, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101210-03.dmp
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 10/12/2010 3:45:12 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0x80000004, 0x8055A77B, 0xF3EA1B30, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101210-02.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 10/12/2010 1:51:40 PM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x10000050 (0xFFFFF0C7, 0x0, 0x8055A777, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini101210-01.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Sun 10/10/2010 5:22:59 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC000001D, 0x804EBB40, 0xF39A6B84, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101010-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 10/9/2010 3:20:57 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0x886046C7, 0x1, 0x8055A787, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini100910-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 10/7/2010 10:40:08 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x10000050 (0xB06306DE, 0x1, 0x8055A77F, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini100710-01.dmp
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 10/6/2010 9:24:19 PM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x10000050 (0xB062A5CC, 0x1, 0x8055A787, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini100610-02.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Wed 10/6/2010 6:10:24 PM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x10000050 (0xA8629C1A, 0x1, 0x8055A77F, 0x0)
Error: Unknown
Dump file: C:\WINDOWS\Minidump\Mini100610-01.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Mon 9/13/2010 7:50:41 PM your computer crashed
This was likely caused by the following module: aswsp.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8055A775, 0xF37A5B40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini091310-01.dmp
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module



On Mon 6/21/2010 6:07:37 PM your computer crashed
This was likely caused by the following module: watchdog.sys
Bugcheck code: 0x100000EA (0x82BA13D8, 0x83170BA0, 0xF8D55CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
Dump file: C:\WINDOWS\Minidump\Mini062110-01.dmp
file path: C:\WINDOWS\system32\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini101410-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

28 crash dumps have been found on your computer. Only 27 could be analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

What do I do?
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello kingciph.... Welcome to
GeeksToGo, :D
;) ;)

I'm sorry to hear about your issue. We will try to help you resolve this as soon
as possible.
  • Please understand we are all volunteers and we are not here all the time.
  • Sometimes it may be a extended amount of time to get back to you. If it has been
    more then 3 days please shoot me a PM and I will try to get back to you quickly
    then.
  • Please do the following and supply the requested information as needed. If you
    don't understand my instructions please ask and I will try to explain them
    clearer for you.
  • Do not attempt any steps unless instructed or ask before to
    make sure they will not cause any further issues.



Part of your issue is Avast but I believe the main issue is your OS itself. Please do the following.
Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem
  • 0

#3
kingciph

kingciph

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
Thank you!! :D
I will try this tonight. As it may take quite awhile, I need to wait until I finish working.
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
No problem. When you reply I'll get a email notifying me.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP