Is your issue over? If not, I can say that the single crash dump you uploaded is a crash during gaming, BF3.
You are overclocked.
Code:
CPUID: "Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz"
MaxSpeed: 2500
CurrentSpeed: 2508
If an overclocked system is crashing, it is must to stop overclocking at first. As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)
Display driver is failing.
Code:
fffff880`0a5e6618 fffff880`0fee0a11*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm+0xbda11
And it is old.
Code:
fffff880`0fe23000 fffff880`10b17000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Tue Oct 02 23:51:13 2012 (506B3099)
CheckSum: 00CD4613
ImageSize: 00CF4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Install the latest WHQL only.
- Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
- Now follow Drivers - Clean Left over Files after Uninstalling
- Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 320.49 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
The network driver is failing, too.
Code:
fffff880`0a5e6178 fffff880`10b45132Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Rt64win7+0x2e132
And the driver is even more old.
Code:
fffff880`10b17000 fffff880`10b50000 Rt64win7 T (no symbols)
Loaded symbol image file: Rt64win7.sys
Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
Image name: Rt64win7.sys
Timestamp: Fri May 22 20:22:30 2009 (4A16BC2E)
CheckSum: 00041606
ImageSize: 00039000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Update it from
Realtek.
The system is old. So we should check the heat, too. Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of
Speccy.
Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe. And, let us know about the wattage of the PSU.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Let us know the results.
And, next time, post it following the
Blue Screen of Death (BSOD) Posting Instructions and upload your MSINFO32.nfo file.
- Click on the start button
- Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
- File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
- Give the time for processing, it will save a .nfo file on your desktop.
- Zip it, and upload it following the instruction.
____________________________________________________________________________
BSOD ANALYSIS:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[B]BugCheck 3B[/B], {c000001d, fffff800030ebbc4, fffff8800a5e65f0, 0}
Probably caused by : hardware ( nt!KiSystemServiceHandler+7c )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff800030ebbc4, Address of the instruction which caused the bugcheck
Arg3: fffff8800a5e65f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nt!IopCompleteRequest+4c4
fffff800`030ebbc4 004c8b74 add byte ptr [rbx+rcx*4+74h],cl
CONTEXT: fffff8800a5e65f0 -- (.cxr 0xfffff8800a5e65f0)
rax=fffffa8003d65760 rbx=fffffa800484c240 rcx=0000000000000000
rdx=0000000000000342 rsi=0000000000000000 rdi=fffffa80067b9970
rip=fffff800030ebbc4 rsp=fffff8800a5e6fc0 rbp=0000000000000000
r8=0000000000000002 r9=fffffa8003d65700 r10=0000000003d65700
r11=0000000000000000 r12=0000000000000001 r13=0000000000000000
r14=fffff88002fd3180 r15=fffffa8003d65be0
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!IopCompleteRequest+0x4c4:
fffff800`030ebbc4 004c8b74 add byte ptr [rbx+rcx*4+74h],cl ds:002b:fffffa80`0484c2b4=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: bf3.exe
CURRENT_IRQL: 2
IRP_ADDRESS: ffffffffffffff88
MISALIGNED_IP:
nt!IopCompleteRequest+4c4
fffff800`030ebbc4 004c8b74 add byte ptr [rbx+rcx*4+74h],cl
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800030ebbc4
STACK_TEXT:
fffff880`0a5e5d28 fffff800`030cbde9 : 00000000`0000003b 00000000`c000001d fffff800`030ebbc4 fffff880`0a5e65f0 : nt!KeBugCheckEx
fffff880`0a5e5d30 fffff800`030cb73c : fffff880`0a5e6d88 fffff880`0a5e65f0 00000000`00000000 fffff800`030fa820 : nt!KiBugCheckDispatch+0x69
fffff880`0a5e5e70 fffff800`030f1fad : fffff800`032efc00 fffff800`0322d0d4 fffff800`0305d000 fffff880`0a5e6d88 : nt!KiSystemServiceHandler+0x7c
fffff880`0a5e5eb0 fffff800`030f9620 : fffff800`0321c118 fffff880`0a5e5f28 fffff880`0a5e6d88 fffff800`0305d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0a5e5ee0 fffff800`031066cf : fffff880`0a5e6d88 fffff880`0a5e65f0 fffff880`00000000 fffffa80`067b9970 : nt!RtlDispatchException+0x410
fffff880`0a5e65c0 fffff800`030cbec2 : fffff880`0a5e6d88 fffffa80`0484c240 fffff880`0a5e6e30 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`0a5e6c50 fffff800`030ca01f : fffff880`0a5e6e30 fffff880`0a5e6e02 00000000`00000000 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0a5e6e30 fffff800`030ebbc4 : 00000000`00000000 fffffa80`0484c240 00000000`00000000 00000000`ffffff00 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0a5e6fc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0x4c4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemServiceHandler+7c
fffff800`030cb73c b801000000 mov eax,1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceHandler+7c
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
