BSoD is becoming more and more frequent

Last 3 day i am havin random BSoD.

Well it should be a BSoD but the screen becomes pixcelerate with dark red and black picxels. and after few seconds mice pointer rezezs to with HDD and i have to restart my PC.

Today it happened 3 time for about 40 min that i was working on my 6860.

here are the dump if you have any ide what this means at event viewer.
The following boot-start or system-start driver(s) failed to load:
archlp

Still have to download windows debug tools to see what is inside the dump.

if someone out there has it please post them as TXT file.

 

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Shared\Dump\082910-25178-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\windows\symbols* Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Sun Aug 29 14:53:45.407 2010 (GMT+2)
System Uptime: 0 days 0:53:27.670
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88002f15000, 1, fffff8800fe781ce, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+751ce )

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

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

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f050e0
fffff88002f15000

FAULTING_IP:
nvlddmkm+751ce
fffff880`0fe781ce 42891488 mov dword ptr [rax+r9*4],edx

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880054a2050 -- (.trap 0xfffff880054a2050)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002ef9000 rbx=0000000000000000 rcx=fffffa8006671030
rdx=0000000000040084 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800fe781ce rsp=fffff880054a21e8 rbp=0000000000000000
r8=0000000000000000 r9=0000000000007000 r10=0000000000000000
r11=fffffa80052b6000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x751ce:
fffff880`0fe781ce 42891488 mov dword ptr [rax+r9*4],edx ds:79a4:fffff880`02f15000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002d4df14 to fffff80002ccd740

STACK_TEXT:
fffff880`054a1ee8 fffff800`02d4df14 : 00000000`00000050 fffff880`02f15000 00000000`00000001 fffff880`054a2050 : nt!KeBugCheckEx
fffff880`054a1ef0 fffff800`02ccb82e : 00000000`00000001 fffffa80`06671000 fffff880`054a2400 fffff800`02cd3652 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`054a2050 fffff880`0fe781ce : fffff880`0fe7f536 00000000`00000000 fffff880`08c66000 fffff800`02e47e80 : nt!KiPageFault+0x16e
fffff880`054a21e8 fffff880`0fe7f536 : 00000000`00000000 fffff880`08c66000 fffff800`02e47e80 00000000`00000000 : nvlddmkm+0x751ce
fffff880`054a21f0 00000000`00000000 : fffff880`08c66000 fffff800`02e47e80 00000000`00000000 fffff880`08c66000 : nvlddmkm+0x7c536


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+751ce
fffff880`0fe781ce 42891488 mov dword ptr [rax+r9*4],edx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nvlddmkm+751ce

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c37918e

FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+751ce

BUCKET_ID: X64_0x50_nvlddmkm+751ce

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

0: kd> !analyze -v


Well as i can see its from Nvidia drivers. drivers 258.xx crashed a lot. one i was getting black screens now with 258.96 i get this.

I have to downgrade at 257.xx and see what will change singe i had no problem with 257 series.