Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

bsod when trying to run vista32 with 4gb ram


  • Please log in to reply
14 replies to this topic

#1 Kyah

Kyah

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 26 January 2009 - 06:05 PM

Hello,

I am getting really desperate now and hopefully someone will be able to help me out. Basically I've spent whole day trying to get 4gigs of ram work with my windows vista ultimate on asus striker extreme motherboard (680i - bios 1305) without getting blue screens after a couple of minutes (or even seconds!) after entering into windows. Sometimes I can't even enter windows at all! I doubt it's a purely mobo issue since I'd run the very same 4 gigs (even OCed) on XP for about 3 months without any issues at all. Perhaps my motherboard has some major issues with vista ultimate? I use Q6600 if that makes any difference.

Stuff I've noticed:
1) RAM is certainly not faulty. All 4 components run perfectly on their own in any setups (1-3 at a time). I've also tested every single one of them using prime and memtest. They're flawless (corsair xms2 800mhz).
2) I've tried any voltages and any clocks/memory timings - defaults, OCed and even heavily underclocked. Nothing works.
3) I am currently using VIsta Ultimate SP1 which contains patch KB929777. A fairly well-known hotfix for vista 4gb ram crashes. You've guessed it - no results.
4) I even tried to take away some memory from the system through command prompt. Some users reported that this workaround takes the amount of ram below the unfortunate 4gb threshold and the system becomes stable. Unfortunately, it did not work for me (in fact it appeared as if the command itself did not alter the amount of ram present at all ><)

Here's some additional info:

a) I was using Win XP 32 bit for 3 months without a single BSOD even though I was running 4gb ram all the time (very often OCed might I add). Now I have Windows Vista 32 bit. Interestingly enough, it shows 4gb in windows. Before it crashes, that is.
:huh: Vista runs OK with anything less than 4gb. However, 3gb disable dual channel (even on the first pair according to cpu-z) and 2gb is not enough for me with the amount of stuff I run at the same time.
c) I only have these 4 sticks. Mind you, I've just finished testing them all on memtest (6 hours), A+C slots on prime for 6 hours and then B+D slots using the other 2 modules. Once again, after 6 hours of full load on prime95 - no probs. Both memory and the slots are flawless!

It appears that WInDBG has some issues with opening the crash files but this is what I did recover. Perhaps you'll be able to draw some conclusions from it. Thanks in advance! (or perhaps you will be able to advise me to use some alternative means of opening this dump since this one does not look very comprehensible. I am a complete noob so please try to keep it straightforward :huh:)

Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


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


MODULE_NAME: nt

FAULTING_MODULE: 81c18000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt+0x70b4e
807f0bec 81c52085 badb0d00 00000000 00000000 nt+0x5aae4
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt+0x3a085
807f0cd8 81c4dcda 00000000 84417740 00000000 nt+0x35ed1
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt+0x35cda
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt+0x1a86ad
00000000 00000000 00000000 00000000 00000000 nt+0x8f686


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+70b4e
81c88b4e 837c242800 cmp dword ptr [esp+28h],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+70b4e

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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



Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x81c18000 PsLoadedModuleList = 0x81d25930
Debug session time: Sun Jan 25 19:44:09.599 2009 (GMT+0)
System Uptime: 0 days 0:05:51.721
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 9c0000, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
***

BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:38 AM

Posted 26 January 2009 - 06:55 PM

Please read the information in this post: http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/
and ensure that the symbol file path is correct (from step 5 in the above).
Then re-run the analysis and ensure that you're connected to the internet when running it.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Kyah

Kyah
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 27 January 2009 - 04:41 PM

Hello Usama! After some fighting with the debugger (I am a complete noob!) I've come up with this.
By the way: What is really really weird (apart from all modules working perfectly) is the fact that I actually got all 4 gigs to work but I had to switch them to Corsair, Corsair / Random Memory, Random Memory. In this state, all 4 gigs passed 12 hours of prime95! However, since Asus Striker Extreme has ABAB layout this disabled dual channel option which crippled my performance to 4,5 on vista experience despite all modules running at 800mhz (and over if I care to OC them). Thus, this is not really an acceptable solution.


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.x86fre.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x81c18000 PsLoadedModuleList = 0x81d25930
Debug session time: Sun Jan 25 19:44:09.599 2009 (GMT+0)
System Uptime: 0 days 0:05:51.721
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 9c0000, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+dc )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 009c0000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: 807f0bec -- (.trap 0xffffffff807f0bec)
ErrCode = 00000000
eax=009c0000 ebx=81d25e00 ecx=009c0000 edx=00000000 esi=84a92000 edi=881ab940
eip=81c52085 esp=807f0c60 ebp=807f0c98 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiProcessWorkingSets+0x21e:
81c52085 8b08 mov ecx,dword ptr [eax] ds:0023:009c0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c72ae4 to 81c88b4e

STACK_TEXT:
807f0bd4 81c72ae4 00000000 009c0000 00000000 nt!MmAccessFault+0x158
807f0bd4 81c52085 00000000 009c0000 00000000 nt!KiTrap0E+0xdc
807f0c98 81c4ded1 00000002 807f0cb4 00000001 nt!MiProcessWorkingSets+0x21e
807f0cd8 81c4dcda 00000000 84417740 00000000 nt!MmWorkingSetManager+0x19a
807f0d7c 81dc06ad 00000000 64867fea 00000000 nt!KeBalanceSetManager+0x12a
807f0dc0 81ca7686 81c4dbb0 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
81c72ae4 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 47918b0a

FAILURE_BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID: 0x1a_41287_nt!KiTrap0E+dc

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

#4 Kyah

Kyah
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 27 January 2009 - 05:02 PM

And this is a different dump from one day into numerous attempts to fix the problem just by switching over ram:


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81c0e000 PsLoadedModuleList = 0x81d1b930
Debug session time: Sun Jan 25 23:53:57.742 2009 (GMT+0)
System Uptime: 0 days 0:04:25.490
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {b2bffff8, 2, 1, 81c845a1}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+f1 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: b2bffff8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 81c845a1, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d3a6d8
Unable to read MiSystemVaType memory at 81d1b2e0
b2bffff8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+f1
81c845a1 895110 mov dword ptr [ecx+10h],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: 8cf588b8 -- (.trap 0xffffffff8cf588b8)
ErrCode = 00000002
eax=83e023c4 ebx=ffffffff ecx=b2bfffe8 edx=00085d1b esi=83627a88 edi=01ffffff
eip=81c845a1 esp=8cf5892c ebp=8cf5893c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!MiUnlinkFreeOrZeroedPage+0xf1:
81c845a1 895110 mov dword ptr [ecx+10h],edx ds:0023:b2bffff8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c845a1 to 81c68c84

STACK_TEXT:
8cf588b8 81c845a1 badb0d00 00085d1b 00000000 nt!KiTrap0E+0x2ac
8cf5893c 81c84fc6 0006c51b 83986888 87fac080 nt!MiUnlinkFreeOrZeroedPage+0xf1
8cf5896c 81c50b38 0000011b 87f268a0 91eb2110 nt!MiRemoveAnyPage+0xa9
8cf589f0 81de5d67 849972c8 00000000 a9a2d010 nt!MiPfPutPagesInTransition+0x5c5
8cf58a20 81da872e 00000001 8cf58a6c 00000000 nt!MmPrefetchPages+0x101
8cf58aac 81da8c69 00f58aec 8cf58be4 00000001 nt!PfpPrefetchFilesTrickle+0x1a3
8cf58b00 81da8f06 a9b04000 e32b0d17 8cf58bf8 nt!PfpPrefetchRequestPerform+0x295
8cf58b54 81dc89d4 8cf58be4 81cfd801 e32b0a5b nt!PfpPrefetchRequest+0x16e
8cf58c18 81dc2abf 02ebf684 00000014 81cfd801 nt!PfSetSuperfetchInformation+0x182
8cf58d50 81c6597a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
8cf58d50 77639a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02ebf69c 00000000 00000000 00000000 00000000 0x77639a94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+f1
81c845a1 895110 mov dword ptr [ecx+10h],edx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+f1

BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+f1

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: b2bffff8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 81c845a1, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d3a6d8
Unable to read MiSystemVaType memory at 81d1b2e0
b2bffff8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+f1
81c845a1 895110 mov dword ptr [ecx+10h],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: 8cf588b8 -- (.trap 0xffffffff8cf588b8)
ErrCode = 00000002
eax=83e023c4 ebx=ffffffff ecx=b2bfffe8 edx=00085d1b esi=83627a88 edi=01ffffff
eip=81c845a1 esp=8cf5892c ebp=8cf5893c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!MiUnlinkFreeOrZeroedPage+0xf1:
81c845a1 895110 mov dword ptr [ecx+10h],edx ds:0023:b2bffff8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c845a1 to 81c68c84

STACK_TEXT:
8cf588b8 81c845a1 badb0d00 00085d1b 00000000 nt!KiTrap0E+0x2ac
8cf5893c 81c84fc6 0006c51b 83986888 87fac080 nt!MiUnlinkFreeOrZeroedPage+0xf1
8cf5896c 81c50b38 0000011b 87f268a0 91eb2110 nt!MiRemoveAnyPage+0xa9
8cf589f0 81de5d67 849972c8 00000000 a9a2d010 nt!MiPfPutPagesInTransition+0x5c5
8cf58a20 81da872e 00000001 8cf58a6c 00000000 nt!MmPrefetchPages+0x101
8cf58aac 81da8c69 00f58aec 8cf58be4 00000001 nt!PfpPrefetchFilesTrickle+0x1a3
8cf58b00 81da8f06 a9b04000 e32b0d17 8cf58bf8 nt!PfpPrefetchRequestPerform+0x295
8cf58b54 81dc89d4 8cf58be4 81cfd801 e32b0a5b nt!PfpPrefetchRequest+0x16e
8cf58c18 81dc2abf 02ebf684 00000014 81cfd801 nt!PfSetSuperfetchInformation+0x182
8cf58d50 81c6597a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
8cf58d50 77639a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02ebf69c 00000000 00000000 00000000 00000000 0x77639a94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+f1
81c845a1 895110 mov dword ptr [ecx+10h],edx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+f1

BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+f1

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: b2bffff8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 81c845a1, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d3a6d8
Unable to read MiSystemVaType memory at 81d1b2e0
b2bffff8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+f1
81c845a1 895110 mov dword ptr [ecx+10h],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: 8cf588b8 -- (.trap 0xffffffff8cf588b8)
ErrCode = 00000002
eax=83e023c4 ebx=ffffffff ecx=b2bfffe8 edx=00085d1b esi=83627a88 edi=01ffffff
eip=81c845a1 esp=8cf5892c ebp=8cf5893c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!MiUnlinkFreeOrZeroedPage+0xf1:
81c845a1 895110 mov dword ptr [ecx+10h],edx ds:0023:b2bffff8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c845a1 to 81c68c84

STACK_TEXT:
8cf588b8 81c845a1 badb0d00 00085d1b 00000000 nt!KiTrap0E+0x2ac
8cf5893c 81c84fc6 0006c51b 83986888 87fac080 nt!MiUnlinkFreeOrZeroedPage+0xf1
8cf5896c 81c50b38 0000011b 87f268a0 91eb2110 nt!MiRemoveAnyPage+0xa9
8cf589f0 81de5d67 849972c8 00000000 a9a2d010 nt!MiPfPutPagesInTransition+0x5c5
8cf58a20 81da872e 00000001 8cf58a6c 00000000 nt!MmPrefetchPages+0x101
8cf58aac 81da8c69 00f58aec 8cf58be4 00000001 nt!PfpPrefetchFilesTrickle+0x1a3
8cf58b00 81da8f06 a9b04000 e32b0d17 8cf58bf8 nt!PfpPrefetchRequestPerform+0x295
8cf58b54 81dc89d4 8cf58be4 81cfd801 e32b0a5b nt!PfpPrefetchRequest+0x16e
8cf58c18 81dc2abf 02ebf684 00000014 81cfd801 nt!PfSetSuperfetchInformation+0x182
8cf58d50 81c6597a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
8cf58d50 77639a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02ebf69c 00000000 00000000 00000000 00000000 0x77639a94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+f1
81c845a1 895110 mov dword ptr [ecx+10h],edx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+f1

BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+f1

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: b2bffff8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 81c845a1, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d3a6d8
Unable to read MiSystemVaType memory at 81d1b2e0
b2bffff8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+f1
81c845a1 895110 mov dword ptr [ecx+10h],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: 8cf588b8 -- (.trap 0xffffffff8cf588b8)
ErrCode = 00000002
eax=83e023c4 ebx=ffffffff ecx=b2bfffe8 edx=00085d1b esi=83627a88 edi=01ffffff
eip=81c845a1 esp=8cf5892c ebp=8cf5893c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!MiUnlinkFreeOrZeroedPage+0xf1:
81c845a1 895110 mov dword ptr [ecx+10h],edx ds:0023:b2bffff8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c845a1 to 81c68c84

STACK_TEXT:
8cf588b8 81c845a1 badb0d00 00085d1b 00000000 nt!KiTrap0E+0x2ac
8cf5893c 81c84fc6 0006c51b 83986888 87fac080 nt!MiUnlinkFreeOrZeroedPage+0xf1
8cf5896c 81c50b38 0000011b 87f268a0 91eb2110 nt!MiRemoveAnyPage+0xa9
8cf589f0 81de5d67 849972c8 00000000 a9a2d010 nt!MiPfPutPagesInTransition+0x5c5
8cf58a20 81da872e 00000001 8cf58a6c 00000000 nt!MmPrefetchPages+0x101
8cf58aac 81da8c69 00f58aec 8cf58be4 00000001 nt!PfpPrefetchFilesTrickle+0x1a3
8cf58b00 81da8f06 a9b04000 e32b0d17 8cf58bf8 nt!PfpPrefetchRequestPerform+0x295
8cf58b54 81dc89d4 8cf58be4 81cfd801 e32b0a5b nt!PfpPrefetchRequest+0x16e
8cf58c18 81dc2abf 02ebf684 00000014 81cfd801 nt!PfSetSuperfetchInformation+0x182
8cf58d50 81c6597a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
8cf58d50 77639a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02ebf69c 00000000 00000000 00000000 00000000 0x77639a94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+f1
81c845a1 895110 mov dword ptr [ecx+10h],edx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+f1

BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+f1

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

#5 Kyah

Kyah
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 27 January 2009 - 05:11 PM

And the last one. Sorry for this spam but it seems to me that they are slightly different. Hence, I'm posting them just to be safe....


Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81c15000 PsLoadedModuleList = 0x81d22930
Debug session time: Sun Jan 25 21:56:09.274 2009 (GMT+0)
System Uptime: 0 days 0:00:26.393
Loading Kernel Symbols
...WARNING: mcupdate_GenuineIntel overlaps kdcom
............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {558b0000, 2, 1, 89975242}

Probably caused by : ecache.sys ( ecache!EcCacheIoWatchdog+304 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 558b0000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 89975242, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'mcupdate_GenuineIntel' and 'kdcom' overlap

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d416d8
Unable to read MiSystemVaType memory at 81d222e0
558b0000

CURRENT_IRQL: 2

FAULTING_IP:
ecache!EcCacheIoWatchdog+304
89975242 8901 mov dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 8c502cac -- (.trap 0xffffffff8c502cac)
ErrCode = 00000002
eax=97aae852 ebx=00000000 ecx=558b0000 edx=af770700 esi=898105d0 edi=89980500
eip=89975242 esp=8c502d20 ebp=8c502d7c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
ecache!EcCacheIoWatchdog+0x304:
89975242 8901 mov dword ptr [ecx],eax ds:0023:558b0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 89975242 to 81c6fc84

STACK_TEXT:
8c502cac 89975242 badb0d00 af770700 81fc65b0 nt!KiTrap0E+0x2ac
8c502d7c 81dbd6d5 89980500 7e3fb60f 00000000 ecache!EcCacheIoWatchdog+0x304
8c502dc0 81ca46de 89974f3e 89980500 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
ecache!EcCacheIoWatchdog+304
89975242 8901 mov dword ptr [ecx],eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ecache!EcCacheIoWatchdog+304

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ecache

IMAGE_NAME: ecache.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918fb7

FAILURE_BUCKET_ID: 0xD1_ecache!EcCacheIoWatchdog+304

BUCKET_ID: 0xD1_ecache!EcCacheIoWatchdog+304

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 558b0000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 89975242, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'mcupdate_GenuineIntel' and 'kdcom' overlap

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d416d8
Unable to read MiSystemVaType memory at 81d222e0
558b0000

CURRENT_IRQL: 2

FAULTING_IP:
ecache!EcCacheIoWatchdog+304
89975242 8901 mov dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 8c502cac -- (.trap 0xffffffff8c502cac)
ErrCode = 00000002
eax=97aae852 ebx=00000000 ecx=558b0000 edx=af770700 esi=898105d0 edi=89980500
eip=89975242 esp=8c502d20 ebp=8c502d7c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
ecache!EcCacheIoWatchdog+0x304:
89975242 8901 mov dword ptr [ecx],eax ds:0023:558b0000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 89975242 to 81c6fc84

STACK_TEXT:
8c502cac 89975242 badb0d00 af770700 81fc65b0 nt!KiTrap0E+0x2ac
8c502d7c 81dbd6d5 89980500 7e3fb60f 00000000 ecache!EcCacheIoWatchdog+0x304
8c502dc0 81ca46de 89974f3e 89980500 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
ecache!EcCacheIoWatchdog+304
89975242 8901 mov dword ptr [ecx],eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ecache!EcCacheIoWatchdog+304

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ecache

IMAGE_NAME: ecache.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918fb7

FAILURE_BUCKET_ID: 0xD1_ecache!EcCacheIoWatchdog+304

BUCKET_ID: 0xD1_ecache!EcCacheIoWatchdog+304

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

#6 Kyah

Kyah
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 27 January 2009 - 06:15 PM

Hi, while running memtest one last time with all 4 gigs I've googled some info that there is a problem with 680i mobos (especially from asus) trying to run 4gigs in dual channel on vista. However, nobody really seems to have a universal solution for it. I've already played with memory timings, mhz and tried voltages from 1,8 to even 2,2v. Perhaps there is some workaround? I don't really need the 4gigs. I'll be fine with 3 but I do need dual channel for optimal gaming performance :huh:

#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:38 AM

Posted 27 January 2009 - 09:21 PM

Most of these seem to be associated with msnmsgr.exe - can you stop that process from loading and see if it improves things. The 680i chipset has had some issues and I've seen recommendations to only run 2 gB on them also. Good luck with this one!

Parameter 1 means: 0x41287 - Internal memory management structures are corrupted. To further investigate the cause, a kernel memory dump file is needed
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#8 Kyah

Kyah
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 28 January 2009 - 06:00 PM

thanks usasma. I will try to obtain that kernel dump this weekend (as soon as I google how to do it lol :D)
Do you reckon updating chipset drivers (or bios) might help? I am really afraid of tinkering with bios though. Playing with OS is one thing, but mobo...
Asus striker extreme is known for its numerous bugs ;(

#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:38 AM

Posted 28 January 2009 - 06:59 PM

Start
Control Panel (classic view)
System
Advanced Settings (in left sidebar)
Advanced tab
Startup and Recovery System Settings button
In the next window, towards the bottom, under System Failure...Write debugging information
Click on the dropdown box and select "Kernel memory dump"
The default location will be C:\Windows\memory.dmp

This will be a large file and will contain a lot of stuff! I'm not real familiar with them, but will give it a go.
If it's just flat too big to post, shoot me a PM.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#10 Kyah

Kyah
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 29 January 2009 - 03:38 PM

here's the baddie:


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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81c10000 PsLoadedModuleList = 0x81d1d930
Debug session time: Tue Jan 27 18:03:27.872 2009 (GMT+0)
System Uptime: 0 days 0:01:28.994
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {3a01b8f8, 2, 1, 81fbdff9}

Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+2ac )

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

3: kd> !analyze -v
*******************************************************************************
* *
* 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: 3a01b8f8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 81fbdff9, address which referenced memory

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


WRITE_ADDRESS: 3a01b8f8

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+29
81fbdff9 8902 mov dword ptr [edx],eax

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 807a4abc -- (.trap 0xffffffff807a4abc)
ErrCode = 00000002
eax=807a4b40 ebx=83e93828 ecx=87968bc8 edx=3a01b8f8 esi=a1de3ba8 edi=87968b94
eip=81fbdff9 esp=807a4b30 ebp=807a4b4c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29:
81fbdff9 8902 mov dword ptr [edx],eax ds:0023:3a01b8f8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81fbdff9 to 81c6ac84

STACK_TEXT:
807a4abc 81fbdff9 badb0d00 3a01b8f8 9a2a0700 nt!KiTrap0E+0x2ac
807a4b2c 81c569e8 87968b88 a1de3ba8 00000000 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29
807a4b4c 8a4b130c 87968b94 00000001 8b01e700 nt!ExAcquireResourceSharedLite+0x21
807a4b84 8a424cbc 87968b94 32509276 a1de3ba8 Ntfs!NtfsRemoveHashEntry+0x22
807a4bd8 8a49ace0 87a92890 87968498 a1de3918 Ntfs!NtfsTeardownFromLcb+0x102
807a4c28 8a422bde 87a92890 a1de3a08 a1de3ba8 Ntfs!NtfsTeardownStructures+0xed
807a4c50 8a4a0b66 87a92890 a1de3a08 a1de3ba8 Ntfs!NtfsDecrementCloseCounts+0xad
807a4cb0 8a4af1d4 87a92890 a1de3a08 a1de3918 Ntfs!NtfsCommonClose+0x4da
807a4d44 81c6b68e 00000000 00000000 83e93828 Ntfs!NtfsFspClose+0x117
807a4d7c 81db86d5 00000000 5990ea3f 00000000 nt!ExpWorkerThread+0xfd
807a4dc0 81c9f6de 81c6b591 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+2ac
81c6ac84 833da046d38100 cmp dword ptr [nt!KiFreezeFlag (81d346a0)],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTrap0E+2ac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

FAILURE_BUCKET_ID: 0xA_nt!KiTrap0E+2ac

BUCKET_ID: 0xA_nt!KiTrap0E+2ac

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

3: kd> !analyze -v
*******************************************************************************
* *
* 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: 3a01b8f8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 81fbdff9, address which referenced memory

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


WRITE_ADDRESS: 3a01b8f8

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+29
81fbdff9 8902 mov dword ptr [edx],eax

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 807a4abc -- (.trap 0xffffffff807a4abc)
ErrCode = 00000002
eax=807a4b40 ebx=83e93828 ecx=87968bc8 edx=3a01b8f8 esi=a1de3ba8 edi=87968b94
eip=81fbdff9 esp=807a4b30 ebp=807a4b4c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29:
81fbdff9 8902 mov dword ptr [edx],eax ds:0023:3a01b8f8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81fbdff9 to 81c6ac84

STACK_TEXT:
807a4abc 81fbdff9 badb0d00 3a01b8f8 9a2a0700 nt!KiTrap0E+0x2ac
807a4b2c 81c569e8 87968b88 a1de3ba8 00000000 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29
807a4b4c 8a4b130c 87968b94 00000001 8b01e700 nt!ExAcquireResourceSharedLite+0x21
807a4b84 8a424cbc 87968b94 32509276 a1de3ba8 Ntfs!NtfsRemoveHashEntry+0x22
807a4bd8 8a49ace0 87a92890 87968498 a1de3918 Ntfs!NtfsTeardownFromLcb+0x102
807a4c28 8a422bde 87a92890 a1de3a08 a1de3ba8 Ntfs!NtfsTeardownStructures+0xed
807a4c50 8a4a0b66 87a92890 a1de3a08 a1de3ba8 Ntfs!NtfsDecrementCloseCounts+0xad
807a4cb0 8a4af1d4 87a92890 a1de3a08 a1de3918 Ntfs!NtfsCommonClose+0x4da
807a4d44 81c6b68e 00000000 00000000 83e93828 Ntfs!NtfsFspClose+0x117
807a4d7c 81db86d5 00000000 5990ea3f 00000000 nt!ExpWorkerThread+0xfd
807a4dc0 81c9f6de 81c6b591 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+2ac
81c6ac84 833da046d38100 cmp dword ptr [nt!KiFreezeFlag (81d346a0)],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTrap0E+2ac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

FAILURE_BUCKET_ID: 0xA_nt!KiTrap0E+2ac

BUCKET_ID: 0xA_nt!KiTrap0E+2ac

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

3: kd> !analyze -v
*******************************************************************************
* *
* 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: 3a01b8f8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 81fbdff9, address which referenced memory

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


WRITE_ADDRESS: 3a01b8f8

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+29
81fbdff9 8902 mov dword ptr [edx],eax

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 807a4abc -- (.trap 0xffffffff807a4abc)
ErrCode = 00000002
eax=807a4b40 ebx=83e93828 ecx=87968bc8 edx=3a01b8f8 esi=a1de3ba8 edi=87968b94
eip=81fbdff9 esp=807a4b30 ebp=807a4b4c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29:
81fbdff9 8902 mov dword ptr [edx],eax ds:0023:3a01b8f8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81fbdff9 to 81c6ac84

STACK_TEXT:
807a4abc 81fbdff9 badb0d00 3a01b8f8 9a2a0700 nt!KiTrap0E+0x2ac
807a4b2c 81c569e8 87968b88 a1de3ba8 00000000 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29
807a4b4c 8a4b130c 87968b94 00000001 8b01e700 nt!ExAcquireResourceSharedLite+0x21
807a4b84 8a424cbc 87968b94 32509276 a1de3ba8 Ntfs!NtfsRemoveHashEntry+0x22
807a4bd8 8a49ace0 87a92890 87968498 a1de3918 Ntfs!NtfsTeardownFromLcb+0x102
807a4c28 8a422bde 87a92890 a1de3a08 a1de3ba8 Ntfs!NtfsTeardownStructures+0xed
807a4c50 8a4a0b66 87a92890 a1de3a08 a1de3ba8 Ntfs!NtfsDecrementCloseCounts+0xad
807a4cb0 8a4af1d4 87a92890 a1de3a08 a1de3918 Ntfs!NtfsCommonClose+0x4da
807a4d44 81c6b68e 00000000 00000000 83e93828 Ntfs!NtfsFspClose+0x117
807a4d7c 81db86d5 00000000 5990ea3f 00000000 nt!ExpWorkerThread+0xfd
807a4dc0 81c9f6de 81c6b591 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+2ac
81c6ac84 833da046d38100 cmp dword ptr [nt!KiFreezeFlag (81d346a0)],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTrap0E+2ac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

FAILURE_BUCKET_ID: 0xA_nt!KiTrap0E+2ac

BUCKET_ID: 0xA_nt!KiTrap0E+2ac

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

#11 Kyah

Kyah
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 29 January 2009 - 04:13 PM

and a brand new one from today.... is it the same?


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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x81c34000 PsLoadedModuleList = 0x81d41930
Debug session time: Thu Jan 29 20:44:42.154 2009 (GMT+0)
System Uptime: 0 days 0:00:09.883
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {72cffff6, 2, 0, 81caa4c5}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+15 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* 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: 72cffff6, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 81caa4c5, address which referenced memory

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


READ_ADDRESS: 72cffff6

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+15
81caa4c5 0fb6460e movzx eax,byte ptr [esi+0Eh]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8d717bf0 -- (.trap 0xffffffff8d717bf0)
ErrCode = 00000002
eax=80cf3000 ebx=92081000 ecx=00000400 edx=00000000 esi=80cf2000 edi=92081000
eip=81c9dd13 esp=8d717c64 ebp=8d717c6c iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210212
nt!memcpy+0x33:
81c9dd13 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

LAST_CONTROL_TRANSFER: from 81caa4c5 to 81c8ec84

STACK_TEXT:
8d7179d0 81caa4c5 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
8d717a54 81caafc6 ff55ffff 000002ec 81d42220 nt!MiUnlinkFreeOrZeroedPage+0x15
8d717a84 81cbe74c 000002ec 86a14030 c0248204 nt!MiRemoveAnyPage+0xa9
8d717abc 81caf62e 00000001 92081000 c0248204 nt!MiResolveDemandZeroFault+0x411
8d717b68 81ca580e 92081000 00000000 00000000 nt!MiDispatchFault+0x9a6
8d717bd8 81c8eab4 00000001 92081000 00000000 nt!MmAccessFault+0xdca
8d717bd8 81c9dd13 00000001 92081000 00000000 nt!KiTrap0E+0xdc
8d717c6c 81d7b586 92081000 80cf2000 00001000 nt!memcpy+0x33
8d717c94 81d7bb70 8b026008 00000000 86a14030 nt!HvpDropPagedBins+0x86
8d717d7c 81ddc6d5 00000003 76d12ede 00000000 nt!CmpLoadHiveThread+0x351
8d717dc0 81cc36de 81d7b81e 00000003 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+15
81caa4c5 0fb6460e movzx eax,byte ptr [esi+0Eh]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+15

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+15

BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+15

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

3: kd> !analyze -v
*******************************************************************************
* *
* 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: 72cffff6, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 81caa4c5, address which referenced memory

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


READ_ADDRESS: 72cffff6

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+15
81caa4c5 0fb6460e movzx eax,byte ptr [esi+0Eh]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8d717bf0 -- (.trap 0xffffffff8d717bf0)
ErrCode = 00000002
eax=80cf3000 ebx=92081000 ecx=00000400 edx=00000000 esi=80cf2000 edi=92081000
eip=81c9dd13 esp=8d717c64 ebp=8d717c6c iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210212
nt!memcpy+0x33:
81c9dd13 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

LAST_CONTROL_TRANSFER: from 81caa4c5 to 81c8ec84

STACK_TEXT:
8d7179d0 81caa4c5 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
8d717a54 81caafc6 ff55ffff 000002ec 81d42220 nt!MiUnlinkFreeOrZeroedPage+0x15
8d717a84 81cbe74c 000002ec 86a14030 c0248204 nt!MiRemoveAnyPage+0xa9
8d717abc 81caf62e 00000001 92081000 c0248204 nt!MiResolveDemandZeroFault+0x411
8d717b68 81ca580e 92081000 00000000 00000000 nt!MiDispatchFault+0x9a6
8d717bd8 81c8eab4 00000001 92081000 00000000 nt!MmAccessFault+0xdca
8d717bd8 81c9dd13 00000001 92081000 00000000 nt!KiTrap0E+0xdc
8d717c6c 81d7b586 92081000 80cf2000 00001000 nt!memcpy+0x33
8d717c94 81d7bb70 8b026008 00000000 86a14030 nt!HvpDropPagedBins+0x86
8d717d7c 81ddc6d5 00000003 76d12ede 00000000 nt!CmpLoadHiveThread+0x351
8d717dc0 81cc36de 81d7b81e 00000003 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+15
81caa4c5 0fb6460e movzx eax,byte ptr [esi+0Eh]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+15

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+15

BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+15

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

3: kd> !analyze -v
*******************************************************************************
* *
* 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: 72cffff6, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 81caa4c5, address which referenced memory

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


READ_ADDRESS: 72cffff6

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlinkFreeOrZeroedPage+15
81caa4c5 0fb6460e movzx eax,byte ptr [esi+0Eh]

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8d717bf0 -- (.trap 0xffffffff8d717bf0)
ErrCode = 00000002
eax=80cf3000 ebx=92081000 ecx=00000400 edx=00000000 esi=80cf2000 edi=92081000
eip=81c9dd13 esp=8d717c64 ebp=8d717c6c iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210212
nt!memcpy+0x33:
81c9dd13 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

LAST_CONTROL_TRANSFER: from 81caa4c5 to 81c8ec84

STACK_TEXT:
8d7179d0 81caa4c5 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
8d717a54 81caafc6 ff55ffff 000002ec 81d42220 nt!MiUnlinkFreeOrZeroedPage+0x15
8d717a84 81cbe74c 000002ec 86a14030 c0248204 nt!MiRemoveAnyPage+0xa9
8d717abc 81caf62e 00000001 92081000 c0248204 nt!MiResolveDemandZeroFault+0x411
8d717b68 81ca580e 92081000 00000000 00000000 nt!MiDispatchFault+0x9a6
8d717bd8 81c8eab4 00000001 92081000 00000000 nt!MmAccessFault+0xdca
8d717bd8 81c9dd13 00000001 92081000 00000000 nt!KiTrap0E+0xdc
8d717c6c 81d7b586 92081000 80cf2000 00001000 nt!memcpy+0x33
8d717c94 81d7bb70 8b026008 00000000 86a14030 nt!HvpDropPagedBins+0x86
8d717d7c 81ddc6d5 00000003 76d12ede 00000000 nt!CmpLoadHiveThread+0x351
8d717dc0 81cc36de 81d7b81e 00000003 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiUnlinkFreeOrZeroedPage+15
81caa4c5 0fb6460e movzx eax,byte ptr [esi+0Eh]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiUnlinkFreeOrZeroedPage+15

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b7e8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+15

BUCKET_ID: 0xA_nt!MiUnlinkFreeOrZeroedPage+15

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

#12 Blue Coconut

Blue Coconut

  • Members
  • 65 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:the right side ocean, NC
  • Local time:09:38 AM

Posted 29 January 2009 - 05:17 PM

Hello Kyah.

I have been reading through your post and I have just a couple questions.

1. Did you build this machine. If so, what method did you use for burn in.

2. If you didn't build it, what is the manufacturer name. Lots of HP's use the ASUS platform, plus it would be great if u say its an HP. LOL

3. If you know the first 5 digits of the serial number of the system board. **( but this is not important if you don't know it)** It will give some info on diagnostics.

4. When this started, what all did you do to the machine before the problem started. IE, replaced ram, updated BIOS, made a small CMOS change, left your tongue hanging on your lip to long. Anything else other than replacing the RAM and firing it up. No need to get real detailed, just basically, "what all did you do just before the problem started".

Thanks...

{USASMA....} This is your baby, It just caught my eye and started reading through it. I will not interject unless I see an obvious problem.
Ever tried landing a city block? Its a rush one cannot describe.

#13 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:38 AM

Posted 29 January 2009 - 08:04 PM

Blue Coconut - feel free to contribute. The more "hands" on the problem, the more likely we are to reach a solution quickly.

Kyah - they all appear to be the same error. Vista insists it's a driver issues although each of the errors points to Windows system files (this isn't uncommon).

The next step here is to prepare your system for a disaster - as the tools that we use can cause the system not to boot. Backup all of your important data, ensure that you have the recovery disks on hand, make sure that you can boot into the Recovery Environment from the disk, create a System Restore point, and anything else that you can think of. Once all that's ready, post back and we'll start working.

I propose that we use Driver Verifier to verify the drivers on your system. The desired result of using Driver Verifier is that the faulty driver will cause an immediate BSOD. Unfortunately, if this is a driver that's loaded early in the boot sequence, you may not be able to boot into Windows. If not, we'll try Safe Mode, and if that fails we'll try the Recovery Environment.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#14 Kyah

Kyah
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:02:38 PM

Posted 30 January 2009 - 10:29 AM

Brrr sounds scary O.o
Regarding Coconut's questions, yes I did build this machine with a friend about 3 months ago but the problem only started occuring once I replaced xp with vista ultimate (and ONLY when I use 4 gigs in dual channel which is really really weird...)
I am sorry I'm still a major noob and I don't know what you mean by 'burning in'. Is this checking if particular components work before I include them in the system? If so, I haven't done anything in this department. Like I said though, everything worked perfectly with xp no matter how much ram I used.
This relates to your last question too. Basically, all I did was swapping the OS...

Which driver's removal would possibly render me unable to enter windows? Regardless, I'll try the driver verifier method you've suggested. Then again, any non-windows integral drivers I've installed are asus xonar DX and nvidia gpu drivers so I'll just start with these first at some point during this weekend!

#15 Blue Coconut

Blue Coconut

  • Members
  • 65 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:the right side ocean, NC
  • Local time:09:38 AM

Posted 30 January 2009 - 10:58 AM

Good morning Kyah,

First, before we go any further, I 110% agree with usasma, are you prepared for a disaster. OR if yo have just built this machine, do you have all software cd's and OEM os dc. And mainly, is your HDD backed up with all your personal data. Now if you havent loaded personal stuff, documents pics etc and not worried then thats fine.

OK.

My first question is you said you are now using Vista, How did you upgrade. Which Vista upgrade did you use, I see it says ultimate. Can you tell me exactly what it says on the disk. u'll have to excuse me I am at work and back and forth from the test bench and my desk. Is vista an upgrade or is it a complete install. I do see one problem we can address just going through your post, dealing with your interrupts, but I want to narrow this down a little bit.

also if you can get the machine to boot into CMOS, please go in and record your settings as they are now. If you have a problem with this no biggie.

second, can you enter into the safe mode screen, not mode, but the enter screen to select which safe mode to load. Oh and are you running any other OS within your HDD. say do you have more than one way to boot....XP, server, vista etc.

I will be with you

please be patient
Ever tried landing a city block? Its a rush one cannot describe.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users