Mate,
Have you checked for FSX patches
HERE?
It appears that FSX caused one of the crashes.
Have you tried turning off BitDefender whilst playing FSX?
Code:
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon Aug 18 19:09:43.227 2014 (UTC + 10:00)
System Uptime: 0 days 1:16:04.024
BugCheck A, {80, 2, 1, fffff80010545c10}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2b156 )
BUGCHECK_STR: 0xA
PROCESS_NAME: WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon Aug 18 02:48:26.474 2014 (UTC + 10:00)
System Uptime: 0 days 0:43:39.271
BugCheck 50, {fffffa8087163b90, 0, fffff8800315540c, 5}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+398 )
BUGCHECK_STR: 0x50
PROCESS_NAME: fsx.exe
In order for me to get a better idea of what is crashing you will need to enable Driver verifier, instructions below.
Driver verifier
The Driver Verifier tool that is included in every version of Windows since Windows 2000 it is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior.
***FIRST: Please backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a
System Restore point (so you can restore the system using the Windows 7 Startup Repair feature.)
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select:
---- Special Pool
---- Pool Tracking
---- Force IRQL Checking
----Deadlock Detection
---- Security Checks (Windows 7 & 8)
---- Miscellaneous Checks
- Click "Next"
- Select "Select driver names from a list" and click "Next"
- Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
Will I see anything when I enable Driver Verifier?
No, Driver Verifier configures Windows so that people looking at the crash dump files get (in most cases) more detailed information about what actually crashed the computer.
How Long should I wait for a crash?
- If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
How do I turn Driver Verifier off?!
- Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page.
- Or press the Windows Key + R, and type in "verifier /reset" (Without the quotes)
- Then locate and zip up the memory dump file and upload it with your next post. then locate and zip up the memory dump file and upload it with your next post.
I can't get in to Windows, what do I do?
- If Windows will not start and get to a login screen or desktop, because it crashes too soon, try it in
Safe Mode.
- If you can't get into
Safe Mode, try using
System Restore from your installation DVD to set the system back to the previous restore point that you created.
Instructions on putting files in a Zip file and extracting (Taking them out) again are explained
HERE.
However if you decide to reinstall it
*might* fix the problem, quite often it doesn't. If you do decide to reinstall I would also recommend that you update the firmware on your SSD. Be aware that updating the firmware on the SSD will wipe the drive, so best to do it if you are reinstalling.
There seems to be a motherboard F9 BIOS update
HERE (your current BIOS is F6)
BUT it is a last resort, as updating the motherboard BIOS can brick the motherboard.
If you were having crashes before the MS patch it is unlikely that it is causing your crashes now.
