Welcome to the Forum.
Based on the bugchecks, I would recommend you follow and complete the steps given below:1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS:
Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.
2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its
removal tool and use
Microsoft Security Essentials in its place.
Malwarebytes is a great combination with it. Go through
this thread for more info.
3. Run
Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using
Check Disk (chkdsk) - Read Event Viewer Log
4. Run
SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
5. Make scans with
Kaspersky TDSskiller and
ESET Online scanner.
6. Perform a
Clean Start up, this will help avoid any problematic applications from bugging the system.
7. Use
Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.
8. Use
Crystal Disk Info to
upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a
Hard Drive Diag.
9. Test and Diagnose RAM issues with
RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
10. Monitor hardware temperature for overheating issues with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:
Code:
Loading Dump File [C:\Users\USER\Downloads\SF_16-01-2014\011614-30108-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03290e70
Debug session time: Thu Jan 16 19:23:17.081 2014 (UTC + 6:00)
System Uptime: 0 days 5:30:36.971
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff900c20867a0, 0, fffff9600065dc51, 0}
Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!CddBitmapHw::Release+31 )
Followup: MachineOwner
---------
6: 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: fffff900c20867a0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600065dc51, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fb0e0
GetUlongFromAddress: unable to read from fffff800032fb198
fffff900c20867a0
FAULTING_IP:
cdd!CddBitmapHw::Release+31
fffff960`0065dc51 483b9080070000 cmp rdx,qword ptr [rax+780h]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: BFBC2Game.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800bd0c170 -- (.trap 0xfffff8800bd0c170)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c2086020 rbx=0000000000000000 rcx=fffff900c06dd9f0
rdx=fffffa8009604060 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600065dc51 rsp=fffff8800bd0c300 rbp=0000000000000001
r8=0000000000000000 r9=fffff960002e2a40 r10=0000000000001eea
r11=fffff8800bd0c320 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cdd!CddBitmapHw::Release+0x31:
fffff960`0065dc51 483b9080070000 cmp rdx,qword ptr [rax+780h] ds:fffff900`c20867a0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003143694 to fffff800030c3880
STACK_TEXT:
fffff880`0bd0c008 fffff800`03143694 : 00000000`00000050 fffff900`c20867a0 00000000`00000000 fffff880`0bd0c170 : nt!KeBugCheckEx
fffff880`0bd0c010 fffff800`030c196e : 00000000`00000000 fffff900`c00c0010 00000000`00001700 00000000`6b121783 : nt! ?? ::FNODOBFM::`string'+0x41db7
fffff880`0bd0c170 fffff960`0065dc51 : 00000000`00000000 00001604`00000000 00000a4e`00000000 00000000`060506d3 : nt!KiPageFault+0x16e
fffff880`0bd0c300 fffff960`000f7278 : 00000000`00000001 fffff900`c00c0010 00000000`00000001 fffff900`c24c72a0 : cdd!CddBitmapHw::Release+0x31
fffff880`0bd0c340 fffff960`00236fc4 : fffff900`00000000 fffffa80`00000000 fffff900`c24c72a0 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x358
fffff880`0bd0c490 fffff960`00237067 : fffff900`c00c0010 00000000`00000001 fffff900`c00c0010 00000000`00000000 : win32k!vDynamicConvertNewSurfaceDCs+0xd8
fffff880`0bd0c4c0 fffff960`002378ff : fffff900`c00c0010 00000000`00000001 fffff900`c252d280 fffff900`c00c0010 : win32k!bDynamicRemoveAllDriverRealizations+0x6f
fffff880`0bd0c4f0 fffff960`001f9717 : 00000000`00000000 fffff900`00000000 fffff900`00000400 fffff900`00000000 : win32k!bDynamicModeChange+0x1d7
fffff880`0bd0c5d0 fffff960`0003b29a : 00000000`00000000 fffff900`00000000 00000000`fffffffe 09d72a20`00000004 : win32k!DrvInternalChangeDisplaySettings+0xc5b
fffff880`0bd0c810 fffff960`00124e61 : 00000000`00000004 fffff900`c00c0010 00000000`00000000 09d72a20`00000004 : win32k!DrvChangeDisplaySettings+0xeda
fffff880`0bd0c9f0 fffff960`001250be : 00000000`00000000 00000000`0dd4f368 00000000`0dc4e800 fffff880`06ceeb2b : win32k!xxxInternalUserChangeDisplaySettings+0x329
fffff880`0bd0cab0 fffff960`001127e8 : 00000000`0dc4e800 00000000`0dd4f368 00000000`00000000 00000000`00000004 : win32k!xxxUserChangeDisplaySettings+0x92
fffff880`0bd0cba0 fffff800`030c2ad3 : fffffa80`09604060 fffff880`0bd0cc60 00000000`0dd4f368 00000000`00000004 : win32k!NtUserChangeDisplaySettings+0x98
fffff880`0bd0cbe0 00000000`74ca265a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0dc4e7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74ca265a
STACK_COMMAND: kb
FOLLOWUP_IP:
cdd!CddBitmapHw::Release+31
fffff960`0065dc51 483b9080070000 cmp rdx,qword ptr [rax+780h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: cdd!CddBitmapHw::Release+31
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fbfc6
FAILURE_BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31
BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31
Followup: MachineOwner
---------