Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: System Service Exeption 0x3B

18 Apr 2012   #11
Brunan

Windows 7 Home Premium 64bit
 
 

Okay, The last MemTest finished about 2 hours ago, Only got on the computer now. It showed up One error. I didn't know how to copy what it said so here is what I took down straight from the screen.

==========
Tst: 3
Pass: 0
Failing Address: 00000100014 - 1.0mb
Good: ffffffff
Bad: fff8ffff
Err-Bits: 00070000
Count: 1
CPU: 0
==========

Writhziden, Are you able to translate this for me please?


My System SpecsSystem Spec
.
18 Apr 2012   #12
writhziden

Windows 7 Home Premium 64 Bit
 
 

It means either the module you tested or the slot you tested is bad. I would recommend testing with the same module that produced the error in the other slot(s). If you do not want to run Memtest86+, just run Windows as you normally would with that module in the other slot. See if Windows is stable or not. Run that way for as long as it normally takes to get a crash. If it crashes, the module is likely bad. Test the other module in each slot by running Windows as long as it normally takes to get a crash. See if the system is then stable with that module. Remember to avoid static damage to your modules and PC.
My System SpecsSystem Spec
18 Apr 2012   #13
Brunan

Windows 7 Home Premium 64bit
 
 

I tested Stick 1 and Stick 2 in Slot 1 and got no errors. Other for today, where I tested Stick 1 in Slot 2, So I take it that Slot 2 is bad?
Also, To get the use of both my sticks again, Can I just use the other 2 slots available on my Motherboard?
My System SpecsSystem Spec
.

18 Apr 2012   #14
writhziden

Windows 7 Home Premium 64 Bit
 
 

If it is a bad slot, then yes, you can use the other two slots. There are no guarantees that it is not a bad module, though. Keep track of which module may be bad. Memtest86+ can throw errors sometimes and not other times for a bad module. It is not an exact science because electronics can be rather finicky. Sometimes, it takes multiple tests to determine a bad module, and sometimes Windows makes a better memory testing tool than any diagnostic because it stresses RAM in more ways than the diagnostics do. That is why I was recommending testing by doing your normal routine in Windows and seeing if the system was stable with different modules in different slots.

You can try the two modules in the other two slots and see if Windows is stable. If it is not, try removing the suspected bad module and running Windows again to see how it responds.
My System SpecsSystem Spec
20 Apr 2012   #15
Brunan

Windows 7 Home Premium 64bit
 
 

Okay, I have moved the 2 Modules to the 2 other slots. Going okay so far, I'm using my computer as I normally would and no crash's.
If I get no crash's by Monday I will mark this as Solved.
Thanks for all the work you've done Writhziden, You have been a massive help to me, I'm extremely grateful
My System SpecsSystem Spec
20 Apr 2012   #16
writhziden

Windows 7 Home Premium 64 Bit
 
 

You're welcome. Glad it has been more stable. Best wishes it remains so!
My System SpecsSystem Spec
21 Apr 2012   #17
Brunan

Windows 7 Home Premium 64bit
 
 

Emm, I think I spoke to soon. I got a Blue Screen today after about 10 minutes of my computer being on. I have attached the Dump File. For some reason, I didn't physically see the Blue Screen, The computer just froze for a second and then restarted all on its own, Is this strange?
My System SpecsSystem Spec
21 Apr 2012   #18
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\Brunan\042112-24429-01\042112-24429-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`0424e000 PsLoadedModuleList = 0xfffff800`04492650
Debug session time: Sat Apr 21 06:50:40.304 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:15.896
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80081b8748, 0, 0}

Probably caused by : hardware

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80081b8748, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031bd6f0 fffff800`0450fca9 : fffffa80`081b8720 fffffa80`06a56b60 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdc10 fffff800`043f0577 : fffffa80`081b8720 fffff800`0446a2b8 fffffa80`06a56b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdc40 fffff800`04357935 : fffff800`044cbac0 00000000`00000001 fffffa80`0797a820 fffffa80`06a56b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdc80 fffff800`042d4361 : fffff880`0111be00 fffff800`04357910 fffffa80`06a56b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdcb0 fffff800`04564fda : 00000000`00000000 fffffa80`06a56b60 00000000`00000080 fffffa80`06a25040 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`042bb9c6 : fffff880`02f64180 fffffa80`06a56b60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd5e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------
Proceed by reading about your crash in Stop 0x124 - what it means and what to try


Also, you may want to try running with just the memory module that did not show any errors. See if it was the module that was causing the errors in Memtest86+ and not the slot.
My System SpecsSystem Spec
24 Apr 2012   #19
Brunan

Windows 7 Home Premium 64bit
 
 

I got yet another BSOD, But it didn't give a Dump. I'm not sure why, But here is everything I took down off the screen

Stop Error: 7E
***dxymmsl.sys - Address FFFFF880045BA1BC base at FFFFF880457C000, Datestamp 4ce799C1
My System SpecsSystem Spec
24 Apr 2012   #20
writhziden

Windows 7 Home Premium 64 Bit
 
 

Was this with the one suspected good RAM module?


The crash points to your graphics card drivers or the hardware itself. Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Quote   Quote: Originally Posted by Dev Center - Hardware > Learn > Debugging > Windows Debugging > Bug Checks (Blue Screens) > Bug Check Code Reference > Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Resolution
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.
  • Make sure you have enough disk space.

  • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

  • Try changing video adapters.

  • Check with your hardware vendor for any BIOS updates.

  • Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.
If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is started with the /DEBUG switch.
If exception code 0x80000002 occurs, the trap frame supplies additional information.
If you do not know the specific cause of the exception, consider the following issues:
  • Hardware incompatibility. Make sure that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about compatibility with Windows 7 at the Windows 7 Compatibility Center.

  • Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you must start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the computer by using the Recovery Console and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.
You can also disable memory caching of the BIOS might to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version.


Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For NVIDIA:
    • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
    • Restart your computer
    • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
    • If any remain of the above, uninstall one at a time
    • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
  6. For AMD:
    • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
    • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
      1. Click Start Menu
      2. Right Click My Computer/Computer
      3. Click Manage
      4. Click Device Manager from the list on the left
      5. Expand Display adapters
      6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
      7. Restart your computer after uninstalling drivers for all display cards
      8. Install the latest driver for the display cards once Windows starts

      Alternatively:
      1. Login as an adminstrative user
      2. Click Start Menu
      3. Click Control Panel
      4. Click Hardware and Sound
      5. Click Device Manager (the last link under Devices and Printers)
      6. Expand Display adapters
      7. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  7. Restart your computer after uninstalling drivers for all display cards
  8. Install the latest driver for the display cards once Windows starts
My System SpecsSystem Spec
Reply

 System Service Exeption 0x3B




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD System Service Exeption
Hello everyone Recently I reinstalled my Windows 8.1. Clean installation and got BSODs from the beginning mainly System Service Exception. Before reinstalling there were BSODs as well but not almost every time I use computer. It occurs even on logon screen. Grab all from SF in attachment.
BSOD Help and Support
BSODs on a new machine, "System Service Exeption"
Hello all, I have a new machine (self assembled), and after two weeks I now experience regular BSODs (System Service Exeption). Most of them have happened while using Cubase, a music software which is somewhat resource intesive. It's the only more resource intesive program I've used regularly so...
BSOD Help and Support
System Service Exception 0x3B c0000005
Hey everybody (and TorrentG, I saw a bunch of threads like this that you replied to...). So, as you can tell, I'm getting a SYSTEM_SERVICE_EXCEPTION 0x3B c0000005 BSOD. I have a custom build, with Win7 x64 Enterprise (from technet). Install at this point is less than a year old. I installed...
BSOD Help and Support
0x3b bsod system service exception
Hello, I alt tabbed from Cs source to close a messenger window when I got the Bsod. I've uploaded the crash dump : Zippyshare.com - 092910-52587-01.dmp My specs are in my member profile. Thank you.
BSOD Help and Support
System Service Exception (0x3b) when starting games from Steam...
Hi all. This is my very first post on these forums. I have tried searching for a solution to my problem, and persistent 'googling' led me to this site. Here is my issue... From the 27/07/10, I have mysteriously started getting this 'SYSTEM SERVICE EXCEPTION' BSOD whenever I attempt to...
BSOD Help and Support
System Service Exeption Probably caused by : afd.sys
Please help me, to find whats causing this. dump file attached. i had these bsods during playing a GTA4 cutscene, and during the completion of mission 3 or 4 in modern warfare 2. dont know if thats the cause though.
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 05:20.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App