Win32k.sys and ntoskrnl.exe 0x3b BSOD

[Burnsy]

Ok I just received another bluescreen 0x50 page fault in non paged area, I was also getting this one prior to my fresh install of windows. Unfortunately I forgot to enable driver verifier today but hopefully this dmp helps. Also is defective RAM still a possible cause or is it most likely a driver issue?

 

[Thedoctor44]

You are still getting the same bugcheck, I think ruling out faulty RAM is our next step.

Follow these instructions and run Memtest86 for at least 8 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[Burnsy]

Ok I have completed a 12 pass memtest with no errors

 

[Thedoctor44]

Well that rules out RAM, are there any more new dump files?

 

[Burnsy]

This one is from the 23 so I dont know if it is relevant, if not I will wait to get another one the send those

 

[Burnsy]

Right just got this one there, dont know if it matters but I got this when exiting Trials Fusion but as I said they are very random so it might just be a coincidence. Also could it possibly be chrome because every time I bluescreen chrome is open but again might just be a coincidence or the fact that chrome is always open anyway.

 

[Thedoctor44]

The blue screen you have is 0x3B which is a System Service Exception. The driver getting the blame is win32k.sys which I believe is the Windowing graphics driver by microsoft.
Now this isn't the cause but 0x3B bugchecks are caused a lot by 3rd party graphics drivers so I recommend updating or rolling back your AMD driver.

You can follow these instructions if it helps.

How-To Install AMD Catalyst? Drivers For A Windows® Based System

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff9600025c43e, fffff880086eee20, 0}

Probably caused by : [COLOR="Red"]win32k.sys[/COLOR] ( win32k!MulDeleteDeviceOrRedirectionBitmap+1a )

Followup: MachineOwner

fffff880`102e2000 fffff880`10fd2000   atikmdag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="SeaGreen"]Fri Dec 06 21:19:43 2013[/COLOR] (52A23F6F)
    CheckSum:         00CA856E
    ImageSize:        00CF0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Burnsy]

I have the latest stable driver "13.12" and I dont think I should try a BETA driver as those may be unstable. My friend has a similar card with 13.12 and is going fine, however if you insist that I try a Beta driver then I will because you are the expert not me

 

[Thedoctor44]

I'm no expert and I won't preach to you claiming I am.

Anyway, I don't recommend BETA drivers especially when you are having bugchecks.
Recently we are having issues with the 13.12 AMD drivers, can you roll back to 13.9 I believe it is.

I've never had an AMD card so I don't know the drivers particularly well.

 

[Burnsy]

If I rollback it takes me to standard VGA. Do you know of a way to get the 13.1 drivers?

 

[Thedoctor44]

That shouldn't happen...

Unfortunately no because I've never used AMD products so I can't say I'm familiar with their drivers.

Does it not work via device manager?

 

[Burnsy]

Found it on the website just downloading now and I will install, I will return with further details of bluescreens and keep this thread updated in case any one has the same problem.

 

[Thedoctor44]

Ok, let us know.

 

[Burnsy]

Ok downgrading my graphics drivers to 13.9 did not work, I just received this while playing another game

 

[Thedoctor44]

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.

 

[Burnsy]

Are you sure it may be a driver because the lag I get in games and browsing the internet is pretty annoying to deal with and it may even take a week for my next bluescreen :\ I had another bluescreen but I dont know if you want the files for it as it will probably just show the same stuff as I wasnt running Driver Verifier at the time.

 

[Thedoctor44]

Just upload it anyway, lets see if anything else comes up.

 

[Burnsy]

Here ya go,

 

[Thedoctor44]

Stress test your graphics card with Furmark

I recommend running it for around 30 minutes

   Warning

Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures

 

[Burnsy]

So I should disable driver verifier?