Occasional Blue Screen, Problem error 'X64_IP_MISALIGNED'

Hi,
I have uploaded the latest crash dump file which occurred when i was casually browsing the internet. Just after changing to a new tab the computer blue screened. I've been having other crashes lately but think most of them can be attributed to the new and very faulty battlefield game. This kind of infrequent bluescreen happens when i am doing very little with the computer.
I'd greatly appreciate some help!



edit:
here is the debugging tools text for the crash in question:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffff89, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030895c2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cb100
ffffffffffffff89

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiCommitThreadWait+1a2
fffff800`030895c2 184889 sbb byte ptr [rax-77h],cl

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff880009a9860 -- (.trap 0xfffff880009a9860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880009a99b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030895c2 rsp=fffff880009a99f0 rbp=fffffa800c749b50
r8=0000000000000000 r9=0000000000000000 r10=000000000002448e
r11=fffff880031d7101 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiCommitThreadWait+0x1a2:
fffff800`030895c2 184889 sbb byte ptr [rax-77h],cl ds:ffffffff`ffffff89=??
Resetting default scope

MISALIGNED_IP:
nt!KiCommitThreadWait+1a2
fffff800`030895c2 184889 sbb byte ptr [rax-77h],cl

LAST_CONTROL_TRANSFER: from fffff80003093169 to fffff80003093bc0

STACK_TEXT:
fffff880`009a9718 fffff800`03093169 : 00000000`0000000a ffffffff`ffffff89 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9720 fffff800`03091de0 : 00000000`00000000 fffff800`03096e53 00000000`00000000 fffffa80`0c749b50 : nt!KiBugCheckDispatch+0x69
fffff880`009a9860 fffff800`030895c2 : 00000000`00000052 fffffa80`0c749b48 00000000`00000000 fffff800`032ce500 : nt!KiPageFault+0x260
fffff880`009a99f0 fffff800`030564fb : fffffa80`0c749b50 00000000`00000000 fffffa80`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1a2
fffff880`009a9a80 fffff800`030569ea : fffffa80`0c5d1400 00000000`0000007f 00000000`00000000 00000000`00000000 : nt!KeWaitForGate+0xfb
fffff880`009a9ad0 fffff800`033302ea : fffffa80`0c749b50 00000000`00000080 fffffa80`0c749040 00000000`00000282 : nt!MmZeroPageThread+0x2ed
fffff880`009a9c00 fffff800`030848e6 : fffff800`0320ee80 fffffa80`0c749b50 fffff800`0321ccc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9c40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9870 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiCommitThreadWait+1a2
fffff800`030895c2 184889 sbb byte ptr [rax-77h],cl

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiCommitThreadWait+1a2

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
---------

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffff89, 2, 1, fffff800030895c2}

Probably caused by : hardware ( nt!KiCommitThreadWait+1a2 )

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

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Let us see a screenshot of the furmark window before you close it.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

It seems that furmark is not rendering images rightly ..... it looks like something like this .....

Attachment 300709

The furry thing is not properly rendered.

Now, go for another test. Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

ConorMcEnery said:

thanks for the reply
I ran furmark again for 15 mins with a max temp of 78.
i enabled driver verifier as instructed and upon restarting there was an immediate bluescreen with a nvlddmkm.sys error, which has been the main culprit in most of my BSODs..
I have tried uninstalling and reinstalling the GPU driver many times, and have used Guru3D driver sweeper to do a fresh install aswel. I am currently running the very latest beta driver.

Points noted.

And unfortunately I dont know any driver version that works good with GTX 770. You may try the drivers on a trial and error basis:

• 320.49 WHQL
• 327.23 WHQL
• 331.58 WHWL
• 331.65 WHQL
• 331.82 WHQL

Get them from Drivers - Download NVIDIA Drivers

Do a clean install on all of them. Uninstall the previously installed driver first.
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
• Download the target WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Lengthy process, but the only stable version of nvidia is 314.22 lately, which does not support 700 series GPU.

Let us know your results. Cause it will help us to build the knowledge to troubleshoot 700 series GPUs.

EDIT: What is the wattage of your Power Supply? Those heavy duty GPUs cannot work with inadequate or failing PSUs at all.