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 Multiple Errors- HELP


  • Please log in to reply

#1
edeline

edeline

    New Member

  • Member
  • Pip
  • 2 posts
Hello,

I have a Gateway computer with windows XP operating system, I have been getting multiple BSOD's for the last bit, came out of nowhere. I tried following the tutorials and everything posted on here but haven't had much luck since I am have no experience with this. Anyone able to help me out?

http://i54.tinypic.com/33o00hy.jpg[/IMG] (Picture of System deets)

I have the dumpfiles saved but I don't know how to upload them on here.

Edited by edeline, 19 July 2011 - 05:27 PM.

  • 0

Advertisements


#2
Ztruker

Ztruker

    Member 5k

  • Technician
  • 7,065 posts
Download and run WhoCrashed. Post results here. That may give us some info on what is causing the problem. Could be hardware or software.
  • 0

#3
edeline

edeline

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
System Information (local)
--------------------------------------------------------------------------------

computer name: ELEISHA
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Genuine Intel® CPU T1400 @ 1.83GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 1063370752 total
VM: 2147352576, free: 2062172160



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Tue 7/12/2011 11:14:28 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071211-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x77 (0xFFFFFFFFC000000E, 0xFFFFFFFFC000000E, 0x0, 0xFF9000)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 7/12/2011 10:49:00 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x77 (0xFFFFFFFFC00000B5, 0xFFFFFFFFC00000B5, 0x0, 0x39AD000)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 7/12/2011 2:20:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF861A1920, 0xFFFFFFFF861A1A94, 0xFFFFFFFF805C8D78)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 7/11/2011 2:16:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071011-08.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD8FFF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF8D8FFF, 0xFFFFFFFFF5CEEA0C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 7/11/2011 2:07:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071011-07.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x77 (0x1, 0x0, 0x0, 0xFFFFFFFFA652695C)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 7/11/2011 1:44:29 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071011-06.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x77 (0x1, 0x0, 0x0, 0xFFFFFFFFF7999D1C)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 7/11/2011 1:28:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071011-05.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x8CB2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8062EB7B, 0xFFFFFFFFA48AB83C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Mon 7/11/2011 1:13:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071011-04.dmp
This was probably caused by the following module: win32k.sys (win32k+0x86691)
Bugcheck code: 0x10000050 (0xFFFFFFFF8989D4FF, 0x1, 0xFFFFFFFFBF886691, 0x0)
Error: CUSTOM_ERROR
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 this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 7/11/2011 1:10:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071011-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x77 (0x1, 0x4275BE, 0x0, 0xFFFFFFFFA4D53C70)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/10/2011 7:23:05 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071011-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x77 (0x1, 0x0, 0x0, 0xFFFFFFFFF23DEC34)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/10/2011 7:19:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini071011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x77 (0x1, 0x0, 0x0, 0xFFFFFFFFF4847CA0)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/10/2011 1:36:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini070911-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0x86FFF)
Bugcheck code: 0x10000050 (0xFFFFFFFFBEEC54D0, 0x1, 0xFFFFFFFFBF886FFF, 0x0)
Error: CUSTOM_ERROR
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 this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 7/10/2011 1:30:15 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini070911-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x77 (0x1, 0x0, 0x0, 0xFFFFFFFFAA31295C)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



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

13 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

aswsp.sys (avast! self protection module, AVAST Software)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
  • 0

#4
Ztruker

Ztruker

    Member 5k

  • Technician
  • 7,065 posts
The only one that points to anything other than the operating system is this one:

This was probably caused by the following module: aswsp.sys (aswSP+0x8CB2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8062EB7B, 0xFFFFFFFFA48AB83C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System


When did you install Avast Anti-virus?

Try uninstalling it via Control Panel, Add and Remove Programs.
Download and install Microsoft Security Essentials in it's place.

See if the BSODs continue or not.
  • 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