Not sure why-BSOD


New Member
I have a home built tower running windows 7. I seem to always get a BSOD when trying to start the system. I tried to check to make sure all drivers were up to date and I think they are. I thought perhaps it was caused by a buildup of dust because I have so much air going through this think. So I took my air tank and you should have seen the dust fly. But still no luck. I found a windows mini-dunp file and I will try to attach it to this post. I am not sure what to do with it since it comes up with gibberish to me. View attachment 042312-30732-01.dmp


Noob Whisperer
Hello and welcome to the forum.
One dump file
[U][B]BugCheck 100000D1[/B][/U], {91eb0ad7, 9, 0, 9349aadb}
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]atikmpag.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]atikmpag.sys[/B][/U][/COLOR]
Probably caused by : [COLOR=#ff0000][U][B]atikmdag.sys[/B][/U][/COLOR] ( atikmdag+95adb )
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arg1: 91eb0ad7, memory referenced
Arg2: 00000009, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 9349aadb, address which referenced memory
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d73828
Unable to read MiSystemVaType memory at 82d53d80
9349aadb 8b6c5657        mov     ebp,dword ptr [esi+edx*2+57h]
LAST_CONTROL_TRANSFER:  from 9348fd50 to 9349aadb

WARNING: Stack unwind information not available. Following frames may be wrong.
80d91b90 9348fd50 861ca000 85e72900 85a2c1d0 atikmdag+0x95adb
80d91ba8 9341ed6e 861ca000 80d91bcc 9314181e atikmdag+0x8ad50
80d91bb4 9314181e 85e72900 00000000 85f46000 atikmdag+0x19d6e
80d91bcc 9317eb14 85e72900 00000000 80d91bf0 atikmpag+0x481e
80d91bdc 9318ed59 85f46000 85ac4920 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
80d91bf0 82c45e4d 85f46000 85ac4920 80d91c1c dxgkrnl!DpiFdoLineInterruptRoutine+0x12
80d91bf0 8301cba0 85f46000 85ac4920 80d91c1c nt!KiInterruptDispatch+0x6d
80d91c98 8301a92d 93bca8cb 86bdc368 868031e8 hal!KfLowerIrql+0x58
80d91c9c 93bca8cb 86bdc368 868031e8 00000000 hal!KeReleaseQueuedSpinLock+0x2d
80d91d28 93bef3c9 863fd008 82c42fa2 863fd008 dxgmms1!VidSchiScheduleCommandToRun+0x85
80d91d3c 93bef485 863fd008 00000000 86438d48 dxgmms1!VidSchiRun_PriorityTable+0xf
80d91d50 82dfc4e6 863fd008 bc648e39 00000000 dxgmms1!VidSchiWorkerThread+0x7f
80d91d90 82c9d999 93bef406 863fd008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
9349aadb 8b6c5657        mov     ebp,dword ptr [esi+edx*2+57h]
SYMBOL_NAME:  [COLOR=#ff0000][U][B]atikmdag[/B][/U][/COLOR]+95adb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [COLOR=#ff0000][U][B]atikmdag[/B][/U][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][U][B]atikmdag.sys[/B][/U][/COLOR]
FAILURE_BUCKET_ID:  0xD1_[COLOR=#ff0000][U][B]atikmdag[/B][/U][/COLOR]+95adb
BUCKET_ID:  0xD1_[COLOR=#ff0000][U][B]atikmdag[/B][/U][/COLOR]+95adb
atikmdag.sys 4/19/2011 ATI Video Driver see if there is something more current here AMD Graphics Drivers & Software
Some other older drivers which may need your attention
giveio.sys 4/3/1996 Possibly a part of Speed Fan. Uninstall and make sure the driver is no longer on your system. Update to the newest version of speed fan.
pcouffin.sys 12/5/2006 Used by any number of CD / DVD burning software. Update, uninstall or rename to pcouffin.OLD
fetnd6.sys 6/19/2008 VIA Rhine Family Fast Ethernet Adapter try here for an update Rhine Ethernet Controllers - VIA Technologies, Inc.

If Blue Screens persist, then;
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on 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
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area .
Good luck


New Member
OK I got another BSOD I tired to grab the mini-dump but it said it was named the same as the one I already posted. Odd. But I disconnected the dvd-rom just for the heck of it. I ran memtest86+ overnight with no errors. Then I uninstalled the video driver and tried booting up. It booted without a problem. Of course it installed the video driver right away when I booted and then I got the BSOD when I tried to restart the computer. I have tried installing several other video card drivers with no success. Not sure what to do next.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.