BSOD 0x0000003B win32k.sys, ntoskrnl.exe

[hovnik]

hi
I've been having BSOD for months now, at random times, most often when watching videos or listening music. When computer freezes, there's a strange buzzing noise coming from my speakers.

I have allredy updated audio and graphic card drivers and tested ram and hard drive...

 

[Arc]

Hi hovnik.

Those BSODs are caused by avast.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000112aa7, fffff880093ef0b0, 0}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS"]aswSnx.SYS[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS"]aswSnx.SYS[/URL]
[COLOR=Red]Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS"]aswSnx.SYS[/URL][/COLOR] ( aswSnx+2d026 )

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

Description here: Driver Reference Table - aswSnx.SYS

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus (you may keep FLux there if you want).
5. Apply > OK
6. Accept then restart.

Let us know the results.

 

[hovnik]

done that, but still the same error

 

[Arc]

BugCheck 3B, {c0000005, fffff960000e566a, fffff88009624970, 0}

Probably caused by : win32k.sys ( win32k!NtUserQueryWindow+18a )

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

No probable cause.

Does it happen elsewhere other than Poker Stars?

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[hovnik]

today it crashed while watching a movie in VLC player... and it was different code 0x000000c9

 

[Arc]

Stop 0x000000c9 means Verifier Enabled BSOD.

BugCheck C9, {20d, c0, fffffa800927e760, 0}

[COLOR=Red]Probably caused by : ntkrnlmp.exe[/COLOR] ( nt!VerifierBugCheckIfAppropriate+3c )

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

And it is also not pointing to any driver.

So we may consider that the issue is not being caused by any driver. Disable Driver Verifier now.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know about the wattage of your computer.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results.

 

[hovnik]

as I mentioned in the first post I have already tested ram.
Anyway today I let memtest run overnight for over 11h and there were no errors.

Graphic card test: temperature during test was 95°C, and I didn't notice anything special.

PSU has 600W and this site recommends 365W.

CPU test: How long should I run it? I'm running it for 3 hours now, no errors, cpu temperature is 64°C...

No, I'm not overclocking, everything on bios is on default.

speccy screenshot:

 

[Arc]

No driver is failing, no hardware is causing any trouble .... so only one thing remains there, that is the motherboard. Unfortunately we cannot test the motherboard.

Still, before blaming the motherboard, a clean reinstall may be a worthy step.