BSOD caused by SYSTEM_SERVICE_EXCEPTION ntroskrnl.exe

Dp

First you need to update a driver you have from 2005 called asacpi.sys.  A huge cause of BSODS.

Second run driver verifier

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

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

http://support.asus.com/download.aspx?slanguage=en&m=p7p55d%20le&p=1&s=32&os=29&hashedid=e7zic83pvqsr80lm

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).  If you are using Win 8 there is at least a 2012 version which is needed for that.  If you cant find it on the ASUS site you can download it using windows update.  Read about it here

These crashes were related to memory corruption (probably caused by a driver). Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

If you are over-clocking anything reset to default before running these tests.

In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)

**2-Memtest. (**You can read more about running memtest here)

Hi there

Firstly, please accept my sincere thanks for responding.

I have updated the driver as you suggested. It is now displaying a driver for 2009 which according to your notes is correct. For your information, I'm running Windows 7 64bit.

Now, I ran Driver Verifier using the wiki guide. It didn't blue screen on startup (which is a good sign I presume), it didn't blue screen when I ran some tasks but it did make the computer run pretty slowly. What I did manage to do was make the computer restart without prompting.  This wasn't a BSOD, it just restarted.  Therefore I have no dump file to provide you as it wasn't a Blue Screen.

I was doing some daft things to try and make it crash, loading up multiple intensive programs and I think in truth I just overloaded the computer. Is there anything I can provide you. Should I leave Driver Verifier running?

Alternatively, I can leave it off and on Saturday (the next time I plan to use FSX for a few hours), see if I get a BSOD.

Let me know your thoughts and thanks again for your guidance.

Dave

David

Verifier will only force the crash when the misbehaving driver is loaded.  It will slow the computer down a tiny bit.  I would leave it running and upload any new DMPS.  I would also upload your event viewer logs

Please provide us with your Event Viewer administrative logs by following these steps:

Press the Win key + "R" and type eventvwr>enter

Expand Custom Views

Click Administrative Events

Right click Administrative Events

Save all Events in Custom View As...

Save them in a folder where you will remember which folder and save as Errors.evtx

Go to where you saved Errors.evtx

Right click Errors.evtx -> send to -> compressed (zipped) folder

Upload the .zip file to Onedrive or a file sharing service and put a link to it in your next post

*

**If you have updated to win 8.1 and you get the error message "**the system cannot find the file specified" it is a known problem.  The work around is to edit the registry.  If you are not comfortable doing this DONT.  If you are, backup the key before you do

Press Win+"R" and input regedit

Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels.Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"

Hi there,

Just trying to provide you the Event Viewer files but when accessing the Event Viewer, I get an error stating that the Event Log Service is unavailable. Verify that the service is running.

I'm going to run the Driver Verifier for a few hours and see how it gets on.

Thanks

Dave

Dave

Click on the Start button and select Control Panel, Administrative Tools, Services. Locate Windows Event Log in the list. Check that it has started and that the StartUp type is Automatic. If it is not set to Automatic right click and select Properties, General tab. There is a box after StartUp type. The options are available on a drop down by clicking on the arrow down to the right of the box. Make the change and click on Apply and OK. Restart the computer and check whether it has started.