BSOD - Constant

Hey so, another BSOD problem thats been on going for months. I have since it first started, replaced the memory (with same exact type, dual channel 1600mhz corsair memory), now running both sets , 16 gigs total, since that didnt seem to change anything. Ive also just bought a brand new mother board, the ASUS Crosshair V Formula and a new WD 500 GIG HDD. On this motherboard is an AMD PHENOM II X6 1090T and SLId is 2 NVIDIA GEFORCE 450 GTS. Every piece of hardware is basically new and never been over clocked. Formatted several times, updated every piece of hardware with the newest drivers, im out of guesses. I have ran a Windbg and here is what i got from the minibug file i was able to retrieve today as it just did the memory dump again. I dont really understand what im reading other then where it says "Probably caused by : win32k.sys" Does this mean my operating system isnt being installed right, causing it to crash? I format using a USB drive i made bootable with Windows 7, possible files corrupt?

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80024656b3, 2, 0, fffff800032dd01a}

Probably caused by : win32k.sys ( win32k!SetWakeBit+f8 )

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


Any information would help! All post more memory dumps as they happen, which they will!

 

Here is the anaylzed version, didnt know of any other way to post it so hopefully it works for you guys! Thanks

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: fffffa80024656b3, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800032dd01a, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350f0e0
fffffa80024656b3

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeSetEvent+18a
fffff800`032dd01a 0fb6422b movzx eax,byte ptr [rdx+2Bh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: csrss.exe

TRAP_FRAME: fffff88006269870 -- (.trap 0xfffff88006269870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800f906b28 rbx=0000000000000000 rcx=fffffa800f906b28
rdx=fffffa8002465688 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032dd01a rsp=fffff88006269a00 rbp=0000000000000000
r8=fffffa800f465658 r9=fffffa800f906b20 r10=fffff80003267000
r11=fffff880062699d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!KeSetEvent+0x18a:
fffff800`032dd01a 0fb6422b movzx eax,byte ptr [rdx+2Bh] ds:fffffa80`024656b3=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032d8469 to fffff800032d8f00

STACK_TEXT:
fffff880`06269728 fffff800`032d8469 : 00000000`0000000a fffffa80`024656b3 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`06269730 fffff800`032d70e0 : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`06269870 fffff800`032dd01a : fffffa80`0f8fcea0 00000000`00000000 00000000`00000000 fffff880`03288180 : nt!KiPageFault+0x260
fffff880`06269a00 fffff960`0012b1dc : 00000000`00000000 fffff960`00000002 00000000`00000000 fffffa80`02465688 : nt!KeSetEvent+0x18a
fffff880`06269a70 fffff960`00122bb7 : fffff900`c1f036a0 00000000`00000001 00000000`00000004 fffff800`032e504b : win32k!SetWakeBit+0xf8
fffff880`06269aa0 fffff960`001235d4 : 00000000`00000000 fffff960`0033fa90 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x157
fffff880`06269af0 fffff960`000b4714 : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`800003b4 : win32k!RawInputThread+0x9b4
fffff880`06269bc0 fffff960`00133ea6 : fffffa80`00000002 fffff880`06255f40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`06269bf0 fffff800`032d8153 : fffffa80`0f484060 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`06269c20 000007fe`fd103d3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01a4fb68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd103d3a


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!SetWakeBit+f8
fffff960`0012b1dc 488b5c2430 mov rbx,qword ptr [rsp+30h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: win32k!SetWakeBit+f8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

FAILURE_BUCKET_ID: X64_0xA_win32k!SetWakeBit+f8

BUCKET_ID: X64_0xA_win32k!SetWakeBit+f8

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

 

I have also done several memory checks and there are no memory errors.

 

Alright so i did 4 more memory checks, all with just a single card of memory. No errors. Did a disc check which took forever, no errors. Guess ill wait for more minidump files to see if it gets a better description.

 

That first bsod dump you displayed there could very well be a hard drive issue. I had the exact same error and others, multitutes of times on my Gateway laptop. The issue was never resolved ;(, until of course I replaced the hard drive. Also, scan disk only detected an error once.

 

Thats what i was PRAYING for but i took another drive and tried installing windows on it, it blue screened aswell, and i get even get SP1 for windows 7 to install. All sorts of wierd stuff. Ive also swapped video cards (was using 2 for sli) which are brand new, none of that is working either. Im wondering, could this be an operating system error? Most of the windows updates keep failing as well...Well heres another crash dump for ya guys. This one is different.


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


Loading Dump File [C:\Windows\Minidump\121511-29858-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0325f000 PsLoadedModuleList = 0xfffff800`0349ce70
Debug session time: Thu Dec 15 02:33:19.800 2011 (UTC - 6:00)
System Uptime: 0 days 0:07:46.174
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0ffe1c408, 0, fffff8800151e700, 5}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushLsnStreams+e8 )

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

5: 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: fffff8a0ffe1c408, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800151e700, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035070e0
fffff8a0ffe1c408

FAULTING_IP:
Ntfs!NtfsFlushLsnStreams+e8
fffff880`0151e700 4c8b6018 mov r12,qword ptr [rax+18h]

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800334c360 -- (.trap 0xfffff8800334c360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0ffe1c3f0 rbx=0000000000000000 rcx=fffffa800da3c440
rdx=0000000000003fd8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800151e700 rsp=fffff8800334c4f0 rbp=fffff800034745a0
r8=fffffa8011b71518 r9=0000000000000028 r10=fffffa8011b71518
r11=fffffa8011b71000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
Ntfs!NtfsFlushLsnStreams+0xe8:
fffff880`0151e700 4c8b6018 mov r12,qword ptr [rax+18h] ds:c600:fffff8a0`ffe1c408=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000334e7a1 to fffff800032cf5c0

STACK_TEXT:
fffff880`0334c1f8 fffff800`0334e7a1 : 00000000`00000050 fffff8a0`ffe1c408 00000000`00000000 fffff880`0334c360 : nt!KeBugCheckEx
fffff880`0334c200 fffff800`032cd6ae : 00000000`00000000 fffffa80`0da3c440 fffffa80`0ff66500 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x40d4b
fffff880`0334c360 fffff880`0151e700 : 00000000`000004f0 fffffa80`0da3c440 fffff800`034745a0 fffffa80`00000000 : nt!KiPageFault+0x16e
fffff880`0334c4f0 fffff880`014e3131 : fffff880`0334cab0 00000000`00000000 fffff800`03474500 fffff880`0334c601 : Ntfs!NtfsFlushLsnStreams+0xe8
fffff880`0334c590 fffff880`014e47eb : fffff880`0334cab0 fffffa80`0da3c180 fffff880`0334ca00 fffff880`01469600 : Ntfs!NtfsCheckpointVolume+0x1391
fffff880`0334c990 fffff880`014e49ab : fffff880`0334cab0 fffffa80`0da3c180 fffffa80`0da3c188 fffff880`014599c2 : Ntfs!NtfsCheckpointAllVolumesWorker+0x4b
fffff880`0334c9e0 fffff880`014e3a38 : fffff880`0334cab0 00000000`00000000 fffff880`014e47a0 fffff880`0334ccb8 : Ntfs!NtfsForEachVcb+0x167
fffff880`0334ca80 fffff800`032dc7e1 : 00000000`00000000 fffff880`014cfb00 fffff800`034d6101 00000000`00000003 : Ntfs!NtfsCheckpointAllVolumes+0xb8
fffff880`0334ccb0 fffff800`0356f6fa : 00000000`00000000 fffffa80`0c7a3b60 00000000`00000080 fffffa80`0c77b5f0 : nt!ExpWorkerThread+0x111
fffff880`0334cd40 fffff800`032adb46 : fffff880`03288180 fffffa80`0c7a3b60 fffff880`03293040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0334cd80 00000000`00000000 : fffff880`0334d000 fffff880`03347000 fffff880`0334b640 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
Ntfs!NtfsFlushLsnStreams+e8
fffff880`0151e700 4c8b6018 mov r12,qword ptr [rax+18h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: Ntfs!NtfsFlushLsnStreams+e8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d79996d

FAILURE_BUCKET_ID: X64_0x50_Ntfs!NtfsFlushLsnStreams+e8

BUCKET_ID: X64_0x50_Ntfs!NtfsFlushLsnStreams+e8

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