BSOD : SYSTEM_SERVICE_EXCEPTION ; hardware related?

Hi! Have been getting BSOD for about a month now and been trying to fix it myself but I really don't know what the problem is. I believe it is hardware related either to the motherboard or processor but can't really confirm that either is faulty. It started after I installed a SSD so I thought that was the problem for awhile and based my troubleshooting on it being faulty. However I don't think it's the issue anymore because I've tried doing fresh installs without it on a HDD and reverted my BIOS to default settings and still have BSOD problems. I did get the crashing to stop after I completely disassembled my system and put it back together, reapplying themal paste to the processor. This made the crashing stop for about a week. My temps for the processor don't seem to be dangerously high though. Less than 60C. My video card gets a bit hot but says below 70C. But I have tried using a different video card too so I think that it's not the problem.

edit : Crashes usually happen under load (gaming) but happens while idle as well.

I will just make a list of the things I've tried. I've probably done some other things too trying to Google and find out a solution. Can't remember everything I've tried.

- Multiple fresh installs of Windows 7 and Vista on a SSD and HDD.
- Tried Memtest86+ for a total of ~20 passes and hours
- Tried using a different video card with fresh install
- Updated BIOS for motherboard and firmware for SSD

If there is any information I've forgotten that I should post please let me know. Any help that can be provided will be greatly appreciated. Thank you!

Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

We need to try & find what the driver is crashing your system.

Please read carefully re Driver Verifier .

Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks for replying! I got the Asacpi.sys driver from the ASUS website. Not from the links you gave but the one for my motherboard. From here...

ASUS - Motherboards- ASUS M3A78-EM

The driver I had was an old one from 2005. Have one from 2009 now. Also did the driver verifier thing. Will post again if it crashes. Where is the memory dump file located?

Coco hime said:

Thanks for replying! I got the Asacpi.sys driver from the ASUS website. Not from the links you gave but the one for my motherboard. From here...

ASUS - Motherboards- ASUS M3A78-EM

The driver I had was an old one from 2005. Have one from 2009 now. Also did the driver verifier thing. Will post again if it crashes. Where is the memory dump file located?

Good Job


To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Ok here is the minidump.zip

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Coco hime\Minidump\032912-12402-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c8e650
Debug session time: Thu Mar 29 11:05:00.305 2012 (UTC - 6:00)
System Uptime: 4 days 20:12:32.292
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002dc0e7b, fffff88009ad6e80, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+9b )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002dc0e7b, Address of the instruction which caused the bugcheck
Arg3: fffff88009ad6e80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObpLookupDirectoryEntry+9b
fffff800`02dc0e7b 0fb717          movzx   edx,word ptr [rdi]

CONTEXT:  fffff88009ad6e80 -- (.cxr 0xfffff88009ad6e80)
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8a0017853d0
rdx=fffff88009ad7950 rsi=0000000000000000 rdi=fff7f8a006f3a6e8
rip=fffff80002dc0e7b rsp=fffff88009ad7860 rbp=fffffa8005499cc8
 r8=0000000000000040  r9=0000000000000001 r10=fffff8a0017853d0
r11=0000000000000002 r12=fffff88009ad7950 r13=fffff8a0017853d0
r14=0000000000000040 r15=fffff8a0017853d0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ObpLookupDirectoryEntry+0x9b:
fffff800`02dc0e7b 0fb717          movzx   edx,word ptr [rdi] ds:002b:fff7f8a0`06f3a6e8=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  UpdateTask.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dc0479 to fffff80002dc0e7b

STACK_TEXT:  
fffff880`09ad7860 fffff800`02dc0479 : fffffa80`05499cc8 fffff880`09ad7950 fffff8a0`0896b301 fffffa80`00000001 : nt!ObpLookupDirectoryEntry+0x9b
fffff880`09ad78c0 fffff800`02dc1796 : 00000000`00000000 fffffa80`05499b10 fffff880`09ad79d0 fffffa80`04407080 : nt!ObpLookupObjectName+0x489
fffff880`09ad79b0 fffff800`02dc309c : 00000000`00000000 00000000`00000000 00000000`00000001 fffff8a0`06f3a6e0 : nt!ObOpenObjectByName+0x306
fffff880`09ad7a80 fffff800`02dae8c4 : 00000000`002ae0d8 00000000`00100021 00000000`002ae930 00000000`002ae078 : nt!IopCreateFile+0x2bc
fffff880`09ad7b20 fffff800`02ac5fd3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtOpenFile+0x58
fffff880`09ad7bb0 00000000`7761164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`002ae038 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7761164a


FOLLOWUP_IP: 
nt!ObpLookupDirectoryEntry+9b
fffff800`02dc0e7b 0fb717          movzx   edx,word ptr [rdi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObpLookupDirectoryEntry+9b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

STACK_COMMAND:  .cxr 0xfffff88009ad6e80 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpLookupDirectoryEntry+9b

BUCKET_ID:  X64_0x3B_nt!ObpLookupDirectoryEntry+9b

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

Still the same crash... Possible causes are Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...

Check for corrupted files:

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

Hardware checks:

• If you are overclocking any hardware, please stop.
  
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest

Underlying driver check:

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 204943
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

Heya! [: Thanks for the suggestions on things to try. Here is what I found from trying them...

Disk Check - Windows has checked the file system and found no problems : I only ran this on the SSD that has the OS on it. Haven't had a chance to run on the storage HDDs.

SFC /SCANNOW - no integrity violations

Overclocking - I'm not overclocking anything on my system

FurMark - Video card temps hit 90C max. Never crashed when running. Looking at other users temps this seems to be in line with what they get under heavy load.

Video Memory Stress Test - It said it wasn't compatible with my card so only ran 2 passes. No errors.

Prime95 - This caused a crash every time I ran it. Only tried the first 2 tests but did them multiple times. CPU temps hit 56C max. AMD's site has max temps listed as 55-63C.

IntelBurnTest - Didn't try this because Prime95 was causing crashes.


I got some different BSOD errors than the SYSTEM_SERVICE_EXCEPTION I was getting before from running Prime95. I did get one DRIVER_VERIFIER_IOMANAGER_VIOLATION error that I think was maybe caused by my usb hub. So I unplugged it. I'll upload my Minidump folder just in case.

It looks like you found the culprit already. Your processor is overheating. You should be getting high 40s for that processor during stress. Do you have the proper cooling system installed? Is the thermal compound applied between the processor and heat sink properly? Are your fans reaching the necessary speeds to cool the processor?

I think you're right about the processor overheating. I didn't think the temperature was an issue by what I was reading online but I guess you can't trust everything you hear.

So I just took everything apart, reapplying thermal paste to the CPU and cleaning the heat sink as much as possible. I used a business card method of applying thermal paste this time. Not sure if that is the best way. I used the "put a dot in the middle and let the heat sink pressure spread it out" method last time because I remember reading a guide about that being the best way. But when I looked at it tonight it looked really uneven so decided not to go that route again.

Anyways I've been running Prime95 now for about 30 mins and max temp it hit was 51C. 5 degrees less. I guess it's not quite ideal but it hasn't crashed yet where before it would crash in about 5-10 mins. So I think it's a good thing and we're on the right track. Will mess with it more and run Prime95 longer tomorrow and post up if everything is still going well.

Here is the heat sink I'm using btw : Newegg.com - ZALMAN CNPS8700 2 Ball CPU Cooler