Overclock.net › Forums › Intel › Intel CPUs › Battlefield 3 Blue Screen Problems
New Posts  All Forums:Forum Nav:

Battlefield 3 Blue Screen Problems

post #1 of 37
Thread Starter 
I got my 480 on Friday so i wanted to oc my cpu to reduce the chance of any bottlenecks. I got to 4ghz ran prime for 3 hrs then linx and intel burn test and had no problems. Then i tried a few games like crysis 2, mafia 2 etc no problems at all but when i started playing bf3 after maybe 2 mins in game i get a blue screen error with a message saying that the system has halted. I tried raising my vcore to check if that was the problem and it didnt work. Also can it be fraps cause i have had problems before with fraps and bf3 the game would crash or (this happened only once) I would get a blue screen with the same msg
This is my cpuz validation:
http://valid.canardpc.com/show_oc.php?id=2358301

I also tried different bclocks and bus speeds to see if it was that and nothing worked.
I need some help

Note: The temps in game were okay, the max i saw it was 69C in crysis 2 when the fans were at 70%

Note: Note: I have overclocked it before when i had a 460 and everything was running okay, maybe it is the video card.
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
post #2 of 37
Please navigate to C:/Windows/Minidump and zip up any dump files located there that you'd like to have analyzed, and then attach that zip here. If there are no dumps located in C:/Windows/Minump, you may be writing full memory dumps to C:/Windows, and it'll be called MEMORY.DMP.

If there are no dumps in either of those locations, but you know you have a page file set up, any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, will delete this upon use.
post #3 of 37
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

Please navigate to C:/Windows/Minidump and zip up any dump files located there that you'd like to have analyzed, and then attach that zip here. If there are no dumps located in C:/Windows/Minump, you may be writing full memory dumps to C:/Windows, and it'll be called MEMORY.DMP.
If there are no dumps in either of those locations, but you know you have a page file set up, any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, will delete this upon use.

I had two files there and i put them into .zip file. Whats next? Follow your guide on crash dump analysis?
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
post #4 of 37
Quote:
Originally Posted by The Pro View Post

I had two files there and i put them into .zip file. Whats next? Follow your guide on crash dump analysis?

No, please attach the zip here using the attachment system (paper clip in the reply box).
post #5 of 37
Thread Starter 
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
post #6 of 37
How old is your PSU? The 480 is a power sucker and it looks like you'll be close to your maximum power draw. It could be that your system is drawing more power than your psu can provide.
Money-Sink
(26 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k Asus P8P67 Deluxe GTX 980 16 GB G.Skill 1600MHz 8-8-8-24 
Hard DriveHard DriveHard DriveHard Drive
Plextor M3 C300 64GB Seagate Barracuda 7200.12 Samsung Spinpoint S4 
Hard DriveHard DriveOptical DriveCooling
Fantom Drive 1TB External Samsung 850 Pro Asus DVD Burner Custom Full Water Loop 
OSMonitorMonitorKeyboard
Windows 10 Pro Dell U2711 Dell U2412m Razer Blackwidow Ultimate 
PowerCaseMouseMouse Pad
Corsair AX760 HAF X Logitech G9 Mionix Ensis 320 
AudioAudioAudioAudio
Sound Blaster Z Logitech G35 Klipsch Promedia 2.1 Audio Technica ATH AD700 
OtherOther
Scythe KM02-BK Fan Controller Misc Fans, Cathodes, and LEDs 
  hide details  
Reply
Money-Sink
(26 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k Asus P8P67 Deluxe GTX 980 16 GB G.Skill 1600MHz 8-8-8-24 
Hard DriveHard DriveHard DriveHard Drive
Plextor M3 C300 64GB Seagate Barracuda 7200.12 Samsung Spinpoint S4 
Hard DriveHard DriveOptical DriveCooling
Fantom Drive 1TB External Samsung 850 Pro Asus DVD Burner Custom Full Water Loop 
OSMonitorMonitorKeyboard
Windows 10 Pro Dell U2711 Dell U2412m Razer Blackwidow Ultimate 
PowerCaseMouseMouse Pad
Corsair AX760 HAF X Logitech G9 Mionix Ensis 320 
AudioAudioAudioAudio
Sound Blaster Z Logitech G35 Klipsch Promedia 2.1 Audio Technica ATH AD700 
OtherOther
Scythe KM02-BK Fan Controller Misc Fans, Cathodes, and LEDs 
  hide details  
Reply
post #7 of 37
Thread Starter 
Quote:
Originally Posted by Mithrandir8 View Post

How old is your PSU? The 480 is a power sucker and it looks like you'll be close to your maximum power draw. It could be that your system is drawing more power than your psu can provide.
It is probably 2 years old it is as old as my gtx 460 was.
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
post #8 of 37
3 dumps, 3 different bugchecks.

Before we begin, the first thing I noticed is you have an nVidia GPU installed, but the 116 TDR bugcheck crash dump points to AMD's video card drivers as the culprit. Have you not reformatted when you installed the nVidia GPU after previously having an AMD GPU?

Regardless, moving on:

1st dump is a x124 hardware BSOD, likely related to your OC being unstable. Please return any overclocked components to stock and see if the issue stops. If continues, keep me updated.

2nd dump: 116 TDR bugcheck. There are a multitude of things that can cause this specific bugcheck. Before going into that, I should mention this:

NOTE: If overclocking, please reset the system to default values while troubleshooting it. This includes CPU, RAM, GPU overclocking. You're more than welcome to put your stocks back to clock after we've diagnosed your issues!!!!!

The first thing I recommend doing if overclocks aren't the issue is fully uninstalling and reinstalling your nVidia video card drivers, as a bad driver installation can cause 116 bugchecks, especially since the culprit is being pointed to the (nVidiavideo card drivers). If these issues started happening after a driver update, rollback the video card drivers you installed to an earlier version that worked previously without issue.

If drivers do not help, your issue may be heat related, inadequate cooling, dust buildup in the fans or pci-e slot, so make sure your rig is being cooled adequately.

Run Furmark to test your video card to ensure that the card(s) itself is running as intended:
Quote:
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

The following hardware issues can cause a TDR event:
Quote:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile

Memtest download to test your RAM: http://www.memtest86.com/

To "reset" the pagefile, follow these instructions:
Quote:
Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:
Quote:
SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)

- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

The following software issues can cause a TDR event:
Quote:
-Incompatible drivers of any sort (either GPU, sound, etc) ( http://www.microsoft.com/windows/com...s/default.aspx )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)

3rd dump: 3B bugcheck with danew.sys (New DeathAdder Mouse driver) listed as the culprit. Please ensure that this driver is up to date here.

Your drivers list looks okay, nothing from what I can see that is out-of-date or in an important need of update.

With all of this being said, here's a checklist I would follow:

1. Reset all overclocks to stock. If you're still BSOD'ing after that, follow the next steps.

2. Update your mouse driver as I suggested in #3. If you're still BSOD'ing, follow the next steps.

3. Run all the diagnostics I have suggested and provided in #2.

Keep me updated smile.gif

Dumps for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\050412-68453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0365d000 PsLoadedModuleList = 0xfffff800`038a2670
Debug session time: Fri May  4 18:38:56.731 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:53.557
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88006a0c269, fffff8800791cee0, 0}

Probably caused by : danew.sys ( danew+1269 )

Followup: MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88006a0c269, Address of the instruction which caused the bugcheck
Arg3: fffff8800791cee0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
danew+1269
fffff880`06a0c269 488b7840        mov     rdi,qword ptr [rax+40h]

CONTEXT:  fffff8800791cee0 -- (.cxr 0xfffff8800791cee0)
rax=0000000000000000 rbx=0000000000000088 rcx=fffff8800791d920
rdx=fffffa800688ec10 rsi=fffffa800688ec10 rdi=fffffa800a7ce290
rip=fffff88006a0c269 rsp=fffff8800791d8c0 rbp=0000000000000001
 r8=0000000000000801  r9=fffff8000365d000 r10=fffff88003515d60
r11=fffff8800791d948 r12=fffffa8006918380 r13=0000000000000001
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
danew+0x1269:
fffff880`06a0c269 488b7840        mov     rdi,qword ptr [rax+40h] ds:002b:00000000`00000040=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  razerhid.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88006a0c269

STACK_TEXT:  
fffff880`0791d8c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : danew+0x1269


FOLLOWUP_IP: 
danew+1269
fffff880`06a0c269 488b7840        mov     rdi,qword ptr [rax+40h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  danew+1269

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: danew

IMAGE_NAME:  danew.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ba87dcd

STACK_COMMAND:  .cxr 0xfffff8800791cee0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_danew+1269

BUCKET_ID:  X64_0x3B_danew+1269

Followup: MachineOwner
---------


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\050512-23712-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03819000 PsLoadedModuleList = 0xfffff800`03a5e670
Debug session time: Sat May  5 14:52:01.917 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:49.681
Loading Kernel Symbols
.....................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008eda028, b2000000, 10005}

Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008eda028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8a98 fffff800`03e14a3b : 00000000`00000124 00000000`00000000 fffffa80`08eda028 00000000`b2000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`039a6513 : 00000000`00000001 fffffa80`08edda60 00000000`00000000 fffffa80`08eddab0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`03e14700 : 00000000`00000728 fffffa80`08edda60 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`03e14052 : fffffa80`08edda60 fffff800`00ba8e70 fffffa80`08edda60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`03e13f0d : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`03e07e88 : 00000000`26a8c158 c010ac9a`7f65e54e 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`0389452c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`03894393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000001`4001b685 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`3bc1f860 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`4001b685


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN_PRV

BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN_PRV

Followup: MachineOwner
---------


Loading Dump File [C:\Users\Cardbox\Downloads\050512-52977-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea7650
Debug session time: Sat May  5 18:12:10.458 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:30.956
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800563f010, fffff88003f298c8, ffffffffc00000b5, a}

*** 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+78c8 )

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: fffffa800563f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f298c8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+78c8
fffff880`03f298c8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`009d0a58 fffff880`052db000 : 00000000`00000116 fffffa80`0563f010 fffff880`03f298c8 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`009d0a60 fffff880`052daddb : fffff880`03f298c8 fffffa80`0563f010 fffffa80`07bc47a0 fffffa80`03d33410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`009d0aa0 fffff880`05381f07 : fffffa80`0563f010 00000000`c00000b5 fffffa80`07bc47a0 fffffa80`03d33410 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`009d0ad0 fffff880`053afd5a : fffffa80`ffffffff 00000000`00006c00 fffff880`009d0c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`009d0bb0 fffff880`0537d29e : fffffa80`03d33410 ffffffff`feced300 fffffa80`07bc47a0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`009d0bf0 fffff880`053a9e7a : 00000000`00000000 fffffa80`07bc47a0 00000000`00000080 fffffa80`03d33410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`009d0d00 fffff800`02f79fda : 00000000`0a39bce5 fffffa80`06ec4b60 fffffa80`03c8c890 fffffa80`06ec4b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`009d0d40 fffff800`02cd09c6 : fffff880`009e8180 fffffa80`06ec4b60 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009d0d80 00000000`00000000 : fffff880`009d1000 fffff880`009cb000 fffff880`009d07e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78c8
fffff880`03f298c8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+78c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ebb331c

FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_VRF_IMAGE_atikmpag.sys

Followup: MachineOwner
---------





Edited by pjBSOD - 5/5/12 at 3:52pm
post #9 of 37
Thread Starter 
I reset everything to stock setting and the game ran fine. I dont think it was a bad oc though because i had no problems with my 460 at the same overclock settings

I am gonna try reinstalling the drivers, btw the max heat of the gpu was 94C in furmark (in bf3 was 87C teh last i saw it) but the fan ramped up and went down to 90C also what is the safe temp for the cpu around 65-70? Mine didnt go over 69 on teh hottest core in bf3 before teh bsod

and my mouse drivers are the newest but i will reinstall them just incase

and also i never had an amd gpu in this system so idk why the amd drivers were a problem
Edited by The Pro - 5/5/12 at 4:31pm
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
Old Rust Bucket
(16 items)
 
  
CPUMotherboardGraphicsGraphics
i5 3570k @ 4.6GHz Msi Z77A-GD65 EVGA GTX 480  Gigabyte GTX 480 
RAMHard DriveCoolingOS
G.Skill Ripjaws 8Gb 2x ADATA 128gb SSD Eco Coolit Alc Windows 7 Ultimate 64-bit 
MonitorPowerCaseMouse
ASUS VE276Q 27" 1080p Corsair TX750W CoolerMaster HAF 922 Razer Deathadder 3.5G 
  hide details  
Reply
post #10 of 37
Please keep the system at stock and don't re-overclock for now. Our goal here currently is to see whether or not is was the OC being unstable. Keep me updated.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Battlefield 3 Blue Screen Problems