Win7 x64 BSOD SYSTEM_SERVICE_EXCEPTION win32k.sys

kevindd992002 said:

zigzag3143 said:

kevindd992002 said:

Could dwm.exe even be the culprit for this?

Probably not. I did notice that there is a memory exception in the first bug parameter. I would there for recommend you running memtest

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Let us know the results

Ken

From the first day I got this computer, I already ran both Memtest86 and Memtest86+ each with 24 hrs duration and they are completely error-free. So I think there is nothing wrong with my RAM. What could cause that memory exception?

Memory exceptions can be caused by drivers, sloppy code, etc. If you havent try running a system file check first
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Let us know the results from the report at the end.

Then try using driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Ok, I'll try that though it seems to be a long process. I'll report back as soon as I have the necessary results.

Thanks.

cluberti said:

No offense to anyone, but this is a bug in win32k.sys that's existed since at least 2009. I wish you luck in updating your video drivers (they do play into this, so you may avoid it with a different version), but I can tell you I've hit this one myself - exact same callstack and offsets, and MS fixed it in SP1. Just sayin' .

SP1 of what OS? AFAIK, there is still no SP FOR win7 right?

kevindd992002 said:

cluberti said:

No offense to anyone, but this is a bug in win32k.sys that's existed since at least 2009. I wish you luck in updating your video drivers (they do play into this, so you may avoid it with a different version), but I can tell you I've hit this one myself - exact same callstack and offsets, and MS fixed it in SP1. Just sayin' .

SP1 of what OS? AFAIK, there is still no SP FOR win7 right?

Not a legit one.

When is the target release date?