STOP: 0x0000003b

SYSTEM_SERVICE_EXCEPTION
0x3B SYSTEM_SERVICE_EXCEPTION tritt meistens (aber nicht immer) durch einen fehlerhaften Grafiktreiber auf.
Kühlung!! der Komponenten
Überprüfung mit Afterburner!
Zur Info:laut MSDN:
The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Cause:
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
----------------------
http://www.computerbase.de/forum/showthread.php?t=715519&p=7575054#post7575054
Nein, die Meldung steht nicht grundsätzlich nur für irgendeinen fehlerhaften Grafikkartentreiber.
Da steckt noch einiges mehr hinter z.B. RAM, die "Ansprache" des RAM bzw. auf die Zeilen u. Spalten, etc., z.B. kann auch der Mainboardtreiber dafür verantwortlich sein, etc. und noch einiges mehr.
----------------------
Temperaturprobleme ausschliessen: CPU-Z, speccy, CoreTemp, etc
RAM mit MemTest+86 überprüfen
Aktuellste Treiber aufgespielt?
Aktuellstes DirectX Paket installieren:
http://www.computerbase.de/downloads/system/directx/
(über den WebInstaller - aktuellste Grafikkartentreiber installieren). 
Updates!
Die Festplatte defragmentieren.
Danach die Auslagerungsdatei neu einstellen auf einen festen Wert (z.B. 2048 MB). 
Nachdem "pagefile.sys" gelöscht wurde, ERST defragmentieren und danach die Auslagerungsdatei wieder neu anlegen / einrichten - ansonsten wird auch die "NEUE" nicht in einem Stück angelegt 
=================
http://news.softpedia.com/news/Hotfix-Available-for-Windows-7-quot-0x0000003B-quot-Stop-Error-233045.shtml
Some applications can cause functionality issues in Windows 7, Microsoft revealed, with customers even experiencing crashes, and the less-than-loved Blue Screen of Death (BSOD).
In the case of crashes, users can come across the "0x0000003B" stop error, according to the software giant.
This can happen if they run certain apps on Windows 7 RTM or Windows 7 Service Pack 1 (SP1). The Redmond company also notes that Windows Server 2008 R2 customers can also find that they’re impacted by this problem.
Here is the complete stop error message that users get:
“Stop 0x0000003B (c0000094, fffff8800ff22e54, fffff880098897f0, 0) - SYSTEM_SERVICE_EXCEPTION.”
Microsoft did not offer a list of the applications that can cause the issue described above, but the company did offer one example.
It appears that users running Cyberlink YouCam have come across the glitch, and have had their computers crash.
The software giant not only confirmed the problem, but also offered a few details about the root cause:
“This issue occurs because the D3D9 runtime does not perform parameter validation on the rectangle values that are passed by applications such as YouCam,” Microsoft said.
“Therefore, invalid rectangle coordinates are passed to the Dxgkrnl.sys module. However, the Dxgkrnl.sys module also does not validate the rectangle coordinates, and a "divide by zero" exception occurs.”
KB 2584454 was published last month to help customers access additional details on the issue, as well as a fix.
For the time being, Microsoft Support is only offering a hotfix for download to users running Windows 7 RTM and SP1 as well as Windows Server 2008 R2 RTM and SP1.
The promise from Microsoft is that this particular hotfix will be included in Service Pack 2 for Windows 7. But until Windows 7 SP2 becomes available for download, affected customers can already go ahead and deploy the hotfix.
Windows 7 SP1 RTM and Windows Server 2008 R2 SP1 RTM are available for download here.