Author Topic: Problem with BSOD in aswSP.sys file  (Read 9165 times)

0 Members and 1 Guest are viewing this topic.

Offline titanic4

  • Newbie
  • *
  • Posts: 9
Problem with BSOD in aswSP.sys file
« on: March 12, 2012, 07:15:16 PM »
When I'm trying to run a game( in example GTA IV) with Avast enabled it shows login screen(of Rockstar Social Club, enables MP mode) just fine, but when I log in(or select offline option) when DVD spins up to read data(part of Securom protection) entire OS crashes to BSOD with error code 0x0000008E(0xC0000005, 0x99B6DADC, 0x9A7E97A0,0x00000000) on aswSP.sys file. Oddly enough when i disable all shields before i load up the game it runs just fine. What's the cause of that problem? 
Avast! version: 7.0.1426
« Last Edit: March 12, 2012, 07:20:11 PM by titanic4 »

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11820
    • AVAST Software
Re: Problem with BSOD in aswSP.sys file
« Reply #1 on: March 13, 2012, 12:37:26 AM »
Can you please upload the corresponding minidumps (from C:\Windows\Minidump folder) to ftp://ftp.avast.com/incoming ?
Thanks.

Offline titanic4

  • Newbie
  • *
  • Posts: 9
Re: Problem with BSOD in aswSP.sys file
« Reply #2 on: March 13, 2012, 12:26:49 PM »
I got it fixed. Clearing system events(which got somehow corrupted) in Event viewer has fixed this strange problem.

EDIT: It did fix that problem for short time. Now problem is back. Sadly I cannot find minidumps located in C:\Windows\Minidump. Where is possible to find them anyway?
« Last Edit: March 13, 2012, 06:10:46 PM by titanic4 »

m0unds

  • Guest
Re: Problem with BSOD in aswSP.sys file
« Reply #3 on: March 15, 2012, 05:55:15 PM »
I got it fixed. Clearing system events(which got somehow corrupted) in Event viewer has fixed this strange problem.

EDIT: It did fix that problem for short time. Now problem is back. Sadly I cannot find minidumps located in C:\Windows\Minidump. Where is possible to find them anyway?

it's possible that you might have full memory dumps enabled, which would be  c:\windows\memory.dmp - these are usually large-ish files, but you can compress them w/7-zip or whatever to reduce filesize. if one of those memory dumps exists, just make sure the date stamp corresponds with when you encountered the crash. default behavior is to overwrite each memory.dmp as they're created, so you'll usually only have the one. with minidumps, they'll each have unique names unless the overwrite option is specified

if you don't have a memory.dmp file, what i'd suggest (i'm assuming you're using win7 or vista, should be the same/similar procedure for both)

right click on computer (icon on desktop, or computer entry in start menu) > properties > advanced system settings > "Settings" button under startup and recovery subheader > make sure at least "small memory dump" is selected. you can also enable kernel memory dump if you want to be able to submit full memory dumps (larger, but more detailed) and you can also create a folder somewhere on your system disk to make it easier to find and copy the resultant crash dumps when necessary.

hope this helps.

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 87069
  • No support PMs thanks
Re: Problem with BSOD in aswSP.sys file
« Reply #4 on: March 15, 2012, 06:30:24 PM »
Even if the user has Kernel dump enabled, I believe that still creates a mini dump
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.10.6038 (build 22.10.7633.734) UI 1.0.733/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

m0unds

  • Guest
Re: Problem with BSOD in aswSP.sys file
« Reply #5 on: March 15, 2012, 07:10:56 PM »
it depends on the crash - i've seen it complete both dumps, and sometimes it only completes the full dump before it reboots after a bsod with no minidump being generated. if there's no minidump folder, or nothing in it (as the op indicated) my guess is that neither kernel memory dumps nor minidumps are enabled.

*EDIT* forgot to mention, i'll see if i can replicate the crash w/securom and the sandbox driver, and upload the resultant crash dump if it does crash. i just need to reinstall gta4 as i don't think any of the other titles i have installed are protected by securom.
« Last Edit: March 15, 2012, 07:14:28 PM by m0unds »

Offline titanic4

  • Newbie
  • *
  • Posts: 9
Re: Problem with BSOD in aswSP.sys file
« Reply #6 on: March 16, 2012, 01:22:54 PM »
I own also game named Bioshock, which is also protected by Securom. Video of attempt to run this game: http://www.youtube.com/watch?v=2BIUGca7pzA
You can reproduce this bug with any SecuROM protected game.


m0unds

  • Guest
Re: Problem with BSOD in aswSP.sys file
« Reply #7 on: March 16, 2012, 03:43:55 PM »
I own also game named Bioshock, which is also protected by Securom. Video of attempt to run this game: http://www.youtube.com/watch?v=2BIUGca7pzA
You can reproduce this bug with any SecuROM protected game.

actually, i wasn't able to reproduce it with either GTA4 or Bioshock on my machine - what version of windows are you using? i'm on win7 x64.

did you figure out whether you had memory dumps enabled so you can fwd the relevant ones to the avast team to analyze?

Offline titanic4

  • Newbie
  • *
  • Posts: 9
Re: Problem with BSOD in aswSP.sys file
« Reply #8 on: March 16, 2012, 05:24:02 PM »
I own also game named Bioshock, which is also protected by Securom. Video of attempt to run this game: http://www.youtube.com/watch?v=2BIUGca7pzA
You can reproduce this bug with any SecuROM protected game.

actually, i wasn't able to reproduce it with either GTA4 or Bioshock on my machine - what version of windows are you using? i'm on win7 x64.

did you figure out whether you had memory dumps enabled so you can fwd the relevant ones to the avast team to analyze?
Windows Vista Home Premium 32-bit with SP2

CarlosPT

  • Guest
Re: Problem with BSOD in aswSP.sys file
« Reply #9 on: March 17, 2012, 01:43:41 PM »
Hello fellow avast users and team.

I had to register just to inform that i'm also affected with the same exact problem described in this thread.

There is another SecuROM game that I own and been trying to play it without success because of this bug. A very serious one. The game is Cryostasis and I can also confirm that disabling self defense (which the file refers to) doesn't fix anything.

I would gladly upload my minidumps if someone would be kind to explain me how to do it.

My OS is Windows 7 Ultimate x64 and I can reproduce the crash with that game almost everytime.

Thanks in advance.

Offline titanic4

  • Newbie
  • *
  • Posts: 9
Re: Problem with BSOD in aswSP.sys file
« Reply #10 on: March 21, 2012, 01:45:05 PM »
Hello fellow avast users and team.

I had to register just to inform that i'm also affected with the same exact problem described in this thread.

There is another SecuROM game that I own and been trying to play it without success because of this bug. A very serious one. The game is Cryostasis and I can also confirm that disabling self defense (which the file refers to) doesn't fix anything.

I would gladly upload my minidumps if someone would be kind to explain me how to do it.

My OS is Windows 7 Ultimate x64 and I can reproduce the crash with that game almost everytime.

Thanks in advance.
Can you make video of your attempt to run Cryostasis on your computer(with Avast! v. 7.0.1426 installed)?

Offline titanic4

  • Newbie
  • *
  • Posts: 9
Re: Problem with BSOD in aswSP.sys file
« Reply #11 on: March 22, 2012, 04:54:33 PM »
I have done some checking via elimination and it turns out that behavior shield was causing the problem. It needs fixing.

glOOmyART

  • Guest
Re: Problem with BSOD in aswSP.sys file
« Reply #12 on: March 30, 2012, 01:51:14 PM »
I have done some checking via elimination and it turns out that behavior shield was causing the problem. It needs fixing.

I can confirm that. Games w/o SecuROM run fine (in my case Flight Simulator X and Warzone 2100), games with SecuROM BSOD-crash on load. I also noticed that, after I uninstalled and reinstalled Avast 7, the SecuROM Games worked fine, but as soon as it updated the database, BSOD happened again. But this might be coincidentally...

I disable the behavior shield now when i want to game and enable it when i'm done...

moench3992

  • Guest
Re: Problem with BSOD in aswSP.sys file
« Reply #13 on: April 04, 2012, 11:37:31 AM »
I just registered because I am also experiencing BSOD due to aswSP.sys, when starting SecuRom protected OverlordRaisingHell. But for me after the reboot it strangely works just fine. I am running Win7 Ultimate x64 , Avast program and database are up to date. I also uploaded a minidump named overlordBSOD. So please fix this asap as it is really annonying to start the pc twice to be able to play SecuRom games.

jpearl01

  • Guest
Re: Problem with BSOD in aswSP.sys file
« Reply #14 on: April 15, 2012, 05:47:36 PM »
I also have the same problem, here is the
!analyse -v from windbg

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 80000003, The exception code that was not handled
Arg2: 90bac966, The address that the exception occurred at
Arg3: 8078add0, Trap Frame
Arg4: 00000000

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

*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
aswSP+4966
90bac966 cc              int     3

TRAP_FRAME:  8078add0 -- (.trap 0xffffffff8078add0)
ErrCode = 00000000
eax=8650e258 ebx=00000000 ecx=889b1000 edx=00000002 esi=889b10d0 edi=889b1143
eip=90bac967 esp=8078ae44 ebp=8078ae44 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000202
aswSP+0x4967:
90bac967 56              push    esi
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 830d008c to 830f9f1c

STACK_TEXT: 
8078a944 830d008c 0000008e 80000003 90bac966 nt!KeBugCheckEx+0x1e
8078ad60 83059df6 8078ad7c 00000000 8078add0 nt!KiDispatchException+0x1ac
8078adc8 8305a698 8078ae44 90bac967 badb0d00 nt!CommonDispatchException+0x4a
8078adc8 90bac967 8078ae44 90bac967 badb0d00 nt!KiTrap03+0xb8
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ae44 83093933 00000000 889b10d0 8650e258 aswSP+0x4967
8078ae8c 8ae7d9f9 85828d20 8078aeac 8ae7da17 nt!IopfCompleteRequest+0x128
8078ae98 8ae7da17 889b10d0 00000000 c0000185 storport!RaidCompleteRequestEx+0x1c
8078aeac 8ae8cc2e 889b10d0 c0000185 889b10d0 storport!RaidCompleteRequest+0x12
8078aeec 8ae8ce79 85828d20 8675d008 8583a9d8 storport!RaUnitAsyncError+0x196
8078af20 8ae7e31e 85828d20 8583a994 88831dcc storport!RaidUnitCompleteRequest+0x11f
8078af48 830931b5 8583a994 8583a920 00000000 storport!RaidpAdapterDpcRoutine+0x51
8078afa4 83093018 83145d20 88831d48 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 830927dc 9e587ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 9e587ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
830927dc 00000000 0000001a 00d6850f bb830000 0x9e587ce4


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
aswSP+4966
90bac966 cc              int     3

SYMBOL_NAME:  aswSP+4966

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4f56a5d9

FAILURE_BUCKET_ID:  0x8E_aswSP+4966

BUCKET_ID:  0x8E_aswSP+4966

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

However, I wasn't running a game when it crashed, I had just started up Spyware Doctor to scan my system.  A reboot and I was able to scan with Spyware dr. just fine.  I'm running Windows 7 32bit.  Avast is completely up to date as of 4-15-2012