BSOD - System Service Exception, 3b

[andys2]

Hello,

I've recently been getting a BSOD about 3x times a day, so, i stuck a new HDD, installed Windows fresh (dual booted with another copy of Windows 7) - updated fully, etc.. and it happens again - the amazingly vague Microsoft messages indicated win32k.sys however, not really sure.

I've attached a memory dump, if anyone could take a look, it would be much appreciated! Can't for the life of me figure why all this is happening all of a sudden.

Thanks!

 

[usasma]

If you've reinstalled Windows and still have errors - it's most likely a hardware or a compatibility problem.
To check compatibility, look up your hardware and software at this link: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

Try these free hardware diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

Please perform the steps from this post to give us additional information: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Next:

You have the 2005 version of ASACPI.sys installed on your system. This is a known cause of BSOD's with Win7.

If your motherboard supports Windows 7, go to ASUSTeK Computer Inc.-Support- and download the latest version of the Asus ATK0110 ACPI Utility (in the Utilities or ATK section).

If your motherboard doesn't support Windows 7, you'll have to choose which of the following to do:
1 - Remove the 2005 version of ASACPI.sys (some people report this as working - but I haven't verified it).
2 - Install a Win7 version of the driver manually - inserting it into C:\Windows\System32\drivers.
-- 64 bit here: http://www.carrona.org/64bitAsacpi.zip
-- 32 bit here: http://www.carrona.org/32bitAsAcpi.zip
If you do, be sure to scan the download with your antivirus BEFORE opening it.
3 - Download the Vista version of the Asus ATK0110 ACPI Utility for your motherboard and attempt to install it using Compatibility Mode (I don't have experience with this either).
4 - Download the Win7 version of the Asus ATK0110 ACPI Utility driver for another motherboard (I have the P6T Deluxe with a Core i7) and attempt to install that (I don't have experience with this either).
64 bit: ASUSTeK Computer Inc.-Support- download_item_mkt
32 bit: ASUSTeK Computer Inc.-Support- download_item_mkt

If your motherboard doesn't support Windows 7, there's no guarantee that any of this will work. But it's worth a try since the alternative is purchasing a new motherboard.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: [url=http://www.carrona.org/dvrref.html]Driver Reference[/url] ).
Please pay particular attention to any dated 2008 or earlier:

ASACPI.sys   Sun Mar 27 22:30:36 2005 - Asus ATK0110 ACPI Utility ([COLOR=red]a known BSOD maker[/COLOR]).  - http://www.carrona.org/dvrref.html#ASACPI.sys
nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver) - http://www.carrona.org/dvrref.html#nvm62x64.sys

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 15:41:30.920 2010 (UTC - 4:00)
System Uptime: 0 days 1:40:37.699
BugCheck 3B, {c0000005, fffff9600028ca45, fffff88006ee5150, 0}
Probably caused by : win32k.sys ( win32k!MulAssociateSharedSurface+15 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[andys2]

Thanks for this information, updated the drivers as you mentioned - i don't believe this is hardware related, did a memory test and it was fine, no errors - it started a few days ago (no hardware changes have been made for a long time) and it did happen again today.

It can be replicated very easily, alt + tab out of Media Center, instant BSOD or, even exit Media Center and there'll be a BSOD when alt + tabbing into the other screen (dual display).

It's Windows 7 64bit, Retail (Ultimate) with all the latest updates - i've uploaded the new BSOD - any help is much appreciated.

Thanks

 

[Jonathan_King]

I see your nVidia network and storage drivers are old. Please update them to the latest version.

nvm62x64.sys Fri Oct 17 17:01:06 2008
nvstor.sys   Wed May 20 02:45:37 2009

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 19:49:42.358 2010 (UTC - 4:00)
System Uptime: 0 days 0:48:16.138
BugCheck 3B, {c0000005, fffff960002234cb, fffff88003689dd0, 0}
Probably caused by : win32k.sys ( win32k!GrePtInSprite+253 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[andys2]

I downloaded the drivers directly from the nVidia website, downloaded their latest nforce update. Not entirely sure that nvm62x64 is then. But, is this really the cause of the problem? It seems networking wise, unrelated, especially since it can be produced phenomenally easily.

 

[Jonathan_King]

I'm thinking of the storage driver in particular, nvstor.sys. A bad hard drive controller driver can cause weird problems such as you are having.

 

[andys2]

Thanks for your help, so far so good!

 

[Jonathan_King]

Great, glad to hear it. I hope it stays that way...

Thanks for the update.

 

[andys2]

Guess I spoke too soon then? Had a few lately - the latest this morning - exact same error. I've attached it - any help will be greatly appreciated, would love to fix this once and for all.

Thanks

 

[ttran]

Please do a system file check:

Open an elevated command prompt and enter sfc /scannow.

Have you done the memtestx86 as USASMA suggested. If you use built in memtest to test your ram as You said, please download memtestx86 as suggested and test your ram

 

[andys2]

Done both and it seems that there are no issues in this case - will be interested to know what the issue is - seems like a mystery.

 

[Jonathan_King]

Please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 30 06:14:42.330 2010 (UTC - 4:00)
System Uptime: 0 days 3:10:06.109
BugCheck 3B, {c0000005, fffff960002534cb, fffff88005cdfdd0, 0}
Probably caused by : win32k.sys ( win32k!GrePtInSprite+253 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[jcgriff2]

Also check RAM and video.

Bugcheck 0x3b (0xc0000005,,,) = system service threw an exception, 0xc0000005 = memory access violation.

Seeing the Win32 subsystem driver win32k.sys listed as probable cause is indicative of a transition occurring from user-mode into kernel code territory. Video is one of the few permitted to do so.

Regards. . .

jcgriff2

.

 

[andys2]

It always seems to happen after watching something in Media Center, switching to the other screen it'll either a) BSOD straight away, as soon as alt + tab is pressed or b) when you click an application it'll BSOD

 

[Jonathan_King]

That does support video card being the cause...

 

[Neptune Mobile]

I have the exact same issue

same problems exactly,k cannot figure it out.

 

[yowanvista]

same problems exactly,k cannot figure it out.

It would be better for you to start a new thread, your issue might be different

 

[Neptune Mobile]

unfortunately

unfortunately it's the exact same issue. word for word. it has to be related to driver related.

 

[usasma]

Neptune Mobile

We're trying to be nice here. Please start your own thread. The issue is not exactly the same because you have a different system from the original poster. Even if it's the identical make and model - all of your drivers won't be the same, nor will the source of your power - and manufacturer's don't always use the same exact hardware in identical systems.

Also, we're helping andys2 here - and it'll get confusing for both of you if we try to help you both in one topic.
Feel free to lurk and see what we suggest to andys2. If you want a response to your problem, then making a new topic is necessary.