SYSTEM_SERVICE_EXCEPTION 0x0000003b when installing AGP ATI drivers

[devnulllore]

Hi,

I have an older system I just rebuilt, upgrading it to it's current maximum. One of those upgrades, Besides Windows 7 SP1 X64 is one of the last great AGP 8X video cards the HIS HD 4670 IceQ Native HDMI 1GB (128bit) DDR3 AGP. The problem is I cannot use ANY driver later than 11.1 or I get a BSOD saying "System_Service_Exception 0x0000003b"

ATI assumed it was a conflict with the ATI/AMD External Events Utility service.

I found several posts relating to much older drivers and this ATI workaround for those drivers:

*Install the latest drivers
*Reboot
*Start the PC in Safe Mode
*Go to Start > Run
*Run Services.Msc
*Find the ATI External Event Utility Service
*Right click > Properties
*Change it to Startup Type = Disabled
*Apply, then click OK
*Reboot and your system should run normally.

I tried this and I still get the BSOD just before the log on screen shows. Also, yes I am using the AGP specified drivers.

So since I have a backup to restore from I did a little playing around to see if I could get the new ATI 11.6 drivers working. The tech at HIS said to try installing the PCI-E drivers first then apply the AGP hotfix. Well as with MANY others with AGP the PCI-E drivers did not even recognize my card. So I tried again anyway. Used Driver Sweeper in safe mode. Made sure all video devices were uninstalled in device manager and ran regedit to remove any ATI entries. No luck I still crashed with a BSOD just before logon.

Either way here is the memory dump of the crash:

==================================================
Dump File : MEMORY.DMP
Crash Time : 7/6/2011 4:59:48 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`05320897
Parameter 3 : fffff880`05ce0b90
Parameter 4 : 00000000`00000000
Caused By Driver :
Caused By Address :
File Name: atikmdag.sys
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MEMORY.DMP
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 236,294,215
==================================================

I then tried a suggestion, using the csapatch, which has worked on older drivers. Problem is the patch is for XP and Vista x32 not 7 x64 and it would not run. I tried disabling and even removing the AMD External Event Viewer service as ATI suggests but that had no effect.

For now I am back to my restored system running Catalyst package 11.1. I have a ticket in with ATI and HIS, and I even have a ticket number from ATI, but for the life of me I cannot find ANYWHERE on the ATI site to look or add to the ticket.
Anyone else have any ideas or am I stuck with these.

Thanks,

dev

 

[JMH]

Hi,

I have an older system I just rebuilt, upgrading it to it's current maximum. One of those upgrades, Besides Windows 7 SP1 X64 is one of the last great AGP 8X video cards the HIS HD 4670 IceQ Native HDMI 1GB (128bit) DDR3 AGP. The problem is I cannot use ANY driver later than 11.1 or I get a BSOD saying "System_Service_Exception 0x0000003b"

ATI assumed it was a conflict with the ATI/AMD External Events Utility service.

I found several posts relating to much older drivers and this ATI workaround for those drivers:

*Install the latest drivers
*Reboot
*Start the PC in Safe Mode
*Go to Start > Run
*Run Services.Msc
*Find the ATI External Event Utility Service
*Right click > Properties
*Change it to Startup Type = Disabled
*Apply, then click OK
*Reboot and your system should run normally.

I tried this and I still get the BSOD just before the log on screen shows. Also, yes I am using the AGP specified drivers.

So since I have a backup to restore from I did a little playing around to see if I could get the new ATI 11.6 drivers working. The tech at HIS said to try installing the PCI-E drivers first then apply the AGP hotfix. Well as with MANY others with AGP the PCI-E drivers did not even recognize my card. So I tried again anyway. Used Driver Sweeper in safe mode. Made sure all video devices were uninstalled in device manager and ran regedit to remove any ATI entries. No luck I still crashed with a BSOD just before logon.

Either way here is the memory dump of the crash:

==================================================
Dump File : MEMORY.DMP
Crash Time : 7/6/2011 4:59:48 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`05320897
Parameter 3 : fffff880`05ce0b90
Parameter 4 : 00000000`00000000
Caused By Driver :
Caused By Address :
File Name: atikmdag.sys
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\MEMORY.DMP
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 236,294,215
==================================================

I then tried a suggestion, using the csapatch, which has worked on older drivers. Problem is the patch is for XP and Vista x32 not 7 x64 and it would not run. I tried disabling and even removing the AMD External Event Viewer service as ATI suggests but that had no effect.

For now I am back to my restored system running Catalyst package 11.1. I have a ticket in with ATI and HIS, and I even have a ticket number from ATI, but for the life of me I cannot find ANYWHERE on the ATI site to look or add to the ticket.
Anyone else have any ideas or am I stuck with these.

Thanks,

dev

Dev Hi and welcome

We really need the actual DMP file to analyze. PLease use the below to upload them to us.





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.



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.

 

[devnulllore]

Minidump File

Here is the minidump file you requested. I hope this helps you find my problem. Please let me know if there is anything else you need.

Joe

 

[JMH]

Here is the minidump file you requested. I hope this helps you find my problem. Please let me know if there is anything else you need.

Joe

Joe

This crash was blamed on your video driver (atikmdag.sys) and despite it being current it still seems to be problematic. It may be some other component of the video subsystem (ie vram, heat, power, etc).

Often this error code is defined as:
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.

Next step is to download cpu-z and gpu-z (both free) to keep an eye on the temperatures.

There are also a few drivers needing updating

ctgame.sys    4/6/2004 8:42:49 PM        fffff880`04e49000    00005510`04e4dc80    0x00005c9000004c80    0x40734e89                        
ElRawDsk.sys    7/26/2008 1:59:09 PM        fffff880`01400000    fffff300`0140a000    0xfffffa800000a000    0x488b65ed

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[devnulllore]

@JHM

Hi,

I beg your forgiveness but I do not fully understand:

"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."


If you could elaborate on this I would appreciate it very much.


Tested the Vram via MRI's boot disk video card testing suite, whole card runs with flying colors. System runs very cool with above specced cooling and I picked the power supply for scalability and is rated for SLI so I doubt those are a factor, but who knows.

I will follow your notes on updating those drivers and see what happens. Maybe if you elaborate on the notes above I can some up with some semblance of a fix.


Also how did you read that minidump file? I would like to examine it myself to learn how to read them and understand them.

Thanks for the help. I will post whatever findings I come up with.


Joe

 

[devnulllore]

Ok, I looked into those drivers CTgame.sys is the Creative driver for my sound cards game port. They do not have a Windows 7 driver but I found one that, although it does not work, Installs and makes it look like it is installed in Device Manager. I just removed it and disabled the device since I do not use it.

ElRawDsk.sys is a raw disk driver whos only job from what I could gather off of Google is to prevent programs like CHKDSK and Defrag from running too soon in dos mode before logon. I disabled that tried the new drivers and got the same crash.

I am back to my restored image and the 11.1 drivers. Any other thoughts?

Thanks,

Joe

 

[devnulllore]

HIS just replied to my ticket with this wonderful news.

"Thanks a lot for your time.
Please wait for Catalyst 11.8 AGP hotfix driver.
AMD replied to us that all our reported issues will be fixed on this driver."

Let us keep out fingers crossed.

Joe

 

[JMH]

Joe,
* Re your Post 5.
As stated in my Post 4....
"This crash was blamed on your video driver (atikmdag.sys) and despite it being current it still seems to be problematic. It may be some other component of the video subsystem (ie vram, heat, power, etc)."

* Analysis is done via WinDbg & Blue Screen View.
Both can be readily Googled.
FYI -
WinDbg - Wikipedia, the free encyclopedia


* Re your Post 7 -
Please keep us updated re outcome.
Good luck.