SYSTEM_SERVICE_EXCEPTION ATIKMDAG.Sys

My folder: https://www.dropbox.com/s/cryktwdcqi6g3co/minidump.rar?dl=0
Please help me

Widdle
These were related to your video driver (atikmpag.sys). I would remove the current driver and install the newest driver available.
Loading Dump File [C:\Users\Ken\Desktop\minidump\031215-29546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`97079000 PsLoadedModuleList = 0xfffff802`97352250
Debug session time: Thu Mar 12 11:37:44.745 2015 (UTC - 4:00)
System Uptime: 0 days 17:30:12.499
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80102a23374, ffffd0002266cba0, 0}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+21374 )
Followup: MachineOwner
3: 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: fffff80102a23374, Address of the instruction which caused the bugcheck
Arg3: ffffd0002266cba0, 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%p referenced memory at 0x%p. The memory could not be %s.
FAULTING_IP:
atikmpag+21374
fffff801`02a23374 4a8b0cf9 mov rcx,qword ptr [rcx+r15*8]
CONTEXT: ffffd0002266cba0 -- (.cxr 0xffffd0002266cba0;r)
rax=ffffe001c888a590 rbx=ffffe001c4340300 rcx=0000000000000000
rdx=ffffd0002266d5f0 rsi=ffffe001c68b7f40 rdi=ffffe001c888a590
rip=fffff80102a23374 rsp=ffffd0002266d5d0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=ffffe001c888a590 r12=ffffe001c2db5400 r13=ffffe001c69aca40
r14=0000000000000002 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmpag+0x21374:
fffff801`02a23374 4a8b0cf9 mov rcx,qword ptr [rcx+r15*8] ds:002b:00000000`00000000=????????????????
Last set context:
rax=ffffe001c888a590 rbx=ffffe001c4340300 rcx=0000000000000000
rdx=ffffd0002266d5f0 rsi=ffffe001c68b7f40 rdi=ffffe001c888a590
rip=fffff80102a23374 rsp=ffffd0002266d5d0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=ffffe001c888a590 r12=ffffe001c2db5400 r13=ffffe001c69aca40
r14=0000000000000002 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmpag+0x21374:
fffff801`02a23374 4a8b0cf9 mov rcx,qword ptr [rcx+r15*8] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: atieclxx.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from ffffe001c4340300 to fffff80102a23374
STACK_TEXT:
ffffd000`2266d5d0 ffffe001`c4340300 : ffffd000`2266d714 ffffe001`c3840460 00000000`00000000 00000000`00000048 : atikmpag+0x21374
ffffd000`2266d5d8 ffffd000`2266d714 : ffffe001`c3840460 00000000`00000000 00000000`00000048 00000000`00000000 : 0xffffe001`c4340300
ffffd000`2266d5e0 ffffe001`c3840460 : 00000000`00000000 00000000`00000048 00000000`00000000 000000a8`00024020 : 0xffffd000`2266d714
ffffd000`2266d5e8 00000000`00000000 : 00000000`00000048 00000000`00000000 000000a8`00024020 ffffe001`c888a590 : 0xffffe001`c3840460
FOLLOWUP_IP:
atikmpag+21374
fffff801`02a23374 4a8b0cf9 mov rcx,qword ptr [rcx+r15*8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmpag+21374
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 546e9eb6
STACK_COMMAND: .cxr 0xffffd0002266cba0 ; kb
FAILURE_BUCKET_ID: 0x3B_atikmpag+21374
BUCKET_ID: 0x3B_atikmpag+21374
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_atikmpag+21374
FAILURE_ID_HASH: {4a41e3c2-4ddf-1c09-b338-2c76220a0b76}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Similar Messages

Boot Camp 4.0 - Atikmdag.sys crash

Hi all,
I've got a BIG problem with Boot Camp 4.0 ATI driver.
I use a mac mini mid-2011 plugged to a Iiyama PLB2403WS monitor with a HDMI cable. That screen can display 1920x1200 mode.
When I boot the system on Mac OS X Lion, it works perfectly.
After using Boot Camp 4.0 to install Windows 7, the first boot worked well. I had no Aero effects.
But, when I installed Boot Camp Windows support drivers, it did not work anymore.
ATI drivers are guilty because it makes Windows 7 crash at each startup.
I get the famous BSOD displaying the filename Atikmdag.sys with error "PAGE_FAULT_IN_NON_PAGED_AREA".
I guess Apple and AMD must fix the ATI driver for the graphic chip "AMD Radeon 6630M".
When i plug the mac mini on my Samsung HDMI TV, it works great, Windows starts without crashing and i get the Aero effects.
And then when i plug it back to the Iiyama monitor, Windows crashes.
It's confusing and frustrating as I'm not willing to use my TV as the mac mini's monitor display.
Is there any way to make Apple or AMD fix that ?
Or has anyone of you succeeded in using same hardware than me ?
Thanks for your help !

Well I found out by my own a way to overcome this problem
Here is the process to do under windows 7:
1. Install Bootcamp drivers
2. Windows 7 restarts the computer
3. Blue Screen Of Death and the computer automatically restarts...
4. At the restart, press and hold ALT key for boot selection. Choose Windows and then press F8 and then choose Safe Mode with Network activated
5. Go to C:\Windows\System32\drivers and rename atikmdag.sys to atikmdag.sys.old
6. Download latest AMD Radeon Mobility driver for the graphic card (mine is AMD Radeon 6xxxM series)
7. Install the driver
8. Restart the computer
9. Optional : delete file C:\Windows\System32\drivers\atikmdag.sys.old
It works ! You get the Aero effects, no more crash.
My mistake was uninstalling bootcamp's graphical driver beforetrying to install AMD's official drivers (that couldn't detect/recognize the hardware).
But if you don't uninstall bootcamp's graphics drivers, then use the official and latest AMD driver it detects the hardware and you can install the up-to-date driver that works.

HP g049au downgraded to windows 7 32 bit showing atikmdag.sys display problem

HP g049au downgraded to windows 7 32 bit showing atikmdag.sys display problem.
Downgraded according to HP support instructions found here- http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-and-Software/hp-15-g049au-K5B45PA-driver-for...
Crash dump analysis-
On Mon 10/20/2014 5:20:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102014-17222-01.dmp
uptime: 01:20:20
This was probably caused by the following module: atikmdag.sys (atikmdag+0x1CEB1)
Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. CUSTOM_ERROR

Hello @HPpowerUser,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I have read your post on how you have downgraded your system from Windows 8 (64-bit) to Windows 7 (32-bit), and that your system is displaying a atikmdag.sys. I would be happy to assist you in this matter!
According to the available drivers and software for your computer, Windows 7 is only supported for the (64-bit) version of Operating System. To maintain a compatible set of drivers on your system, I recommend downgrading to a 64-bit version of Windows 7.
I hope this helps!
Best Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

T500 Graphic Issue (atikmdag.sys)

Hi, I want to mention I've already went ahead and tried every other possible solution suggested on the web before coming here, but either I am still doing something wrong, or I have to assume my ATI just died... I don't have much experience with computer hardware, so I am really hoping I'm mistaken. Hopefully someone can help me out with this.
The situation:
My T500 Laptop (Win7, 64bit) with switchable graphics suddenly crashed while I was playing a game. The screen froze and the graphics warped/fragmented and I had to force a Reset because nothing happend anymore.
And ever since then I am not able to start up Win7 with my ATI Radeon Mobility HD 3650. I always receive the BSOD (Bluescreen) with the error message that atikmdag.sys caused a critical error and the system shuts down.
Additionally, the Lenovo LCD is no longer showing anything at all, I am forced to use an external monitor to see something.
The start-up screens are all warped by graphical errors, and the only way to load windows using the ATI is to enter safemode. Then I have to uninstall every ATI-Driver if i want to enter Windows again outside safemode.
Next time I start windows, it installs a driver from its local library, and the whole desktop is overlaid with blue vertical lines.
I tried making a screenshot of them, but when I look at the screenshot with my working Intel Graphic card they are nowhere to be seen. Which kinda confuses me...
Using the BIOs to switch from Discrete (ATI) to Integrated (INTEL) graphic card allows me to use my Laptop as usual, with no problems or even hints at the errors the ATI causes. If I use the BIOs to set everything to switchable Graphics I receive the perm-black screen again, but this time even the external monitor is not showing anything.
What I tried to solve this problem:
-Checked for Updates and new drivers.
-Unistalled all installed Drivers and replaced them with the newest Drivers available
-Installed Win7 again, applied every Update, Patch and Driver available
After doing all this, the only thing left would be to assume that the ATI simply died after all the time I spent using her.
Using Google to search for an answer leads me to countless topics with "Use Update" as the answer. I am fairly convinced that the drivers are NOT the problem.
If I need to post anything else, or if the description of my problem is confusing, please tell me. I really hope there is another way to fix my Laptop except replacing it with a new model, so I will try to do anything I can to help find a solution.

This could be a hardware issue. Since it happens as you start up I don't thik it is heat. If under warranty, I would backup everything and send it in - you may end up with a new motherboard. If not, a few thoughts. Re-image your hard drive - back up everything then re-install windows from the bacup media that you made when you got the computer. Otherwise, stick with slow old intel graphics and you will need to game on something else.
T61p, T400
formerly x23, x40

Probably caused by : atikmdag.sys ( atikmdag+127f8 )

I just purchased a new HP ProLiant MicroServer G7 N54L
Here is a short history:
I replaced the 4GB ECC memory to 8GN non-ECC
I originally used a 25ft VGA cable on the on-board VGA port, but had a blue tinge, couldn't recognize the monitor properly, and a bluescreen shutdown, so I removed it.
There is nothing connected to the VGA port now
I now connect using RDP only
The computer freezes randomly and seems to happen when I launch the chrome browser (through RDP)
The dump files are at: https://onedrive.live.com/redir?resid=A19E045098FB769C!1399&authkey=!APLz-efriDf5wAs&ithint=file%2czip
According to my limited knowledge, it seems that the dump files indicate a video problem, but I am not completely sure. Can this be a problem with the motherboard?
Any help is greatly appreciated.

GG
These were related to your 5 year old video driver and may simply need a driver update. It is called a BCC116 and is either the driver or perhaps heat. I would start by removing the current driver and installing the newest driver available.
"It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.
As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
If playing with video driver versions hasn't helped, make sure the box is not overheating.
Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
If so, it might be as simple as dust buildup and subsequently inadequate cooling.
I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
For more information please read this blog http://captaindbg.com/bug-check-0x116-video_tdr_error-troubleshooting-tips/
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\082614-25833-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*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
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0280a000 PsLoadedModuleList = 0xfffff800`02a4d890
Debug session time: Tue Aug 26 23:27:25.092 2014 (UTC - 4:00)
System Uptime: 8 days 2:58:31.684
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80093cd4e0, fffff88004cc57f8, 0, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+127f8 )
Followup: MachineOwner
0: kd> !analyze -v
* Bugcheck Analysis *
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80093cd4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004cc57f8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
FAULTING_IP:
atikmdag+127f8
fffff880`04cc57f8 48895c2408 mov qword ptr [rsp+8],rbx
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
STACK_TEXT:
fffff880`05a5f9c8 fffff880`05327134 : 00000000`00000116 fffffa80`093cd4e0 fffff880`04cc57f8 00000000`00000000 : nt!KeBugCheckEx
fffff880`05a5f9d0 fffff880`05326e3e : fffff880`04cc57f8 fffffa80`093cd4e0 fffffa80`0841cc00 fffffa80`085ce010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05a5fa10 fffff880`04c0ff13 : fffffa80`093cd4e0 00000000`00000000 fffffa80`0841cc00 fffffa80`085ce010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05a5fa40 fffff880`04c39cf1 : 00000000`ffffffff 00000000`02ae8b02 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05a5fb20 fffff880`04c38437 : 00000000`00000102 00000000`00000000 00000000`02ae8b02 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05a5fb50 fffff880`04c0b2d2 : ffffffff`ff676980 fffffa80`085ce010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05a5fbf0 fffff880`04c37ff6 : 00000000`00000000 fffffa80`08641830 00000000`00000080 fffffa80`085ce010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05a5fd00 fffff800`02b1b73a : 00000000`fffffc32 fffffa80`085cf610 fffffa80`06702040 fffffa80`085cf610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05a5fd40 fffff800`028708e6 : fffff800`029fae80 fffffa80`085cf610 fffff800`02a08cc0 fffff880`031b5801 : nt!PspSystemThreadStartup+0x5a
fffff880`05a5fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmdag+127f8
fffff880`04cc57f8 48895c2408 mov qword ptr [rsp+8],rbx
SYMBOL_NAME: atikmdag+127f8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a8a1a8b
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmdag.sys
FAILURE_ID_HASH: {7527b2fa-489f-c504-9452-1a10bd154401}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Atikmdag.sys BSOD appears on Satellite C850-19Q after Win 8.1 update

Please help.
I have Satellite C850-19Q (PSCBYE-00L00GY4), Windows 8 x64, after i update to 8.1 from store, show me BSOD (atikmdag.sys system_thread_exception_not_handled).
I tried to reinstall windows and again install all driver and updates, nothing changed.
Do you have any suggestions?
Thanks in advance.
Sorry about my english mistakes

> i have windows 8.1 before few months ,normaly update without errors, they work perfect and after windows update my system is crash,
Maybe an further Windows updated muddled up the system. I know that graphic card drivers would be updated also automatically during system update too
Uninstall the graphic card driver from device manager.
Then download the Toshiba driver from Toshiba page and install it.
Then please keep eye on further updates in case graphic card driver would ask for update, ignore this notification.
Of course its only my idea but its worth a try

Проблема с драйвером для видеокарты /The problem with the driver for your video card "atikmdag.sys"

При загрузке системы ноутбук стал выдавать "синий экран". Запускается только в безопасном режиме. Переустановил систему все работает, но без драйверов на видеокарту. Как только устанавливаешь драйвера на видеокарту просит перезагрузиться, после перезагрузки вместо хода в сисетму снова "синий экран"

fekero
Thank you for visiting our English HP Support Forum. We are only able to reply to posts written in English. To insure a quick response it would be advisable to post your question in English. The following links are here to assist you if you prefer to post in the following Language Forum.
English: http://h30434.www3.hp.com
Spanish: http://h30467.www3.hp.com
French: http://h30478.www3.hp.com
Portuguese: http://h30487.www3.hp.com
German: http://h30492.www3.hp.com
Korean: http://h30491.www3.hp.com/t5/community/communitypage
Simplified Chinese: http://h30471.www3.hp.com/t5/community/communitypage
Cheers,
KarolB
I work for HP

System_thread_exception_not_handled atikmdag.sys

Now and then I get this error and the BSOD. It usually comes during Youtube access. I'm sure someone has solved this. Please share the solution. New Razerx315Windows 8.1No weird software loaded.

Day three, got the 'thread exception not handled' message again, system re-booted and seems to be fine. So 'flashblock' isn't the fix though it did slow the crashes down from several times a day to one in three days and it does stop the annoying popup ad videos from starting on their own. Back to the drawing board eh.
Waiting on the fix Toshiba and ATI.

Blue screens every few hours with this code SYSTEM_SERVICE_EXCEPTION atikmdag.sys

My desktop blue screens and shuts down every few hours the last two days. Before it does I get this code SYSTEM_SERVICE_EXCEPTION atikmdag.sys
I ran the diagnostics and the only fail I got was for the USB port the FAILURE ID: 9GDN6C-7K4&KN-QFFWLJ-8D0U03
The HP support assistant says I don't have any updated to do and I haven't changed anything? Help?

Hello @amaphotography,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I have read your post on how your desktop computer displays a Blue Screen with an "system service exception" error message, and I would be happy to assist you in this matter!
To prevent your system from locking up in a Blue Screen state in the future, I recommend following the steps in this document on Computer Locks Up or Freezes (Windows 8).
If the issue persists, please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region.
http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
I hope this helps!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

ATIKNDAM.SYS crash

I actually bought a Toshiba before this HP and had the same crash. exactly. returned it and got the HP only to have the same freaking crash. error code says ATIKNDAM.SYS Product name: HP 15 Notebook PC running windows 8.1 64bit

Hello , Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums, I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More. I read your post about the error code, and wanted to help! Have you downloaded the most up to date drivers for your device? Try checking this site for the drivers. Once there, input your Product Number and click "Go". You can select your product on the next screen, using the drop down "+", on the right. On your product support page, you can select Software and Drivers, then click the "Go", that is under Option 2. Once you select your Operating System and click "Update", you should be able to access and download the drivers. You can also use the Recovery Manager, or try a System Restore as well. Here is an additional resource that may be able to assist you:How To Fix Atikmdag.sys Blue Screen Errors (BSOD) (Not a HP supported Web site). Please let me know if this information was helpful by clicking the thumbs up below.
Have a great day!

Random BSOD X58 Pro E new build

Hi everyone, I hope you can help me. I'm new to the custom built PC realm so forgive my ignorance on some of the finer points. I have searched and can't seem to find, or perhaps understand a solution to this problem I'm having. So, with the obligatory "please don't hit me" stuff out of the way here's the deal….
This PC was purchased from ibuypower with a factory 20% overclock. BSODs have appeared randomly since I unpacked it. Initially it was thought these screens were due to an unstable overclock, however they have persisted even with optimized defaults enabled. They usually appear during the first boot of the day, during light duty internet browsing, or doing nothing much at all. The BSOD has never appeared under a heavy load such as flight sim, photoshop, or lightroom (overclocked or not the PC has performed flawlessly running these programs). For example I ran flight simulator for three hours the other night at 3.85GHz with my RAM at 1600MHz and it ran beautifully. As you can see below however (info compiled from the program “whocrashed”) it has happened a ton. These have occurred pretty equally in OC and default configuration. I've ran the default win 7 memory diagnostic, LinX, and memtest86+ with no errors found so far. I hope I have provided enough information for a diagnosis, if most it is useless then I apologize and I will do my best to track down whatever additional info may be required to get to the bottom of this. Thank you in advance.
Intel Core i7-960 3.2GHz
MSI X58 Pro-E MS-7522 BIOS ver. 8.14
Corsair DDR3 1600Mhz 3x2GB
XFX HD 6950 2GB GDDR5 PCI Express 2.1x16
WD 1TB 7200RPM SATA 6.0Gb/s 64MB cache
12-1 internal USB card reader
Corsair H70 Liquid Cooler
Enermax 120mm Fan
Windows 7 home premium 64bit
Corsair AX850 850watts (3.3v/25a, 5v/25a, 12v/70a)
Below is a list of all crashes that have occured...
On Fri 4/8/2011 11:53:11 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x164394)
Bugcheck code: 0x50 (0xFFFFF89FCAC822CC, 0x0, 0xFFFFF88004A21394, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
description: ATI Radeon Kernel Mode Driver
On Fri 4/8/2011 4:05:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040811-16921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41284, 0x2FCC001, 0x0, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Wed 4/6/2011 12:22:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040611-14078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x403, 0xFFFFF68000029698, 0x4E000001B11EA867, 0xFFFFF68000000002)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Wed 4/6/2011 12:13:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040611-17062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x50 (0xFFFFF88047479380, 0x0, 0xFFFFF88004C00215, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
description: NT Kernel & System
On Wed 4/6/2011 12:29:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040511-19218-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x22751)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6800002C398, 0x443000001B152867, 0xFFFFFA8005D5F330)
Error: MEMORY_MANAGEMENT
description: Microsoft Filesystem Filter Manager
On Mon 4/4/2011 12:44:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040411-16234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80033A7AC0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Fri 4/1/2011 3:10:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040111-16984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002922120, 0xFFFFF8800A98B7A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
description: NT Kernel & System
On Fri 4/1/2011 1:35:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040111-17093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004970460, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Thu 3/31/2011 6:16:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033111-24796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41284, 0xA017001, 0x5CD2, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Thu 3/31/2011 6:14:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033111-14218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F4A43D, 0xFFFFF88006FF6D70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
description: NT Kernel & System
On Wed 3/30/2011 6:27:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-17968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003445980, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Wed 3/30/2011 6:24:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-22375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41284, 0x5F3B001, 0xA2D, 0xFFFFF70001080000)
Error: MEMORY_MANAGEMENT
description: NT Kernel & System
On Wed 3/30/2011 6:23:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-23234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x34 (0x50830, 0xFFFFF880033387F8, 0xFFFFF88003338050, 0xFFFFF80002D8908D)
Error: CACHE_MANAGER
description: NT Kernel & System
On Wed 3/30/2011 6:18:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-14640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFB00C2A67AE0, 0x0, 0xFFFFF96000171509, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
description: NT Kernel & System
On Wed 3/30/2011 6:11:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-18218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFFAA007336454, 0x0, 0xFFFFF880012BD642, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
description: NT Kernel & System

With optimized defaults enabled the DRAM voltage is set to auto and it doesn't appear I can change it..please advise. Also, the BSODs have gotten much worse now and I haven't changed anything, they now occur at any time. I've probably gotten six in the past three hours. I guess the computer knows I have reached out to you guys and it's peeved
When the OC is enabled (hasn't been for several days now, but BSODs still occured when it was) the DRAM voltage was set to 1.64v per "tech support" they said that setting it to 1.65v would actually be 1.66v (not sure how that is, but that's what they said).
And to your last question their OC settings were +0.100 on the CPU voltage and 160 on the base clock.

Memory Management, Crit Structure Corrupt, Bad Pool Caller, ntfs file system error

So after freshly installing Win 8.1 I was happy, untill I started to play some games that I previously played on Win 7, I've started to get a whole heap of errors, I did have more written down but have lost the bit of paper they were written on.
Here are the list of errors I can remember.
Memory Management, Crit Structure Corrupt, Bad Pool Caller, ntfs file system error
Specs:
Operating System
Windows 8.1 Pro 64-bit
CPU
AMD Athlon II X2 250
35 °C
Regor 45nm Technology
RAM
6.00GB Dual-Channel DDR2 @ 400MHz (5-5-5-18)
Motherboard
ASUSTeK Computer INC. M3N-H/HDMI (Socket AM2 )
40 °C
Graphics
SyncMaster (1440x900@60Hz)
SAMSUNG (1440x900@60Hz)
ATI Radeon HD 4800 Series (Microsoft Corporation - WDDM v1.1) (Sapphire/PCPartner)
Storage
698GB Western Digital WDC WD7500AAKS-00RBA0 ATA Device (SATA)

Adam
These are Related to
atikmdag.sys ATI Radeon Kernel Mode Driver. Yours is 2+ years old. I would update to the newest driver available.
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\A040614-65203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff803`be013000 PsLoadedModuleList = 0xfffff803`be2da9b0
Debug session time: Mon Apr 7 00:35:03.785 2014 (UTC - 4:00)
System Uptime: 0 days 0:08:48.334
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80001cf7d73, ffffd0002305c470, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+70d73 )
Followup: MachineOwner
0: 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: fffff80001cf7d73, Address of the instruction which caused the bugcheck
Arg3: ffffd0002305c470, 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:
atikmdag+70d73
fffff800`01cf7d73 8a040a mov al,byte ptr [rdx+rcx]
CONTEXT: ffffd0002305c470 -- (.cxr 0xffffd0002305c470;r)
rax=0000000000000000 rbx=ffffcf80021783a0 rcx=ffffcf8002334ff5
rdx=0000307ffdccb010 rsi=ffffcf8004734470 rdi=ffffcf80021783a0
rip=fffff80001cf7d73 rsp=ffffd0002305cea8 rbp=ffffd0002305cf00
r8=0000000000000006 r9=0000000000000000 r10=0000000000000384
r11=ffffcf8002334ff0 r12=0000000000000001 r13=ffffcf8004734470
r14=0000000000000000 r15=ffffcf8004734470
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
atikmdag+0x70d73:
fffff800`01cf7d73 8a040a mov al,byte ptr [rdx+rcx] ds:002b:00000000`00000005=??
Last set context:
rax=0000000000000000 rbx=ffffcf80021783a0 rcx=ffffcf8002334ff5
rdx=0000307ffdccb010 rsi=ffffcf8004734470 rdi=ffffcf80021783a0
rip=fffff80001cf7d73 rsp=ffffd0002305cea8 rbp=ffffd0002305cf00
r8=0000000000000006 r9=0000000000000000 r10=0000000000000384
r11=ffffcf8002334ff0 r12=0000000000000001 r13=ffffcf8004734470
r14=0000000000000000 r15=ffffcf8004734470
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
atikmdag+0x70d73:
fffff800`01cf7d73 8a040a mov al,byte ptr [rdx+rcx] ds:002b:00000000`00000005=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff800025cf3d7 to fffff80001cf7d73
STACK_TEXT:
ffffd000`2305cea8 fffff800`025cf3d7 : ffffcf80`04734470 ffffcf80`04734470 00000000`00000000 ffffcf80`01f52450 : atikmdag+0x70d73
ffffd000`2305ceb0 ffffcf80`04734470 : ffffcf80`04734470 00000000`00000000 ffffcf80`01f52450 ffffd000`2305cf00 : atikmdag+0x9483d7
ffffd000`2305ceb8 ffffcf80`04734470 : 00000000`00000000 ffffcf80`01f52450 ffffd000`2305cf00 fffff800`025f48d3 : 0xffffcf80`04734470
ffffd000`2305cec0 00000000`00000000 : ffffcf80`01f52450 ffffd000`2305cf00 fffff800`025f48d3 ffffcf80`04734470 : 0xffffcf80`04734470
FOLLOWUP_IP:
atikmdag+70d73
fffff800`01cf7d73 8a040a mov al,byte ptr [rdx+rcx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+70d73
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fdf9bbd
STACK_COMMAND: .cxr 0xffffd0002305c470 ; kb
FAILURE_BUCKET_ID: 0x3B_VRF_atikmdag+70d73
BUCKET_ID: 0x3B_VRF_atikmdag+70d73
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_vrf_atikmdag+70d73
FAILURE_ID_HASH: {1ec4cdaf-008d-03dd-4ca9-ade1993441da}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Msi z87 gd 65 gaming freezing and bsod

msi z87 gd 65 gaming freezing and bsod happens in a game or on desktop
build 26/09/2013 08:16 PM
i7 - 4770k
msi z87 gd65 gaming
corsair 32 gb ddr3 cmy32gx3m4a2400c10r
asus r9280x-dc2-3gd5 r9 280x
h110i corsair
corsair hx860i
crucial m4
cooler master cormos 2 case
system started to freeze and bsod
items I have done
osri
new psu
memtest all sticks and one at a time all passed
hd tune smart test passed
increased voltage on memory in case it was that as the x m p does it at 1.5v increase 4 steps from 1.5v to 1.9v all 4 gave the same issue
1.65v bsod as well
who crashed says amd ccc is causing the issue reinstalled with driver from asus and latest also the beta same issue is happening
this is why I think its the main board but was going to run the system from intel gpu by removing the amd gpu from system maybe even test an alt slot x8 to see what happens
currently testing r9 280z card with default gpu clock 850mhz instead of 1000mhz incase that's whats causing it
I know this is another post the other post does not have edit on the post any more so making you aware of this
any one got any ideas as to what to try next
On Sat 06/09/2014 04:26:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8346-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2DBA1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FFB3BA1, 0xFFFFF8800CFEE540, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 21:27:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8564-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600012E354)
Bugcheck code: 0x50 (0xFFFFFD00C0873680, 0x0, 0xFFFFF9600012E354, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 17:54:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-7909-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3267E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004A3267E, 0xFFFFF880060F6A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 23:44:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-9796-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00B7F9E50, 0x0, 0x15B641)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:54:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-7878-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800494A12B, 0xFFFFF88011FF4558, 0xFFFFF88011FF3DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:30:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-8470-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FF8F8F0, 0xFFFFF8800907E420, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 02/09/2014 18:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8143-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8B00E9D800C, 0x0, 0xFFFFF8000397A981, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 31/08/2014 15:31:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-7753-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800413B12B, 0xFFFFF88011DEF558, 0xFFFFF88011DEEDB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 31/08/2014 08:49:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-8424-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F7)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880048308F7, 0xFFFFF88008DC2B00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 30/08/2014 22:58:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-9687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFDA801908C040, 0x2, 0x0, 0xFFFFF80003659EC9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
26 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

No need to edit, just add a reply as flobelix asked for exact models of RAM and motherboard.
As it's double posting, this one gets locked. Please continue this one:
https://forum-en.msi.com/index.php?topic=183138.msg1314803#msg1314803
>>Please read and comply with the Forum Rules.<<
Topic Locked

BSODs relating to drivers

I have been getting two kinds of BSODs:
0xa0000001 : relating to files WppRecorder.sys and atikmdag.sys
0x0000003b : dxgkrnl.sys and ntoskrnl.exe
I know that these are related to drivers. I have tried to upgrade my AMD graphics driver but you can only get "catalyst control center" from the AMD site... I have AMD Radeon R7 260X and win8.1 64bit
Is there an easy way to upgrade my graphics driver?
This is a new computer so I really would like to be able to fix these issues.

J
3 of 4 were related to your video driver. There is a known problem with the April driver so I would revert back to a driver at least 6 months old or more.
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\082714-7093-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff801`27c18000 PsLoadedModuleList = 0xfffff801`27ee22d0
Debug session time: Wed Aug 27 10:20:05.004 2014 (UTC - 4:00)
System Uptime: 0 days 10:43:35.712
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8011ff5b2ec, ffffd00020b227c0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+b12ec )
Followup: MachineOwner
0: 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: fffff8011ff5b2ec, Address of the instruction which caused the bugcheck
Arg3: ffffd00020b227c0, 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:
atikmdag+b12ec
fffff801`1ff5b2ec 488b02 mov rax,qword ptr [rdx]
CONTEXT: ffffd00020b227c0 -- (.cxr 0xffffd00020b227c0;r)
rax=fffff801200d6620 rbx=0000000000000000 rcx=ffffe0000e724028
rdx=0000000000000000 rsi=ffffd00020b2393c rdi=fffff801200d5ff0
rip=fffff8011ff5b2ec rsp=ffffd00020b231f0 rbp=ffffd00020b23321
r8=00000000b9746c14 r9=0000000000000001 r10=0000000000000008
r11=0000000000000000 r12=ffffe0000d8a1900 r13=0000000000000051
r14=0000000000000000 r15=ffffe0000eadc180
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
atikmdag+0xb12ec:
fffff801`1ff5b2ec 488b02 mov rax,qword ptr [rdx] ds:002b:00000000`00000000=????????????????
Last set context:
rax=fffff801200d6620 rbx=0000000000000000 rcx=ffffe0000e724028
rdx=0000000000000000 rsi=ffffd00020b2393c rdi=fffff801200d5ff0
rip=fffff8011ff5b2ec rsp=ffffd00020b231f0 rbp=ffffd00020b23321
r8=00000000b9746c14 r9=0000000000000001 r10=0000000000000008
r11=0000000000000000 r12=ffffe0000d8a1900 r13=0000000000000051
r14=0000000000000000 r15=ffffe0000eadc180
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
atikmdag+0xb12ec:
fffff801`1ff5b2ec 488b02 mov rax,qword ptr [rdx] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000050 to fffff8011ff5b2ec
STACK_TEXT:
ffffd000`20b231f0 00000000`00000050 : fffffff6`00000002 00000001`ffffffff ffffc001`3e553470 ffffe000`0eadc180 : atikmdag+0xb12ec
ffffd000`20b231f8 fffffff6`00000002 : 00000001`ffffffff ffffc001`3e553470 ffffe000`0eadc180 00000000`00000000 : 0x50
ffffd000`20b23200 00000001`ffffffff : ffffc001`3e553470 ffffe000`0eadc180 00000000`00000000 00000000`00000001 : 0xfffffff6`00000002
ffffd000`20b23208 ffffc001`3e553470 : ffffe000`0eadc180 00000000`00000000 00000000`00000001 fffff801`1fec305d : 0x00000001`ffffffff
ffffd000`20b23210 ffffe000`0eadc180 : 00000000`00000000 00000000`00000001 fffff801`1fec305d 00000000`00000000 : 0xffffc001`3e553470
ffffd000`20b23218 00000000`00000000 : 00000000`00000001 fffff801`1fec305d 00000000`00000000 ffffd000`20b23321 : 0xffffe000`0eadc180
FOLLOWUP_IP:
atikmdag+b12ec
fffff801`1ff5b2ec 488b02 mov rax,qword ptr [rdx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+b12ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53bd610a
STACK_COMMAND: .cxr 0xffffd00020b227c0 ; kb
FAILURE_BUCKET_ID: 0x3B_atikmdag+b12ec
BUCKET_ID: 0x3B_atikmdag+b12ec
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x3b_atikmdag+b12ec
FAILURE_ID_HASH: {1b2cc265-caf2-86e2-2d0e-bdd6577813d4}
Followup: MachineOwner
0: kd> lmvm atikmdag
start end module name
fffff801`1feaa000 fffff801`20e53000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Wed Jul 09 11:34:34 2014 (53BD610A)
CheckSum: 00F46306
ImageSize: 00FA9000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Wanikiya and Dyami--Team Zigzag

How to increase brightness in Windows 7 and for the Option sceen?

I have an 15" early 2011 MBP with Snow Leopard and reccently installed 64-bit Windows 7 Pro using an upgrade disk I had. Apparently the backup/upgrade disk would allow me to do a clean install despite not having a previous version of windows to base it off of now that XP is no longer supported.
I had no initial problems installing Windows and getting the bootcamp software fully updated (3.2 I believe,) but while I was in the process of updating all of my windows software things started getting messy. I managed to update some windows functions, but eventually I ran into a real problem after downloading what I believe to be a service pack (not sure which one) that was recommended by the windows updater. After downloading the update, the computer needed to be reset.
Upon resetting the laptop, I found that the option screen that lets you choose which partition to boot into is completely black. I can tell that the display is on because the screen is somewhat brighter than when the laptop is off, but I can't see anything.
For grins, I tried seeing if hitting the right arrow key and then enter would take me to my windows partion, which it did. The loading screen (with the windows icon approaching and illuminating) is completely fine; however, after that loading screen, the screen appears to turn off (nothing, zilch, nada.) I let it sit there for about 5 minutes or so and still had nothing. Upon hard-resetting my computer, I found that when I tried booting windows again it gave me the options to boot into safe mode. Safe mode works and gives full brightness, normal mode does not.
I looked on the forums and saw that deleting C:\WINDOWS\SYSTEM32\DRIVERS\ATIKMDAG.SYS could fix the issue. I downloaded Paragon, mounted the bootcamp partition and removed the offending file from my mac partition.
The option screen was still black, but the login screen appeared after the computer tried to finish patching (the service pack patch failed.) The problem then was that the screen was incredibly dim at full brightness. I had control of the brightness settings via fn+f1/f2. All it took was dimming the screen 3 notches in order to make it go completely black. I logged in and tried updating the radeon video card, reset the computer and found myself back at the off screen issue mentioned earlier after the windows loading screen.
I have yet to check, as this process has been extremely tiring and annoying, but I think I can fix the completely dead screen by removing the driver again. I gave this long story to show what I have done so hopefully I cam get a response I
My burning questions are:
What do I need to do to get the screen back to full brightness when I do get my laptop to boot into windows successfully?
How do I fix my option screen to actually show up again instead of blindly picking the partition I want to boot into?
Are there any windows updates that I need to avoid for 64-bit windows 7? I'm guessing whatever service pack it was I downloaded is one of them.

I don't use the search engine, so I'm afriad I don't have direct experience here.
What I'd probably do is modify the app so that it looks at the Host data to determine which directory it should point to for graphics, formatting, etc. You could also use the obj.conf with variables to pull graphics from directories appropriately branded. Something like:
1) Create "additional doc directory" for images
2) Find the entry in the obj.conf that points to the new directory
3) Modify the path to something like /path/to/$host/images
4) Make sure you create directories like:
/path/to/foobar.com/images/
/path/to/www.foobar.com/images/
/path/to/baz.com/images/
/path/to/www.baz.com/images/

SYSTEM_SERVICE_EXCEPTION ATIKMDAG.Sys

Similar Messages

Maybe you are looking for