BSOD when playing BF3. ntoskrnl.exe seems to be causing it?

[deltax]

Hello all,

Relative computer noob that somehow built his own computer a few years ago lol. Recently I have been getting the dreaded BSOD almost everytime I play BF3, and I am finally deciding to try to get some help on the matter. The causes seem to vary however I've noticed that ntoskrnl.exe seems to be the culprit more often than not. Again, I'm somewhat of a computer noob so I'm not too sure what to really make of all the dmp files, to say I'm confused would be a huge understatement. I've uploaded my dmp file with this post, and if anyone could chime in on what I should do I would greatly appreciate it.

Thanks!

As far as system specs
Gigabyte 880UD-3H
Phenom 1055t
HD 6870
8gb ram
Windows 7 64bit OEM version

 

[Saurabh A]

Hi deltax,

Majority of the crashes seem to be caused by the 'ntkrnlmp.exe' driver.
Driver Description: NT Kernel & System - Different versions/date stamps according to OS and system specifications
The driver installs with 'Windows updates'.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4A, {75732e09, 2, 0, fffff8800a3daca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

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

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 0000000075732e09, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff8800a3daca0, 0

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


PROCESS_NAME:  AvastSvc.exe

BUGCHECK_STR:  RAISED_IRQL_FAULT

Another driver that seems to be causing trouble is 'dxgmms1.sys' (DirectX Graphics MMS), which also installs itself via 'Windows Updates'.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800533ecee, fffff880021bd6a8, fffff880021bcf00}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800533ecee, The address that the exception occurred at
Arg3: fffff880021bd6a8, Exception Record Address
Arg4: fffff880021bcf00, Context Record Address

The following 'Windows update' has failed to install numerous times; which may have an impact on the system performance.

2013-02-13	11:46:29:806	 396	ee8	Misc	WARNING: DownloadFileInternal failed for http://download.microsoft.com/v9/1/windowsupdate/redir/muv4wuredir.cab: error 0x80190194
2013-02-13	11:46:29:806	 396	ee8	Misc	Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:

Is the processor overclocked? Could not pull up the detail.

3: kd> !sysinfo cpuspeed
sysinfo: unknown error 80004005

Please try the following steps:
1. Try using the system in 'Safe Mode'; if the system does not crash in this diagnostic environment, a 'driver' is likely to be the root cause.
2. Uninstall 'Avast' & 'Tuneup Utilities 2012' from the system. Restart it and update 'Windows' to install 'Microsoft Security Essentials'; recheck results.

Also follow instructions in the tutorial to share the findings: http://www.sevenforums.com/windows-updates-activation/234159-windows-genuine-activation-issue-posting-instructions.html

Do reply with the details; will take it forward from there.