BlueScreening

First off, 2 things. Thanks in advance for any assistance. And apologies if I miss providing some information.

My computer has been running great for about a year now. It was initially running 7RC, but has been running 7 Home Premium since it arrived in the mail when they released it.

Recently, the last week I would say, my computer has been getting bluescreens. A couple per day on average I would say. I haven't made any hardware changes. What happened before the very first one was that I tried the Arkham Asylum demo on Steam. and before it would run it installed directx and some run times. I of course already have direct x. I also installed about 20 other games as I got the Eidos pack that Steam had on for sale. I am wondering why each game feels that it is necessary to install direct x before it is run, even when it is already on the system. I am also wondering if this possibly has anything to do with it, conflicting directx files or something, though the crashes don't only occur when I am playing a game.

Other things I should note as recent software changes. I set Windows Live Messenger to run in Vista compatibility mode so that it would move back to the notification area. I also installed Windows Sticky Notes Hider (a forum member here has developed it), and NeXus dock. However I turned off both the dock and the sitcky hider application and still recieved bluescreens.

Other then that I can't think of any changes other then Windows Update installed some windows live games thing, required by Batman Arkham Asylum.

There are no updates available to me on windows update and I sent all of the reports to microsoft.

Just a couple more notes, I noticed in my DxDiag that my keyboard is listed 3 times. Also, Windows 7 does not seem to like my Blackberry as it connects and disconnects at random (or at least the screen turns on and off as if it has).

I've attached the minidump files and my dxdiag report. My system specs are filled out in my profile.

Thanks.

Oh PS.
Here are the critical events from the event viewer.

- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2009-12-28T14:34:08.267200000Z

EventRecordID 11673

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jim-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 30
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0


- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2009-12-28T13:13:30.296800000Z

EventRecordID 11541

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jim-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 59
BugcheckParameter1 0xc0000005
BugcheckParameter2 0xfffff80002ac74a7
BugcheckParameter3 0xfffff88005e24e30
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0


- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2009-12-25T10:39:27.683200000Z

EventRecordID 11144

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jim-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 59
BugcheckParameter1 0xc0000005
BugcheckParameter2 0xfffff80002ad209e
BugcheckParameter3 0xfffff880074ed140
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0


- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2009-12-24T17:22:48.697600000Z

EventRecordID 10729

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jim-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 59
BugcheckParameter1 0xc0000005
BugcheckParameter2 0xfffff80002b09c22
BugcheckParameter3 0xfffff8800832a110
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0


- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2009-12-23T19:11:26.058000000Z

EventRecordID 10466

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jim-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 30
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff80002a6aaed
BugcheckParameter3 0x0
BugcheckParameter4 0xffffffffffffffff
SleepInProgress false
PowerButtonTimestamp 0


- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2009-12-23T17:09:26.429200000Z

EventRecordID 10321

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jim-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 25
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa8006b7c370
BugcheckParameter3 0xfffffa80cf151068
BugcheckParameter4 0xfffffa8006b7c370
SleepInProgress false
PowerButtonTimestamp 0

- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2009-12-23T08:08:19.917600000Z

EventRecordID 10116

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jim-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 30
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff8800c65eb30
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress false
PowerButtonTimestamp 0



EDIT:
The latest is yet another bugcheck code

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF880049A6C65
BCP3: FFFFF880057BEBA8
BCP4: FFFFF880057BE400
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\122809-28173-01.dmp
C:\Users\Jim\AppData\Local\Temp\WER-45801-0.sysdata.xml
- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2009-12-28T17:42:54.154800000Z

EventRecordID 11826

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jim-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 126
BugcheckParameter1 0xffffffffc0000005
BugcheckParameter2 0xfffff880049a6c65
BugcheckParameter3 0xfffff880057beba8
BugcheckParameter4 0xfffff880057be400
SleepInProgress false
PowerButtonTimestamp 0




Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c86e50
Debug session time: Mon Dec 28 09:41:32.374 2009 (GMT-8)
System Uptime: 0 days 3:07:33.469
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff880049a6c65, fffff880057beba8, fffff880057be400}

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+184c65 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880049a6c65, The address that the exception occurred at
Arg3: fffff880057beba8, Exception Record Address
Arg4: fffff880057be400, Context Record Address

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


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

FAULTING_IP:
nvlddmkm+184c65
fffff880`049a6c65 493b4808 cmp rcx,qword ptr [r8+8]

EXCEPTION_RECORD: fffff880057beba8 -- (.exr 0xfffff880057beba8)
ExceptionAddress: fffff880049a6c65 (nvlddmkm+0x0000000000184c65)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff880057be400 -- (.cxr 0xfffff880057be400)
rax=000000011eac1000 rbx=0000000000000000 rcx=000000011eac1000
rdx=fffff880057bee20 rsi=00000000c1d0000f rdi=0000000000000000
rip=fffff880049a6c65 rsp=fffff880057bede8 rbp=fffffa8003d00260
r8=03f872bf15f60885 r9=000000011eac1000 r10=fffffa800515a010
r11=fffff880057beea0 r12=fffffa80051e5c40 r13=fffffa8005d0aa90
r14=0000000000000000 r15=fffffa8005140010
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nvlddmkm+0x184c65:
fffff880`049a6c65 493b4808 cmp rcx,qword ptr [r8+8] ds:002b:03f872bf`15f6088d=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

FOLLOWUP_IP:
nvlddmkm+184c65
fffff880`049a6c65 493b4808 cmp rcx,qword ptr [r8+8]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88004dbce00 to fffff880049a6c65

STACK_TEXT:
fffff880`057bede8 fffff880`04dbce00 : 00000000`00000000 00000000`00000000 fffffa80`05335000 00000000`00000000 : nvlddmkm+0x184c65
fffff880`057bedf0 fffff880`04c6aff8 : fffffa80`05a0b1b0 00000000`00000000 fffffa80`00000000 fffff880`04969db0 : nvlddmkm+0x59ae00
fffff880`057bee20 fffff880`04c6c0ed : fffffa80`05a0b1b0 fffffa80`051e5c40 00000000`00000000 00000000`c1d0000f : nvlddmkm+0x448ff8
fffff880`057beec0 fffff880`04b5a271 : fffff880`057bf260 fffffa80`051e5c40 fffff880`057bf260 fffffa80`05a0b1b0 : nvlddmkm+0x44a0ed
fffff880`057bf130 fffff880`049c51d3 : fffff880`057bf260 00000001`1eac1000 00000000`00000001 fffff880`00000000 : nvlddmkm+0x338271
fffff880`057bf170 fffff880`049c4547 : fffffa80`05a0b1b0 fffff880`00000000 fffff880`00000000 00000000`00000000 : nvlddmkm+0x1a31d3
fffff880`057bf1c0 fffff880`049c4aee : fffff880`057bf4e0 00000000`00000000 00000000`00000000 00000000`00001000 : nvlddmkm+0x1a2547
fffff880`057bf210 fffff880`049c4bd9 : fffffa80`060cde10 fffffa80`05440000 fffff880`057bf440 00000000`00001000 : nvlddmkm+0x1a2aee
fffff880`057bf2c0 fffff880`04963d27 : fffffa80`060cde10 fffff880`057bf440 fffff880`057bf470 fffff880`057bf440 : nvlddmkm+0x1a2bd9
fffff880`057bf300 fffff880`048e00e0 : fffff880`057bf440 fffff880`048d740f fffffa80`060cde10 00000000`00000001 : nvlddmkm+0x141d27
fffff880`057bf3a0 fffff880`048e1ebf : fffff880`048e008a 00000000`00000002 fffffa80`054477a0 fffff880`048a2fe8 : nvlddmkm+0xbe0e0
fffff880`057bf420 fffff880`048c8031 : 00000000`00000002 fffffa80`060cde10 00000000`c1d0000f 00000000`00100000 : nvlddmkm+0xbfebf
fffff880`057bf470 fffff880`048caec6 : fffffa80`060cde10 fffffa80`05440000 00000000`00000000 fffffa80`05251b20 : nvlddmkm+0xa6031
fffff880`057bf610 fffff880`048c3f45 : 00000000`00000000 00000000`00100000 fffffa80`05251b20 fffffa80`05441740 : nvlddmkm+0xa8ec6
fffff880`057bf760 fffff880`04e324c2 : fffff880`0a8a0000 00000000`00000000 00000000`00000000 fffffa80`05440000 : nvlddmkm+0xa1f45
fffff880`057bf790 fffff880`052eb9ac : 00000000`0006fad2 fffff8a0`0ae3b010 00000000`00000100 fffffa80`06c69480 : nvlddmkm+0x6104c2
fffff880`057bf860 fffff880`03ead272 : fffff8a0`0ae3b010 fffff8a0`0ae3b010 00000000`00000000 fffffa80`06157000 : dxgkrnl!DXGADAPTER_DdiBuildPagingBuffer+0x50
fffff880`057bf890 fffff880`03ead0f6 : 00000000`00000000 00000000`00000100 fffffa80`06157000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x106
fffff880`057bfa20 fffff880`03eb6642 : fffffa80`05d1c830 00000000`00000000 00000000`00000100 fffff800`02ac2052 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e
fffff880`057bfa90 fffff880`03eb5889 : fffff8a0`0ae3b010 00000000`00000000 fffffa80`075b4300 fffffa80`05d1c830 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a
fffff880`057bfae0 fffff880`03ea825d : fffff8a0`0ae3b010 fffffa80`06157000 fffffa80`075b43a0 fffffa80`06157000 : dxgmms1!VIDMM_APERTURE_SEGMENT::EvictResource+0xf9
fffff880`057bfb30 fffff880`03ea3358 : fffffa80`0520b9f0 fffffa80`06e71ee0 00000000`00000000 fffff880`057bfca0 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x96d
fffff880`057bfc50 fffff880`03ec116d : fffffa80`00000000 fffffa80`06109410 00000000`0000000f fffff880`03ec2f09 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`057bfca0 fffff880`03ec03f8 : fffff880`009ebec0 fffffa80`06b05010 00000000`00000000 fffffa80`06109410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`057bfcd0 fffff880`03ebfe96 : 00000000`00000000 fffffa80`06b90920 00000000`00000080 fffffa80`06109410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`057bfd00 fffff800`02d5e166 : 00000000`1c09f39d fffffa80`05d1cb60 fffffa80`03c6e890 fffffa80`05d1cb60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`057bfd40 fffff800`02a99486 : fffff880`009e7180 fffffa80`05d1cb60 fffff880`009f1f40 fffff880`0126da90 : nt!PspSystemThreadStartup+0x5a
fffff880`057bfd80 00000000`00000000 : fffff880`057c0000 fffff880`057ba000 fffff880`057bf930 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nvlddmkm+184c65

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56

STACK_COMMAND: .cxr 0xfffff880057be400 ; kb

FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+184c65

BUCKET_ID: X64_0x7E_nvlddmkm+184c65

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

The memory dump analysis that you posted points to your video drivers. Please replace the current one's with one freshly downloaded from the nVidia website.

Then, please try this stuff:

H/W Diagnostics:
Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

One of the BSOD's points to a networking component - so I'd suggest replacing the networking drivers on your system.

Here's a list of the older drivers on your system. Please don't use Windows Update or the Update drivers function in Device Manager to update them. Please visit the support website of the device/program manufacturer for the latest version:

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005
NCREMOTEPCI.SYS Mon Sep 11 16:47:50 2006
athrxusb athrxusb.sys Mon Jan 29 07:57:10 2007
RimUsb_AMD64.sys Mon May 14 12:06:16 2007
nvm62x64.sys Fri Oct 17 17:01:06 2008

Summary of the BSOD's:

Code:

BugCheck 1E, {ffffffffc0000005, fffff80002a6aaed, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiDereferenceControlAreaPfn+5d )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 19, {3, fffffa8006b7c370, fffffa80cf151068, fffffa8006b7c370}
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {ffffffffc0000005, fffff8800c65eb30, 0, 0}
Probably caused by : NETIO.SYS ( NETIO!IndexListEnum+45 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff80002b09c22, fffff8800832a110, 0}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff80002ad209e, fffff880074ed140, 0}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+e )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff80002ac74a7, fffff88005e24e30, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+1cd )

Video drivers didn't do the trick, will continue to check others.
No new drivers available for the network adapter (athrxusb athrxusb.sys)

rimusb is the blackberry driver, and I don't think a new one is available. I'll just leave the blackberry unplugged... It's easier that way then trying to go through the blackberry website, I can't believe people actually like that piece of junk.

I turned off physx in my nvidia control panel, will see if that helps.


EDIT:
http://forums.eidosgames.com/showthread.php?t=97206
I am pretty sure it is something to do with Batman Arkham Asylum causing my blue screen issues, whether it is physx or the version of direct x it installed.

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
Debug session time: Wed Dec 30 14:32:53.754 2009 (GMT-8)
System Uptime: 0 days 10:51:11.666
Loading Kernel Symbols
...............................................................
................................................Page 11ff7e not present in the dump file. Type ".hh dbgerr004" for details
................
.............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002d631c8, 0, ffffffffffffffff}

Page 11ff7e not present in the dump file. Type ".hh dbgerr004" for details
Page 11ff7e not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details
Page 11ff7e not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MiRelocateImageAgain+48 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002d631c8, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

Page 11ff7e not present in the dump file. Type ".hh dbgerr004" for details
Page 11ff7e not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details
Page 11ff7e not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details

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

FAULTING_IP:
nt!MiRelocateImageAgain+48
fffff800`02d631c8 f0480fba2e00 lock bts qword ptr [rsi],0

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002abea17 to fffff80002a7ef00

STACK_TEXT:
fffff880`0961f928 fffff800`02abea17 : 00000000`0000001e ffffffff`c0000005 fffff800`02d631c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0961f930 fffff800`02a7e542 : fffff880`09620108 ffffffff`ffffffff fffff880`096201b0 28bc2bfb`27d80ace : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`0961ffd0 fffff800`02a7ce4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`096201b0 fffff800`02d631c8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`09620340 fffff800`02d770ae : 00000000`00000004 00000000`01000000 00000000`00000000 00000000`00000000 : nt!MiRelocateImageAgain+0x48
fffff880`09620390 fffff800`02d6c893 : fffff880`096205f0 00000000`00000000 fffff880`09620698 fffff880`096205e8 : nt!MmCreateSection+0x302
fffff880`096205a0 fffff800`02edb573 : 00000000`00000000 fffff8a0`09c0c540 00000000`00000000 00000000`00000001 : nt!NtCreateSection+0x162
fffff880`09620620 fffff800`02edbb01 : 00000000`00000000 fffff8a0`09c0c540 fffffa80`04162160 fffff880`00000060 : nt!PfpFileBuildReadSupport+0x163
fffff880`09620710 fffff800`02ee3c1e : fffff8a0`00000000 fffff8a0`00000037 fffff8a0`000000c3 fffff8a0`00000000 : nt!PfpPrefetchFilesTrickle+0x121
fffff880`09620810 fffff800`02ee47b7 : 00000000`00000000 fffff880`09620ca0 fffff880`09620a08 fffff8a0`01889730 : nt!PfpPrefetchRequestPerform+0x30e
fffff880`09620960 fffff800`02ef0d8e : fffff880`09620a08 00000000`00000001 fffffa80`041a5460 00000000`00000000 : nt!PfpPrefetchRequest+0x176
fffff880`096209d0 fffff800`02ef54be : 00000000`00000000 00000000`01b9f4c0 00000000`0000004f fffffa80`046a4001 : nt!PfSetSuperfetchInformation+0x1ad
fffff880`09620ab0 fffff800`02a7e153 : fffffa80`03f14b60 00000000`00000000 00000000`0a06c280 00000000`0a06c2a0 : nt!NtSetSystemInformation+0xb91
fffff880`09620c20 00000000`76e215aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01b9f498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e215aa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRelocateImageAgain+48
fffff800`02d631c8 f0480fba2e00 lock bts qword ptr [rsi],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!MiRelocateImageAgain+48

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x1E_nt!MiRelocateImageAgain+48

BUCKET_ID: X64_0x1E_nt!MiRelocateImageAgain+48

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