New
#11
i guess it really related to battlefield 4 somehow from your experience is such a thing possible ?
and here is the attachment
i guess it really related to battlefield 4 somehow from your experience is such a thing possible ?
and here is the attachment
Most possible.
Uninstall your installed latest version of the display driver.
Then clean up any possible leftover.
Then install version 13.9 WHQL only.
When the driver is properly applied, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Let us know the result.
________________________
Code:*** 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, {ffffffffc0000005, fffff8800f144dbb, fffff880027cf228, fffff880027cea80} Probably caused by : atikmdag.sys ( atikmdag+c7dbb ) Followup: MachineOwner --------- 2: 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: ffffffffc0000005, The exception code that was not handled Arg2: fffff8800f144dbb, The address that the exception occurred at Arg3: fffff880027cf228, Exception Record Address Arg4: fffff880027cea80, Context Record Address 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+c7dbb fffff880`0f144dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] EXCEPTION_RECORD: fffff880027cf228 -- (.exr 0xfffff880027cf228) ExceptionAddress: fffff8800f144dbb (atikmdag+0x00000000000c7dbb) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000000006a8 Attempt to read from address 00000000000006a8 CONTEXT: fffff880027cea80 -- (.cxr 0xfffff880027cea80;r) rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=00000000000e0000 rdi=0000000000000002 rip=fffff8800f144dbb rsp=fffff880027cf460 rbp=fffffa8008789960 r8=0000000000000002 r9=000000f418128000 r10=0000000000000000 r11=fffff880027cf690 r12=fffffa8008966480 r13=fffffa8007f02280 r14=fffffa8006c411d0 r15=fffff8800f07d000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 atikmdag+0xc7dbb: fffff880`0f144dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=???????????????? Last set context: rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=00000000000e0000 rdi=0000000000000002 rip=fffff8800f144dbb rsp=fffff880027cf460 rbp=fffffa8008789960 r8=0000000000000002 r9=000000f418128000 r10=0000000000000000 r11=fffff880027cf690 r12=fffffa8008966480 r13=fffffa8007f02280 r14=fffffa8006c411d0 r15=fffff8800f07d000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 atikmdag+0xc7dbb: fffff880`0f144dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 00000000000006a8 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c7100 GetUlongFromAddress: unable to read from fffff800034c71c0 00000000000006a8 Nonpaged pool FOLLOWUP_IP: atikmdag+c7dbb fffff880`0f144dbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] BUGCHECK_STR: 0x7E ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre LAST_CONTROL_TRANSFER: from 00000000000000a1 to fffff8800f144dbb STACK_TEXT: fffff880`027cf460 00000000`000000a1 : 00000000`00000000 fffffa80`00000028 00000000`00000004 fffffa80`06c411d0 : atikmdag+0xc7dbb fffff880`027cf468 00000000`00000000 : fffffa80`00000028 00000000`00000004 fffffa80`06c411d0 fffff880`0f1a5f6f : 0xa1 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+c7dbb FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 53508a3c STACK_COMMAND: .cxr 0xfffff880027cea80 ; kb FAILURE_BUCKET_ID: X64_0x7E_atikmdag+c7dbb BUCKET_ID: X64_0x7E_atikmdag+c7dbb ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x7e_atikmdag+c7dbb FAILURE_ID_HASH: {1bce3716-c561-7934-01c3-535369bb657c} Followup: MachineOwner --------- 2: kd> lmvm atikmdag start end module name fffff880`0f07d000 fffff880`0ff8d000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Fri Apr 18 07:43:16 2014 (53508A3C) CheckSum: 00EAEEE6 ImageSize: 00F10000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Done and here is screenshot of the furmark test it got stable at 74C , test done for 15mins
so does that means bf4 got nothing to do with my bluescreenofdeath and then again what's seem to be the problem ?
** about the force close no worries i just hit f9 to take a screenshot and then i didnt waited for it to respond so not a problem i guess and i took the pic with printscreen
and as i have read and been reading it could be a driver problem which could be solver but getting an older version of CCC or getting the windows driver but well that might decrease games stability and performance since as the developers say they increase stability and performance with each version especially for popular games which i play most.
or as i saw at an other website this thing which i dont really like
"""
Try simple things first!
1st.
boot into the bios and look at the bios rev on the main screen. asus on the older bios switch from a .rom to a .cap file. the newest bios has a lot of bug fixes and for windows 7/8. the other bug fixes are for ram and cpu code updates. there a usb flashback port to flash your mb without powering the mb on or put the new .cap file on a usb stick and use the bios updater inside of the mb bios. also make sure from the mb installer cd you did not install the Lucid Virtu Software V1.2.108.18765 for Windows 7 32bit & 64bit. it a know issues to crash windows and gpu when it tries to bond a ipgpu with a gpu.
i would also boot into safe mode..uninstall the ati drivers..get windows to boot into windows normal then install the newest intel chipset drivers then reboot. then try the ati drivers again
If not working try this:
2nd.
Follow every step :
Step 1: Download and install the latest ati graphic driver.AND DONT TURN OFF OR RESTART YOUR COMPUTER AFTER INSTALLATION
Step 2: Then go to C:\Windows\System32\Drivers and rename atikmdag.sys to atikmdag.sys.old.
Step 3: Go to ati directory (usually in C:\ATI) and find the file atikmdag.sy_.
Step 4: Copy the file to your Desktop directory.
Step 5: Open cmd.exe by going to Start -> type cmd in the search box and hit enter.
Step 6: Change the directory to Desktop by typing chdir Desktop.
Step 7: Then, type EXPAND.EXE atikmdag.sy_ atikmdag.sys. Or,
expand -r atikmdag.sy_ atikmdag.sys
Step 8: When the expansion is complete, copy the new atikmdag.sys from your Desktop to
C:\Windows\System32\Drivers
Step 9: Restart your computer and the problem should be resolved.
Its not faulty mb or card problem! The drivers is the main culprit here!
""
This is a MSI board having an ASUS PID.
This may be the source of any problem. Can you tell us how you activated this windows installation?Code:Product ID: 00426-OEM-8992662-00173 Original Install Date: 7/9/2013, 9:43:29 AM System Boot Time: 6/6/2014, 4:00:13 PM System Manufacturer: MSI System Model: MS-7758
i have no idea , but this is personal build pc that i built (purchased all the specific hardware from 1 shop same one) i bought the windows as well and the shop had the computer in together and activated the windows and put on , i guess when i get this BSOD i shall take a pic of it and send it to him with the pc to solve it ?
its still in warranty
but what seems to be the problem exactly ? a mother board have asus pid :/ ?
I am guessing that you have got a counterfeit windows installation. And those are problematic. Can you post a report following the Windows Genuine and Activation Issue Posting Instructions? It will help us to determine whether my guess is correct or not.
here i would really like to know if its counterfeit or not
Code:Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 0 Cached Online Validation Code: 0x0 Windows Product Key: *****-*****-Q6MMK-KYK6X-VKM6G Windows Product Key Hash: 289NoAWl2ZoVfuieux/315WkDIc= Windows Product ID: 00426-OEM-8992662-00173 Windows Product ID Type: 2 Windows License Type: OEM SLP Windows OS version: 6.1.7601.2.00010100.1.0.001 ID: {FC222F50-BDEB-4521-8CC1-941A41011610}(1) Is Admin: Yes TestCab: 0x0 LegitcheckControl ActiveX: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows 7 Ultimate Architecture: 0x00000009 Build lab: 7601.win7sp1_gdr.130318-1533 TTS Error: Validation Diagnostic: Resolution Status: N/A Vista WgaER Data--> ThreatID(s): N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 Windows XP Notifications Data--> Cached Result: N/A, hr = 0x80070002 File Exists: No Version: N/A, hr = 0x80070002 WgaTray.exe Signed By: N/A, hr = 0x80070002 WgaLogon.dll Signed By: N/A, hr = 0x80070002 OGA Notifications Data--> Cached Result: N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 OGAExec.exe Signed By: N/A, hr = 0x80070002 OGAAddin.dll Signed By: N/A, hr = 0x80070002 OGA Data--> Office Status: 100 Genuine Microsoft Office Enterprise 2007 - 100 Genuine OGA Version: N/A, 0x80070002 Signed By: N/A, hr = 0x80070002 Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-b01a_E2AD56EA-766-0_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005 Browser Data--> Proxy settings: N/A User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32) Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe Download signed ActiveX controls: Prompt Download unsigned ActiveX controls: Disabled Run ActiveX controls and plug-ins: Allowed Initialize and script ActiveX controls not marked as safe: Disabled Allow scripting of Internet Explorer Webbrowser control: Disabled Active scripting: Allowed Script ActiveX controls marked as safe for scripting: Allowed File Scan Data--> Other data--> Office Details: <GenuineResults><MachineData><UGUID>{FC222F50-BDEB-4521-8CC1-941A41011610}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-VKM6G</PKey><PID>00426-OEM-8992662-00173</PID><PIDType>2</PIDType><SID>S-1-5-21-3397813922-1786779290-2813070985</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7758</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V2.10</Version><SMBIOSVersion major="2" minor="7"/><Date>20130410000000.000000+000</Date></BIOS><HWID>E8473A07018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Jerusalem Standard Time(GMT+02:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>_ASUS_</OEMID><OEMTableID>Notebook</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>64BC76978749586</Val><Hash>GW6PzcEVEDTVKeO5Ym5UUm41dBk=</Hash><Pid>89388-707-0441865-65504</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> Spsys.log Content: 0x80070002 Licensing Data--> C:\Windows\system32\slmgr.vbs(22, 1) (null): The specified module could not be found. Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: 0x00000000 HealthStatus: 0x0000000000000000 Event Time Stamp: 6:6:2014 11:43 ActiveX: Registered, Version: 7.1.7600.16395 Admin Service: Registered, Version: 7.1.7600.16395 HealthStatus Bitmask Output: HWID Data--> HWID Hash Current: MgAAAAEAAgABAAIAAAACAAAAAgABAAEAln0+5/4LEsJGPxCp7D7OcIqbYKqIL85/lmM= OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes Windows marker version: 0x20001 OEMID and OEMTableID Consistent: yes BIOS Information: ACPI Table Name OEMID Value OEMTableID Value APIC ALASKA A M I FACP ALASKA A M I HPET ALASKA A M I MCFG ALASKA A M I FPDT ALASKA A M I SSDT Intel_ AoacTabl SSDT Intel_ AoacTabl SSDT Intel_ AoacTabl SSDT Intel_ AoacTabl SLIC _ASUS_ Notebook
You have a problem in your MGADiag report....
This is not a common one.Code:Licensing Data--> C:\Windows\system32\slmgr.vbs(22, 1) (null): The specified module could not be found.
You also have what appears to be a counterfeit copy of Office installed.
Your BIOS is dated April 2013 - well after the release of Windows 8.
The motherboard is an MSI retail one, but the Product Key in use for Windows is one from an ASUS computer.
Your installations of both Windows and Office are counterfeit.
You need to reformat and reinstall using genuine media and Key.