Disc issue continues.
Open the computer. Make it sure that the SSD is properly fixed and connected. Re-seat the SATA/power cables there. If possible, apply a new SATA cable, and apply the disc to another unused SATA port on the motherboard.
Also try to observe if the BSOD is coming mostly during sleep mode or not.
I have did that, used different SATA port on mobo (3 instead of 1), used different cable, and reconnected power cable and sata to SSD.
I've only had 1 more F4, and that was when I inserted a USB. I have also had a newer BSOD, 116. Basically computer crashed before windows loaded, then at the second boot, it came up with Bccode 116. Attaching the newest DM log.
What I'm thinking of doing is a full format of the SSD (again), but this time installing only the drivers that came with the mobo CD (not the newer ones I installed off MSI's website) + 13.9 for video. Unless there is something else it is advisable to try before doing that.
A stop 0x116 is a display caused BSOD. 13.9 WHQL is a good and stable driver itself, but you should give another newer driver a chance. Try the 14.9 WHQL (not the latest 14,12, as it is problematic with some older model cards/gpus). See how it goes.
If stop 0x116 continues, we will have to check the reason in the other possible places.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa800ede5010, fffff88004099e5c, ffffffffc0000001, 5} Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2 *** 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+ae5c ) 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: fffffa800ede5010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88004099e5c, The pointer into responsible device driver module (e.g. owner tag). Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000005, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: atikmpag+ae5c fffff880`04099e5c 4883ec28 sub rsp,28h 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.17237 (debuggers(dbg).140716-0327) amd64fre STACK_TEXT: fffff880`02e34b58 fffff880`0fd0d134 : 00000000`00000116 fffffa80`0ede5010 fffff880`04099e5c ffffffff`c0000001 : nt!KeBugCheckEx fffff880`02e34b60 fffff880`0fd0b36d : fffff880`04099e5c fffff8a0`0121e050 00000000`00000080 fffffa80`0c750040 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`02e34ba0 fffff880`0fd0b1e3 : fffff8a0`0149b140 fffff8a0`01385990 00000000`00000000 00000000`00000000 : dxgkrnl!CTDR_GDI_RESET_THREAD::Worker+0x25 fffff880`02e34bd0 fffff800`0371a73a : 00000000`01879ad5 fffff800`035f9e80 fffff880`02e34c70 fffffa80`0def8b50 : dxgkrnl!CVP_SYSTEM_THREAD::ThreadRoutine+0xf fffff880`02e34c00 fffff800`0346f8e6 : fffff800`035f9e80 fffffa80`0def8b50 fffff800`03607cc0 fffffa80`0ed8f560 : nt!PspSystemThreadStartup+0x5a fffff880`02e34c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+ae5c fffff880`04099e5c 4883ec28 sub rsp,28h SYMBOL_NAME: atikmpag+ae5c FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 52211d80 FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x116_image_atikmpag.sys FAILURE_ID_HASH: {83e844bc-fe68-2042-4230-7f5d3e90b48a} Followup: MachineOwner --------- 0: kd> lmvm atikmpag start end module name fffff880`0408f000 fffff880`0412d000 atikmpag T (no symbols) Loaded symbol image file: atikmpag.sys Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys Image name: atikmpag.sys Timestamp: Sat Aug 31 04:02:32 2013 (52211D80) CheckSum: 0009C9D2 ImageSize: 0009E000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Hi.
I had the 14.9 before, when you told me to change them (and installed 13.9). You mentioned 14.9 is giving some issues on some cards.
What about 13.12?
So I have formated my computer, and tried to install the minimal amount of drivers/programs. Used the mobo CD for original drivers (chipset, sound, ethernet) and ATI 13.12
First F4 code BSOD, it was exactly when I inserted a USB wire (to mini-usb, the ones used to charge androids) into the mobo's frontal USB 3.0 slot (case only has 3.0 in the front). The wire was not attached to any phone or tablet, so just the USB wire by itself.
As usual, HDD LED became solid, windows froze for several seconds (only mouse could be moved, but nothing clicked), then BSOD. I have attached the newest DM Log after this happening
Before formatting, I changed again the SATA wire and port on the motherboard.
Regarding this, should I download this program and try it?
Can you make it sure that the SSD is running with the latest firmware?
How to Upgrade Samsung SSD Firmware | StorageReview.com - Storage Reviews
Confirmed SSD is running on the latest firmware. Did the check 2 days ago, before formatting my SSD.
In the meantime I will be disconnecting the front USB's and see how that goes.
As there are multiple bugchecks, you may test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Quote