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

BLUE SCREEN, (Solved)


  • Please log in to reply

#616
Lexy610

Lexy610

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 743 posts

Good Afternoon //  On Thursday night I walked away from my computer for a couple of hours and when I returned I had the dreaded "blue screen"! :( I did a hard shut down and had not turned it on till today.

 

Today is the first time I was able to turn on my computer because daily life like work and kids prevented me from logging on .. it started up fine but thought i should update you with that.

 

Thank you :)


  • 0

Advertisements


#617
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,047 posts

Gday.

If you have Who Crashed installed, Please run it and post the log.   If not, please download from the link, install and run. > http://www.majorgeek..._edition,1.html


  • 0

#618
Lexy610

Lexy610

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 743 posts

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 4/14/2014 11:49:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041414-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1BC00)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8063CAA0, 0xFFFFFFFFA36B4724, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus
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: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Sat 2/15/2014 6:21:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021514-01.dmp
This was probably caused by the following module: saskutil.sys (SASKUTIL+0xA6E0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF89424020, 0xFFFFFFFF89424194, 0xFFFFFFFF805D22DA)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Program Files\SUPERAntiSpyware\SASKUTIL.SYS
product: SUPERAntiSpyware
company: SUPERAdBlocker.com and SUPERAntiSpyware.com
description: SASKUTIL.SYS
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. This problem might be caused by a thermal issue.
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: saskutil.sys (SASKUTIL.SYS, SUPERAdBlocker.com and SUPERAntiSpyware.com).
Google query: SUPERAdBlocker.com and SUPERAntiSpyware.com CRITICAL_OBJECT_TERMINATION



On Fri 1/24/2014 12:57:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22FA3)
Bugcheck code: 0x77 (0xFFFFFFFFC0000056, 0xFFFFFFFFC0000056, 0x0, 0x9B4E000)
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 that cannot be identified at this time.



On Tue 1/14/2014 5:46:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011414-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 1/13/2014 2:55:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 1/13/2014 2:16:26 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/20/2013 1:45:41 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini111913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/20/2013 1:20:23 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091913-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/19/2013 8:37:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60580)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537580)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/31/2013 2:00:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini013013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x60488)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFE0, 0x2, 0x0, 0xFFFFFFFF80537488)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


 

Conclusion

11 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have 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:

saskutil.sys (SASKUTIL.SYS, SUPERAdBlocker.com and SUPERAntiSpyware.com)
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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is 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.




 


  • 0

#619
Lexy610

Lexy610

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 743 posts

I don't know if anyone has the same issues .. but I ant seem to get to my last page to post .. It wont let me click on page 42 .. it keeps bringing me back to page 1 and the only other options are pages 2 and 3 and I cant click on those either ... :(

 

I'm i the only one having this issues??


  • 0

#620
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,047 posts

There was a glitch with the site, all in the same boat, it is now fixed.

 

A part of SuperantiSpyware (the add blocker bit) is not playing nicely with Avast

Please make sure that Avast is set to it's default setting then update the definition files. Then close, do not perform a scan.

Uninstall SuperantiSpyware, then download and install the latest version, be sure not to install any other offered applications/add ons.  

> then update the definition files for SuperantiSpyware. then.

> Run a Avast Quick scan, then,

> Run a scan with SAS


  • 0

#621
Lexy610

Lexy610

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 743 posts

I dont think I have SuperantiSpyware?? i do have spyblaster.

 

And what do you mean by run avast as "sas"?


  • 0

#622
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,047 posts

If you look at reply #618, second report, > On Sat 2/15/2014 6:21:46 AM GMT. you will see that SuperantiSpyware, (SAS) is listed and that a part of that program, (SUPERAdBlocker.)

is the most likely cause.

Please post some screenshots, showing all you installed programs.


  • 0

#623
Lexy610

Lexy610

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 743 posts

My mistake .. I did have SAS installed .. I uninstalled the old version and installed the newest one with no extras ... however how do I set AVAST to its default setting? .. tried looking in every tab and cant find anything that says "default"


  • 0

#624
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,047 posts

To reset Avast Free Antivirus to its default settings, follow the below procedure:

  • Double-click on the taskbar icon to open Avast.
  • Click on Settings > Troubleshooting.
  • Expand the "Restore factory defaults"
  • Select the features you want to restore:
    • Shield settings
    • Program Settings
z9SumHlw-ava1-s-.png
  • Click on "Reset Now"

  • 0

#625
Lexy610

Lexy610

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 743 posts

Ok .. done! Thanks


  • 0

Advertisements


#626
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,047 posts

OK.   If you do get another crash, please upload a new Who Crashed.


  • 0

#627
Lexy610

Lexy610

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 743 posts

k will do thank you.


  • 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