Validation of Windows 7 problem after updates.

Nice!

When you can, follow post #55 and let us see the resulting crash dump/s following the Blue Screen of Death (BSOD) Posting Instructions.

It's easy See Option 2. Driver Verifier - Enable and Disable

It is Driver Verifier enabled for sure.

Code:

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

But still it is failing to detect a driver as failing.

Code:

BugCheck E3, {a7353f78, 8ca9b928, 91e50a98, 3}

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

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

No tress of a failing driver in the raw stack, too.

So it is too hard to say at this point thst the issue is originally being caused by a failing/bugging driver.

Plus, memtest86+ also passes nicely.

At this point I would suggest you to run the computer with only one RAM module connected. Remove either of them. See how the computer runs. * As you are using 32 bit windows, 2 GB RAM will not be a very big problem, IMHO.

For any further BSOD, let us see the crash dump. Also see what essenbe suggests.

Lady, don't panic. That's what Driver Verifier is supposed to do, make your computer crash. When it does we hope to catch the offending driver. It didn't work this time though.

After it crashed I disabled Driver Verifier before producing the BSOD. Was that the correct thing to do?

I know this should be in a different thread but think you should know that I think there is something wrong with one of the sound drivers. The reason is that Media Player often refuses to play and shows a white screen followed by "Media Player Not responding". After a couple of minutes it kicks in. Whilst using the verifier in the background I tried to play some music using my Cakewalk Sonar 8.5 Program (Uses Asio4All Driver). It stuttered instead of playing and I had to come out of the program as it was giving me a warning that it was running at b/t 93-97% CPU. It may have just been the verifier that caused it. Closed program and thought I would play my own MP3´s and had the above problem for a couple of minutes before playing. I left it on a playlist and left the PC but I didn´t know anything about the crash until I saw it was stuck, trying to open windows. Only mentioned this in case it is relevant and was going to ask about it after this man problem.



Are you saying I have got to run the verifier again and should I do that with half the RAM available as suggested by Arc or should these tests be separate. Also presuming I can find the RAM! Which one first please.

This is for Arc Quote: (For any further BSOD, let us see the crash dump) What do you mean, please explain as I did not see anything but Windows trying and failing to open as I wasn´t sitting in front of it at the time. If I see another crash dump I will try and get a snapshot. Is that what you mean? Thanks

What you have done with verifier is right. We may suggest you to run it again, but now you try to update the driver to your Creative X-Fi Audio Processor.

Creative Worldwide Support

Does the update solve the audio issue? Let us know.