Blue Screen Error 0x3b SYSTEM_SERVICE_EXCEPTION

Hi,

The main Bug_Check of those are the same BCCode: 3B.

Check this thead for information on using BlueScreenView, MyEventViewer and other methods to
troubleshoot BlueSceens - top 3 replies.

http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

-----------------------------------------------------------------------------------------------------------

Try removing and reseating all cards, memory, and cables (both ends when possible) - actually
remove and replace - do not just snug (on a PC) and clean out the dust bunnies and vents. On
a laptop about all that can be done is reseat the memory and clean the vents.

3b is usually a graphic's driver (display adapter/video driver), other possibilities include
but are not limited to antivirus/antispyware/security programs and even memory (mapping).

BCCode: 3b    0x0000003b

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.


BCCode: 3b    0x0000003b  <-- read this
http://www.faultwire.com/solutions-fatal_error/SYSTEM-SERVICE-EXCEPTION-0x0000003B-*1074.html

============================================================

Vista and Windows 7 love updated drivers so here is how to update the major ones.

References to Vista also apply to Windows 7.

This is my generic how to for proper driver updates : (update video/display driver and BIOS)

This utility makes it easy to see which versions are loaded :

DriverView - Free - utility displays the list of all device drivers currently loaded on your system.
For each driver in the list, additional useful information is displayed: load address of the driver,
description, version, product name, company that created the driver, and more.
http://www.nirsoft.net/utils/driverview.html

For Drivers check System Maker as fallbacks and Device Maker's which are the most current.
Control Panel - Device Manager - Display Adapter - write down the make and complete model
of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate
Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -
Uninstall - REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party
with their own software and drivers and any other major device drivers you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device
Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for
BIOS, Chipset and software updates at System Maker's site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after
each installation.

Always check in Device Manager - Drivers tab to be sure the version you are installing actually
shows up. This is because some drivers rollback before the latest is installed (sound drivers
particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as
needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check
manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

Installing and updating drivers in Windows 7 (updating drivers manually using the methods above
is preferred to ensure the latest drivers from System maker and Device makers are found)
http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

If you update drivers manually then it is a good idea to disable Driver Installations in Windows
Updates, this leaves Windows Updates ON however it will not install drivers which will usually be
older and cause issues. If Updates suggests a new driver then HIDE it (Right Click on it) and then
go look for new ones manually if you wish.

How To Disable Automatic Driver Installation In Windows Vista - Drivers
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx

----------------------------------------------------------------------------------------

Memory tests do not catch all errors such as mismatched memory (possible even for sticks
that appear to be identical) and when faster memory is placed in system behind slower memory.
So it is best to also swap sticks in and out to check for those even if all memory tests fail to show
a problem.

To test RAM check here - let it run 4+ hours or so.
www.memtest.org

For the Windows Memory Diagnostic Tool.

Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click -
RUN AS ADMIN follow the instructions

Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic
Tool
http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

How to Run the Memory Diagnostics Tool in Windows 7
http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool
http://www.howtogeek.com/howto/windows-vista/test-your-computers-memory-using-windows-vista-memory-diagnostic-tool/

Hope this helps.

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION -This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

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.

Please update the ATI drivers.

You also have a fatal hardware error caused by a timer issue of your CPU:

Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR- This bug check indicates that a fatal hardware error has occurre

Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/29/2010 18:18:16
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007281978
Section       @ fffffa8007281a50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000106a5
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80072819c0
Section       @ fffffa8007281b10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : a5 06 01 00 00 08 10 02 - bd e3 98 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8007281b10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007281a08
Section       @ fffffa8007281b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 2 Bank 5)
  Status      : 0xfe00000000800400
  Address     : 0x0000380002c1d7ee
  Misc.       : 0x0000000000007fff

Bah, happened again after updating driver (although no reboot was forced, so I hadn't rebooted), but different BugCheck string.

092510-25968-01.dmp

9/25/2010 10:52:37 PM

IRQL_NOT_LESS_OR_EQUAL

0x0000000a

ffffffff`fffffffa

00000000`00000002

00000000`00000000

fffff800`02cb85ae

ntoskrnl.exe

ntoskrnl.exe+70740

NT Kernel & System

Microsoft® Windows® Operating System

Microsoft Corporation

6.1.7600.16617 (win7_gdr.100618-1621)

x64

C:\Windows\Minidump\092510-25968-01.dmp

8

15

7600

Minidump here

I guess next I'll try reseating components and cleaning for dust. Then looking for other device drivers, maybe.

The past several times I've used the machine, it's happened just about every time, and it hadn't before that, so either some automatic update got me or some hardware just started failing. This time I was in Picasa when it occurred, although there could have been any number of other things going on in the background.

Hi,

The reseat absolutely needs to be done because the cleaning probably blew dirt into sensitive
contacts and/or loosened something - reseat cards, memory, and cables.

===========================================================

Check these KB's

Error message on a blue screen on a computer that is running Windows 7 or Windows Server
2008 R2: "STOP: 0x0000000A"
http://support.microsoft.com/kb/979444

Stop error message on a computer that is running Windows 7 or Windows Server 2008 R2 and
that has iSCSI storage: "0x0000000A"
http://support.microsoft.com/kb/979711

=========================


References to Vista also apply to Windows 7.

Drivers could be at fault however disk issues or antivirus/antispyware/security products are
just as likely to be the root cause as they can force a driver to corrupt or go out of bounds.
The video driver or something affecting it would be very suspect.

Below I will post a generic bluescreen troubleshooter and in the next message how to update
drivers and BIOS as well as do memory checks.

-----------------------------------

BCCode: 0A     0x0000000A

Cause

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Resolving the Problem

If a kernel debugger is available, obtain a stack trace.

To resolve an error caused by a faulty device driver, system service, or BIOS

1. Restart your computer.
2. Press F8 at the character-based menu that displays the operating system choices.
3. Select the Last Known Good Configuration option from the WindowsAdvanced Options menu. This option is most effective when only one driver or service is added at a time.

To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

1. Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
2. Try disabling memory caching of the BIOS.
3. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
4. Make sure the latest Service Pack is installed.
5. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
6. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.

If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.

Comments

Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.

BCCode: 0A     0x0000000A  <-- read this
http://www.faultwire.com/solutions-fatal_error/IRQL-NOT-LESS-OR-EQUAL-0x0000000A-*1025.html

------------------------------------------------------------------------------------------------------------------

Refer to the troubleshooter in the first reply.

Hope this helps.

Happened again. Minidump here .

100110-15406-01.dmp  

10/1/2010 12:36:23 AM   

DRIVER_IRQL_NOT_LESS_OR_EQUAL   

0x000000d1   

ffff844b`fdc38e24   

00000000`00000002   

00000000`00000000   

ffff844b`fdc38e24   

ntoskrnl.exe   

ntoskrnl.exe+70740   

NT Kernel & System   

Microsoft® Windows® Operating System   

Microsoft Corporation   

6.1.7600.16617 (win7_gdr.100618-1621)   

x64       

C:\Windows\Minidump\100110-15406-01.dmp   

8   

15   

7600   

Hi,

You haven't told us what troubleshooting actions you have taken?

Have you tried removing all power and reseating the cards, memory, and cables
as indicated above? Updated the BIOS, low level chipset drivers, and other major
drivers?

-----------------------------------------------------------------------------------------

If there are RAID drivers they are very suspect and/or driver problems are very real prospects. 
Other major possibilities are Video and other drivers. See the driver section in my generic
bluescreen troubleshooting methods below. BIOS, low level chipset drivers, memory and
antivirus/antispyway/security programs can also cause this. 

----------------------------------------------------------------------------------------------------------

BCCode: D1     0x000000D1

Cause

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper addresses.

If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:

• The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
• The function call was made to a function in another driver, and that driver was unloaded.
• The function was called by using a function pointer that was an invalid pointer.

BCCode: d1   0x000000d1  <-- read this
http://www.faultwire.com/solutions-fatal_error/DRIVER-IRQL-NOT-LESS-OR-EQUAL-0x000000D1-*1210.html?order=votes

Hope this helps.

Happened again. Minidump here .

X64_0xD1_CODE_AV_BAD_IP _atikmdag +311c2b

You have a Bad instruction pointer [1]. So check your CPU/RAM for stability issues.

[1] http://en.wikipedia.org/wiki/Instruction_pointer

Hi,

You haven't told us what troubleshooting actions you have taken?

Have you tried removing all power and reseating the cards, memory, and cables as indicated above? Updated the BIOS, low level chipset drivers, and other major drivers?

If there are RAID drivers they are very suspect and/or driver problems are very real prospects. 
Other major possibilities are Video and other drivers. See the driver section in my generic bluescreen troubleshooting methods below. BIOS, low level chipset drivers, memory and antivirus/antispyway/security programs can also cause this. 

I have replaced the video driver and uninstalled the AV (Avast), both 2 or more BSODs ago. Windows Defender is installed, but Realtime Protection disabled. I am running RAID 0. I intend to look for BIOS & other driver updates and to re-seat/clean the interior (although the machine is only 9 months old).

Most recently I uninstalled the AT&T VPN client I use to connect to work (this is a personal machine) since I'd heard about some problems people had with it on Win7 in the past, it's pretty low-level software, it updates itself pretty regularly, and the problem only started in the past couple of months.

Also, this particular crash happened basically on startup. I had powered on and left the machine at the login screen. When I finally switched my USB-based monitor/mouse/keyboard switcher back to the machine and logged in, the crash occurred after a few seconds of the normal "waiting" cursor before the desktop appeared.

At least one of the previous crashes occurred when resuming from Suspend, although others were just during running different applications.

FWIW