Have been having blue screen problems since i got my computer seems to be a different error every time, I have attached my system health report and a zip file of the BSOD Dump & System File Collection app, hope it is helpfull. I have left this way too long and need to get a fix, just brought Brink so would be good to play without blue screening all the time haha
9 of 11 related to yuor video driver.
I would re-install using these.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
Or Phyxion.net - Driver Sweeper
When it is removed then download and install the fresh copy.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051411-23275-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`0321b000 PsLoadedModuleList = 0xfffff800`03458e50 Debug session time: Fri May 13 08:12:49.233 2011 (GMT-4) System Uptime: 0 days 6:42:51.794 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ................... Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffff80000003, fffff88004dc623c, fffff88006689668, fffff88006688ed0} Probably caused by : atikmdag.sys ( atikmdag+3a323c ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffff80000003, The exception code that was not handled Arg2: fffff88004dc623c, The address that the exception occurred at Arg3: fffff88006689668, Exception Record Address Arg4: fffff88006688ed0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid FAULTING_IP: atikmdag+3a323c fffff880`04dc623c 83e01f and eax,1Fh EXCEPTION_RECORD: fffff88006689668 -- (.exr 0xfffff88006689668) ExceptionAddress: fffff88004dc623c (atikmdag+0x00000000003a323c) ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 1 Parameter[0]: 0000000000000000 CONTEXT: fffff88006688ed0 -- (.cxr 0xfffff88006688ed0) rax=0000000000000000 rbx=fffffa8006604020 rcx=fffffa8006604000 rdx=fffff88006689920 rsi=fffff88006689920 rdi=fffff88003de3000 rip=fffff88004dc623c rsp=fffff880066898a8 rbp=fffffa8006604000 r8=fffffa8006604000 r9=fffff88006689ac0 r10=fffff88004f56660 r11=fffff88004f56660 r12=fffff88006689a20 r13=0000000000000000 r14=0000000000000001 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=00000246 atikmdag+0x3a323c: fffff880`04dc623c 83e01f and eax,1Fh Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x7E PROCESS_NAME: System CURRENT_IRQL: 2 ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_PARAMETER1: 0000000000000000 LAST_CONTROL_TRANSFER: from fffff88004dc62a3 to fffff88004dc623c STACK_TEXT: fffff880`066898a8 fffff880`04dc62a3 : fffffa80`06604020 fffff880`04db5c74 00000002`00000001 fffff880`04db66d7 : atikmdag+0x3a323c fffff880`066898b0 fffffa80`06604020 : fffff880`04db5c74 00000002`00000001 fffff880`04db66d7 fffffa80`00000000 : atikmdag+0x3a32a3 fffff880`066898b8 fffff880`04db5c74 : 00000002`00000001 fffff880`04db66d7 fffffa80`00000000 fffffa80`06604000 : 0xfffffa80`06604020 fffff880`066898c0 00000002`00000001 : fffff880`04db66d7 fffffa80`00000000 fffffa80`06604000 fffff880`03de3000 : atikmdag+0x392c74 fffff880`066898c8 fffff880`04db66d7 : fffffa80`00000000 fffffa80`06604000 fffff880`03de3000 fffff880`04db65e0 : 0x2`00000001 fffff880`066898d0 fffffa80`00000000 : fffffa80`06604000 fffff880`03de3000 fffff880`04db65e0 fffffa80`06604000 : atikmdag+0x3936d7 fffff880`066898d8 fffffa80`06604000 : fffff880`03de3000 fffff880`04db65e0 fffffa80`06604000 00000000`00000004 : 0xfffffa80`00000000 fffff880`066898e0 fffff880`03de3000 : fffff880`04db65e0 fffffa80`06604000 00000000`00000004 fffffa80`06604020 : 0xfffffa80`06604000 fffff880`066898e8 fffff880`04db65e0 : fffffa80`06604000 00000000`00000004 fffffa80`06604020 fffff880`03de2800 : 0xfffff880`03de3000 fffff880`066898f0 fffffa80`06604000 : 00000000`00000004 fffffa80`06604020 fffff880`03de2800 00000000`00000001 : atikmdag+0x3935e0 fffff880`066898f8 00000000`00000004 : fffffa80`06604020 fffff880`03de2800 00000000`00000001 00000000`81380000 : 0xfffffa80`06604000 fffff880`06689900 fffffa80`06604020 : fffff880`03de2800 00000000`00000001 00000000`81380000 fffffa80`06bff6c0 : 0x4 fffff880`06689908 fffff880`03de2800 : 00000000`00000001 00000000`81380000 fffffa80`06bff6c0 00000000`00000001 : 0xfffffa80`06604020 fffff880`06689910 00000000`00000001 : 00000000`81380000 fffffa80`06bff6c0 00000000`00000001 00000000`00000000 : 0xfffff880`03de2800 fffff880`06689918 00000000`81380000 : fffffa80`06bff6c0 00000000`00000001 00000000`00000000 00000000`81300000 : 0x1 fffff880`06689920 fffffa80`06bff6c0 : 00000000`00000001 00000000`00000000 00000000`81300000 00000000`00000100 : 0x81380000 fffff880`06689928 00000000`00000001 : 00000000`00000000 00000000`81300000 00000000`00000100 00000000`00000000 : 0xfffffa80`06bff6c0 fffff880`06689930 00000000`00000000 : 00000000`81300000 00000000`00000100 00000000`00000000 00000000`00000000 : 0x1 FOLLOWUP_IP: atikmdag+3a323c fffff880`04dc623c 83e01f and eax,1Fh SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+3a323c FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3c99 STACK_COMMAND: .cxr 0xfffff88006688ed0 ; kb FAILURE_BUCKET_ID: X64_0x7E_atikmdag+3a323c BUCKET_ID: X64_0x7E_atikmdag+3a323c Followup: MachineOwner --------- 1: kd> lmvm atikmdag start end module name fffff880`04a23000 fffff880`05357000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Tue Apr 19 21:53:29 2011 (4DAE3C99) CheckSum: 008E91DD ImageSize: 00934000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Cheers, i used the phyxion driver sweeper yesterday and cleaned my AMD driver then re-installed the latestest driver 11.5. i got one blue screen lastnight, page fault in a non paged area etc, does that one have anything to do with my video card driver or is it non related?
ok sweet where abouts are the located? is it easy to get them?
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.
There you go those are the files from the windows/mini dump file. nothing showed up when i searched for sysdm.cpl but i assume the mini dump is working as there is files in the folder. cheers
Simple and straight forward 15 of 18 were probably caused by your video driver
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
Or Phyxion.net - Driver Sweeper
When it is removed then download and install the fresh copy.
How To Find Drivers:Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\New folder (2)\051511-14866-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols *http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`03489e50 Debug session time: Sat May 14 22:12:58.041 2011 (GMT-4) System Uptime: 0 days 2:14:00.727 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffe48013df2a08, 1, fffff880043d5619, 7} Could not read faulting driver name Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSubmitRenderCommand+1fd ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffe48013df2a08, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff880043d5619, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000007, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f40e0 ffffe48013df2a08 FAULTING_IP: dxgmms1!VidSchiSubmitRenderCommand+1fd fffff880`043d5619 4889542448 mov qword ptr [rsp+48h],rdx MM_INTERNAL_CODE: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: System CURRENT_IRQL: 0 TRAP_FRAME: fffff88002356940 -- (.trap 0xfffff88002356940) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8006826000 rbx=0000000000000000 rcx=fffffa8003f96ec0 rdx=fffff88002356b90 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880043d5619 rsp=fffff88002356ad8 rbp=fffffa8003f96ec0 r8=0000000000000000 r9=0000000000000000 r10=fffffa800682e000 r11=0000000000000018 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc dxgmms1!VidSchiSubmitRenderCommand+0x1fd: fffff880`043d5619 4889542448 mov qword ptr [rsp+48h],rdx ss:0018:fffff880`02356b20=fffff88002356d00 Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000333b849 to fffff800032bc740 STACK_TEXT: fffff880`023567d8 fffff800`0333b849 : 00000000`00000050 ffffe480`13df2a08 00000000`00000001 fffff880`02356940 : nt!KeBugCheckEx fffff880`023567e0 fffff800`032ba82e : 00000000`00000001 00000000`00000000 00000000`11440000 00000000`00010000 : nt! ?? ::FNODOBFM::`string'+0x40e0b fffff880`02356940 fffff880`043d5619 : fffff880`02356ae0 00000000`00000001 00000000`00000001 fffffa80`046fb540 : nt!KiPageFault+0x16e fffff880`02356ad8 fffffa80`046fb540 : fffff880`043d5398 fffff800`00b96080 fffff880`043d4d00 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x1fd fffff880`02356cc8 fffff880`043d5398 : fffff800`00b96080 fffff880`043d4d00 fffffa80`00000000 fffffa80`00000000 : 0xfffffa80`046fb540 fffff880`02356cd0 fffff880`043d4e96 : 00000000`00000000 fffffa80`06c9d970 00000000`00000080 fffffa80`05d6b410 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`02356d00 fffff800`0355f7c6 : 00000000`028e8a87 fffffa80`05d70b60 fffffa80`03ce9040 fffffa80`05d70b60 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`02356d40 fffff800`0329ac26 : fffff800`03436e80 fffffa80`05d70b60 fffff800`03444c40 36336d6f`6d62356a : nt!PspSystemThreadStartup+0x5a fffff880`02356d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidSchiSubmitRenderCommand+1fd fffff880`043d5619 4889542448 mov qword ptr [rsp+48h],rdx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: dxgmms1!VidSchiSubmitRenderCommand+1fd FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa174 FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VidSchiSubmitRenderCommand+1fd BUCKET_ID: X64_0x50_dxgmms1!VidSchiSubmitRenderCommand+1fd Followup: MachineOwner ---------- - The most common drivers are listed on this page: Driver Reference Driver Reference- 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.
- - Driver manufacturer links are on this page: Drivers and Downloads
hello again, i have cleaned my AMD driver using the phyxion.net sweeper, i re booted then opened the sweeper again and there is still a registry file and directory file in the AMD display section does that matter?
Quote