BSOD 0x0000003b, Win32k.sys, ntoskrnl.exe

[FunsBuns]

Dear Support,

I have been taking random BSOD last 2 months. In many occasions it starts while being in-game for a while, or while browsing in Modzilla at at the same time. I have been trying to solve this issue for some time now. I updated nearly everything, re-installed Windows 7 64 bit 2 times already, memory checks all fine. These problems started after Windows XP was replaced by Windows 7 Home Premium 64 Bit on this console. With Windows XP I had never any problems.

In the first 2 months of this year I had no BSOD at all. It all started halfway March. In the same month NVIDIA released GeForce Driver 335.23. I have still no clue if this Driver was and still is causing it. After a fresh Windows install the PC will run alright for some weeks maybe a month. At one moment I will get BSOD every 2-3 days. Soon it will change to once a day. Then it will be like 1-5 random each day. I have tried nearly everything.

BSOD 0x0000003b, Win32k.sys, ntorkrnl.exe are causing the crashes. Windows Support however offers a dozen of different HOTFIXES for this issue. I do not know which one to take, or if any would work.

I have added the File: ENIGMA-wo_04-06-2014_103437,77.zip as requested.

Cheers,
FunsBuns

 

[Golden]

fffff880`086fa258  fffff880`03e7e5bfUnable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
 aswSnx+0x305bf

Driver Reference Table

WinDBG blames Avast. Uninstall it completely, and replace with MSE.

Love from,
Support

 

[FunsBuns]

Hello Golden,

Thank you very much for the fast reply.

I will try to change Avast to Microsoft Security Essentials as soon as possible on this PC. Although I have one question about this change. In our household we are running 4 PC's with Avast software. How is it possible that only this PC gets the BSOD and not the other 3 PC's, which run exactly the same OS.

Cheers,
FunsBuns

 

[Golden]

How is it possible that only this PC gets the BSOD and not the other 3 PC's, which run exactly the same OS.

Each system, despite having the same OS, is slightly different (e.g. motherboard drivers, video drivers etc. and the way they interact with the OS). These small differences may be enough for Avast to conflict with the system, causing a BSOD.

If the other systems do not BSOD, you should of course leave Avast installed as it is.

 

[FunsBuns]

Hello Golden,

So basically what you are trying to say is that the aswSnx.sys file is causing a conflict with the Win32k.sys OS file. In return this conflict might cause this particular BSOD, despite having the same Avast software and OS on each PC at home.

Since this PC is the oldest I have to remove Avast and give MSE a go. Since I do not see any other solution at this time. I will let you know if I will get any other BSOD after MSE is installed.

Thank you very much for your help.

Cheers,
FunsBuns

 

[Golden]

So basically what you are trying to say is that the aswSnx.sys file is causing a conflict with the Win32k.sys OS file. In return this conflict might cause this particular BSOD, despite having the same Avast software and OS on each PC at home.

Sort of....its not necessarily conflicting with Win32k.sys directly, rather whatever conflict is happening is causing Win32k.sys to crash.

 

[FunsBuns]

System Service Exception returned.

0x0000003b; Win32k.sys and ntoskrnl.exe.

Microsoft Security Essentials installed.

Cheers,
FunsBuns

 

[Golden]

The analysis is inconclusive. Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[FunsBuns]

I've been taking two new types of BSOD in the last 24 hours.

0x0000001a; Memory_Management.
0x000000f7; Driver_Overran_Stack_Buffer; nvstor.sys.

I've been trying to switch out memory dimm's one at a time to see if a dimm slot on the Mainboard is damaged or one of the memory dimm's itself. I've changed Bios memory settings all to Auto; 1.9 volt. I think because of these recent changes with the memory I haven taken these particular two BSOD.

Added ENIGMA-ma_09-06-2014_121535,69.zip.

Cheers,
FunsBuns

 

[FunsBuns]

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

There are not many Drivers for me to select on this PC. Just four of them:

secdrv.sys; Macrovision Corporation.
nvlddmkm.sys; NVIDIA Corp.
nvmf6264.sys; NVIDIA Corp.
nvstor.sys; NVIDIA Corp.

On top of the list are three dump files: dump_diskdump.sys; dump_dumpfve.sys; dump_nvstor.sys.

I turned on Driver Verifier for now. Lets see what will happen.

Cheers,
FunsBuns