BSOD on 2015.10.2.2215, XP Pro SP3 {Resolved}

[DavidR]

Had a BSOD on win XP Pro SP3.

This happened when I pressed the sleep button on my keyboard - as far as I'm aware there was nothing different from the other times I have used this function, other than using the 2015.10.2.2215 Sp1 beta currently used.

The BSOD error reported Invalid_Process_Detach_Attempt
Stop: 0x00000006 (0x00000000, 0x0, 0x0, 0x0) First time I have ever seen this stop code.

Blue Screen View highlighted 4 .sys files, in order: aswSnx.sys, fltMgr.sys, mbam.sys and ntoskrnl.sys

I have created a 7zip archive with the memory.dmp and a minidump, Mini032215-01.dmp - these are in 7zip archive MemoryDumps_DavidR_2015-3-22.7z no password. File size, 39.6 MB (41,584,227 bytes).

I have uploaded this to the ftp location. Hope this helps.

DavidR

[DavidR]

Update:

Had a response back from pk and the crash is caused by MBAM - he will pass the dumps on to them.

Hopefully they will be as quick to resolve the issue.

[schmidthouse]

That's good info for XP users, thanks David.

[REDACTED]

BSOD IN AVAST 10.2.2215 This bsod happens on deactivation of modules residents of avast free antivirus when disabled from a bsod blue screen on all versions of windows because I tested it on other machines, I can't tell you the error code is when a blue screen and the pc restarts alone there back to normal thing that happens in windows xp is happening even on vista 7 8 8.1 and 10 technical preview I would like the aavast to analyze this If bsod that happened to me

[DavidR]

BSOD IN AVAST 10.2.2215 This bsod happens on deactivation of modules residents of avast free antivirus when disabled from a bsod blue screen on all versions of windows because I tested it on other machines, I can't tell you the error code is when a blue screen and the pc restarts alone there back to normal thing that happens in windows xp is happening even on vista 7 8 8.1 and 10 technical preview I would like the aavast to analyze this If bsod that happened to me

You can change how the system reacts on a BSOD, rather than close down immediately it can push out the BSOD information and leave the blue screen up. That way you can either record the data, the old fashioned way pen and paper ot take an image on your phone or camera.

In order for avast to analyse anything you have to send them the memory dumps created by the BSOD.

EDIT - NOTE: you shouldn't piggy back on a topic that is:
1. not know to be the same as yours.
2. has already marked as Resolved.
3. Finally thsi one isn't down to avast as my update comment states.