SYSTEM_SERVICE_EXCEPTION BLUE SCREEN WINDOWS 7...PLEASE HELP ME!
I'm not too sure what to so here. I initially thought that it was a virus. Did a scan and I had a trojan by the name of HEUR.Trojan.Script.Generic The file was found and removed. I'm still getting the same blue screen. It states the following: A problem has been detected and windows has been shut down to prevent damage to your computer. SYSTEM_SERVICE_EXCEPTION If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these step: Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restartyour computer, press F8 to select Advanced Startup Options, and then select safe mode. Technical Information: *** STOP: 0x0000003B (0x00000000C00001D, 0xFFFFF88000000000, 0xFFFFF88oo81FE160, 0x0000000000000000) Collection data for crash dump... Initializing disk for crash dump... Beginning dump of physical memory. Dumping Physical memory to disk: 60 I tried it in safe mode and I still got the blue screen. The only thing that I can think of is that I was running an Adobe update and the computer froze on me. I had to shut down manually. Some help would be greatly appreciated!!! Tina =)
July 12th, 2010 4:52pm

Use the instructions here to "open the System Recovery Options menu on your computer" or "To open the System Recovery Options menu using the Windows 7 installation disc or a USB flash drive, or a system repair disc." Then perform a system restore to a previous point in time (when the computer worked fine, preferably without virus).
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2010 9:40pm

Hi Tina, Please understand that to solid troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump and analyze the related source code if needed. Unfortunately, debugging is beyond what we can do in the forum. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers. In the meantime, you can refer to the suggestions below to perform some troubleshooting to see if the culprit can be found. Please unplug all unnecessary devices and then perform the steps below: 1. Click Start, type "devmgmt.msc" (without quotation marks) in the Search bar and press Enter. 2. Expand "Sound, video and game controllers". 3. Right click on your sound card and then click "Properties. 4. In the dropdown menu of Device Usage, please choose "Do not use this device (disable)" and click OK. 5. Please use the same method to disable other dubious hardware such as: internal modem, network card and CD-R drive. Please note some devices such as video adapter are not available to be disabled. Also, you can analyze the small memory dump files yourself. For more information about how to do this, please refer to this knowledge base (KB) article: How to read the small memory dump files that Windows creates for debugging. Regards, Linda Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
July 14th, 2010 8:54am

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. Please upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, otherwise you can't upload them) and post a link here, so that we can look at the dumps. André [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2010 3:57pm

Thanks for the replies... I ran eventvwr and found out that I have 2 errors that keep popping up ever since I tried to update my adobe. The two errors are cap12 event 4107 and 0x80041003 event 10 and every once in a while I see a WMI error. Not too sure if this is going to help, but I've been searching for answers online for the past two days. I think it might be my registry, but I can't seem to fix it. I even went into BIOS and did a few scans and nothing. I will look into the above solutions you all gave me. Andre-I'll send you the dumps tonight. Thanks again.
July 14th, 2010 11:12pm

First of all, remove all unnecessary hardware devices from the computer, try entering Windows safe mode to test whether it is a third-party software/hardware compatibility issue. If so, please download and run Windows 7 Upgrade Advisor to check the reason for the issue. If the issue is caused by some incompatible driver, you might go to Device Manager, right click your hardware device in the list and select Update Driver Software; then click Search automatically for updated driver software. Otherwise, you can run the game .exe file as Administrator or directly contact its own support to solve hte problem in timely manner. If you still get the BSOD error after installing the latest driver, please understand that Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services). The system goes to a blue screen because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are). To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
Free Windows Admin Tool Kit Click here and download it now
July 15th, 2010 7:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics