BSOD 03b system service exception win32k.sys

[morik]

I've had this crash twice in the past couple weeks. At least, the first one was 03b--not sure if it was win32k.sys, or a system service exception.

I keep my computer on 24x7. I have installed the latest updates from MS.

The first time I was playing Diablo 3. The screen went black and then came back several times over an hour or so. I believe I had quit out of the game entirely, and was maybe opening Chrome, when I got the crash.

The second time a video I was watching with VLC media player just finished, and full screen was going back to windowed mode.


I realize the screen going black most likely indicates a problem with the video card or driver, but it is possible that is a separate issue--I also use the HDMI output on my video card to watch movies and listen to music on my home theater system, and I often see the picture go out and come back there, as well. However, it is only recently that I've seen it happen on my main monitor.

I am overclocking almost all my components, but have had this overclock work stably for 2 years or so now. (Core i7 920 overclocked to 3.9 GHz, video cards (2 GTX 460 1GB cards) overclocked as well, but not terribly much.) The system is stable in all games that I've played, and in various stress tests. I've run memory tests at various points with no errors found, though not recently.

I did recently install beta drivers for my video card as recommended for playing guild was 2, as the latest release drivers aren't working properly with it.

I also installed AVG somewhat recently, to augment Microsoft Security Essentials.

Dumps from both crashes attached.

 

[Arc]

Welcome aboard, morik!

We need some more information. You post it again, following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html .

 

[morik]

Sorry about that--the SF debug zip file is now attatched to the OP. It includes a couple crashes from June--I don't recall the details of them though. Haven't had any issues between then and now.

Thanks!

 

[morik]

Bump?

 

[Arc]

Have you got any more crashes after 17th?

The last two dumps show bugchech 3B, with a cause ntkrnlmp.exe, which is not the actual cause. It causes for System service, Device driver, graphics driver, and memory.

In such a situation, it is better to 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.

Let us know the results, with the subsequent crash dumps, if any.

 

[morik]

I just got around to this today--I turned on driver verifier, rebooted, and left prior to fully booting up.
When I came back a couple hours later, I had a BSOD indicating a driver which was being verified failed verification.

Crash file in OP updated to include this crash as well.

Thanks!

 

[Arc]

It is MagicISO SCSI Host Controller driver it is crashing your system.

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {24c, fffff88005083840, fffff980049eaee0, 103}

Unable to load image \SystemRoot\system32\DRIVERS\mcdbus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR=Red][B]Probably caused by : mcdbus.sys [/B][/COLOR]( mcdbus+1d840 )

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

You need to get rid of that thing. Uninstall MagicISO, and report back.

And, dont forget to disable Driver Verifier for now. If it is needed if future, we will suggest it again.

 

[morik]

Hmm that is unfortunate as I use MagicDisc upon occasion.

I happened to have 4 virtual drives active as I forgot to disable them after I was finished using them, but had no drives active at the time of the crashes.

I'll disable the drives and activate the verifier again to see if anything else shakes out.

 

[morik]

After disabling the virtual drives, I ran driver verifier for 24 hours with no issues. Played games, watched videos, normal usage.

 

[Arc]

In this post, I suggested you to disable Driver Verifier.

Disable it now. Let us know how it is working in normal situation.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[morik]

I had another BSOD, this time 001A, memory management.

Chrome had been acting funny for a little while (a couple hours)--sometimes when I opened a new tab and went to a website, the page would stop responding to scrolling (either by grabbing the scrollbar with the mouse, or using the mousewheel). I could still click links within the page, but if I went to another tab and came back, the page wouldn't repaint (it would display whatever was on the tab I had just swapped from).

Refreshing the page a couple times, or reloading it in a new tab (sometimes several times) would fix the issue.

The crash came after chrome had been doing this, and then I closed chrome.

OP updated with new crash dump.

 

[Arc]

Morik you need to enable driver verifier one more time.

 

[morik]

Prior to re-enabling driver verifier I started having some MASSIVE issues with game video--huge sections of the screen would turn black (leaving maybe 20% of the screen rendering normally).

I enabled driver verifier and rebooted, and could launch games fine, but there was green pixelation and flickering over the entire screen (looks like if you just slightly pull out your monitor cable).

No BSOD at this time though.

I verified all cable connections, and tried disabling SLI.
With SLI disabled, I tried launching a game with each graphics card running the monitor, one after the other.

Neither displayed the artifacts/flickering. I enabled SLI and tried again with each graphics card, both displayed the flickering.


I reseated both graphics cards in their PCI-E slots, swapping primary & secondary cards (just for kicks).

With SLI still enabled, I rebooted, and though the computer finished booting, it did not get past the startup screen. (I got the bootup musical bit, but the screen was stuck displaying the startup screen). Swapping to the second graphics card showed my normal desktop--swapping back to the main graphics card (swapping cable, that is) did not display anything.

I did something or other and rebooted--got a couple BSODs in a row (trying to reboot several times). Those are in the OP's attachment now.

I swapped the video cards back, booted to safe mode, disabled verifier, and rebooted. (SLI still enabled)
Got a 1600x1200 display instead of my normal 2560x1600, and no nvidia control center in context menu--the driver didn't detect a compatible device.

Swapping the cable to my other card fixed it.

Disabled SLI and rebooted again--both cards work fine.

I then replaced the SLI cable with a different SLI cable, and so far everything works fine. No flickers in games (with SLI on), etc.


So, my guess is that the SLI cable had something wrong with it, though I was also suspicious that maybe my primary PCI-E slot had some issue.


Anyway, will re-enable verifier and see what happens, but I am interested in what happened with those BSODs, if someone wants to take a look at the latest ones.

Thanks!


EDIT: Upon enabling verifier & rebooting, got an immediate BSOD while windows was starting. OP updated again. (The crash from 9:30 PM today, the other 2 from today are from prior to swapping the PCI cable... not sure why one is labeled 3PM, as I didn't have any crashes until 8:45 or so, when I had 2 in a row)

Disabled verifier and everything seems fine (I know it isn't, but is much better than with the other SLI cable--no symptoms currently, other than failing verifier).

 

[morik]

I took a look at my latest dump file and it appears that this is the culprit:
nvoclk64;NVIDIA Enthusiasts Platform KDM

Also, I have started seeing artifacts again while playing some video games--entire sections of the screen going weird and black.

I'm getting rid of the beta drivers supposedly needed for Guild Wars 2, and installing release drivers. I'll see how that works.

 

[Arc]

If you think, you may upload those crash dumps.

 

[morik]

I was talking about the latest dump I posted.

I installed normal NVIDIA drivers, no help.
Turns out nvoclk64 is from the performance/system utilities module--I uninstalled it as I have no need for it (I use MSI afterburner).

Will see how that works.

 

[morik]

Have been running driver verifier for over 24 hours now, and no crashes.

I'll disable again and see how things go.

 

[Arc]

I was talking about the latest dump I posted.

I installed normal NVIDIA drivers, no help.
Turns out nvoclk64 is from the performance/system utilities module--I uninstalled it as I have no need for it (I use MSI afterburner).

Will see how that works.

Run it. Set everything at default, uninstall it.

At least 80% of your BSOD problems will be over.