BSOD.. Dump files uploaded

richc46

Vista Guru
Gold Member
You have 2 BC exceptions A and 50
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA :Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
The cause may be defective physical memory or incompatible software,especially remote control and antivirus programs. If the error occurs immediately after installing a device driver or application, try to use Safe Mode to remove the driver or uninstall the program. For more information,

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
A kernel-mode process or driver attempted to access a memory location without authorization. This Stop error is typically caused by faulty or incompatible hardware or software. The name of the offending device driver often appears in the Stop error and can provide an important clue to solving the problem. If the error message points to a specific device or category of devices, try removing or replacing devices in that category. If this Stop error appears during Setup, suspect an incompatible driver, system service, virus scanner, or backup program.

Code:
 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Desktop[1].zip\Mini080310-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 Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x81c42000 PsLoadedModuleList = 0x81d59c70
Debug session time: Tue Aug  3 09:31:29.273 2010 (GMT-4)
System Uptime: 0 days 0:00:33.055
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {14, 2, 0, 81cf5102}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+5 )
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: 00000014, 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: 81cf5102, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from 81d79868
Unable to read MiSystemVaType memory at 81d59420
 00000014 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!MiFindNodeOrParent+5
81cf5102 f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  LPMLCHK.EXE
TRAP_FRAME:  a8e8fa9c -- (.trap 0xffffffffa8e8fa9c)
ErrCode = 00000000
eax=00000000 ebx=88a7c600 ecx=00000000 edx=00000001 esi=856de318 edi=856de318
eip=81cf5102 esp=a8e8fb10 ebp=a8e8fb10 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MiFindNodeOrParent+0x5:
81cf5102 f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h ds:0023:00000014=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 81cf5102 to 81c8ffd9
STACK_TEXT:  
a8e8fa9c 81cf5102 badb0d00 00000001 81e7c85f nt!KiTrap0E+0x2e1
a8e8fb10 81c83c44 a8e8fb24 a8e8fb34 81cc6eed nt!MiFindNodeOrParent+0x5
a8e8fb1c 81cc6eed 00000000 00000200 856de378 nt!MiLocateAddressInTree+0x11
a8e8fb34 81cbca9a 856de2f0 00000001 00000000 nt!MiGetSharedProtos+0x41
a8e8fb6c 81cbb848 00000000 a9897aa8 8cffd028 nt!MiCompleteProtoPteFault+0x30e
a8e8fbbc 81cbc721 00000001 778ed00c 8aa7c678 nt!MiResolveTransitionFault+0x911
a8e8fc08 81cb9bb5 00000001 778ed00c c03bc768 nt!MiResolveProtoPteFault+0x4ac
a8e8fcd0 81cdc266 778ed00c 8aa7c678 00000000 nt!MiDispatchFault+0x9a2
a8e8fd4c 81c8fdd4 00000001 778ed00c 00000001 nt!MmAccessFault+0x1fe6
a8e8fd4c 7788d9cf 00000001 778ed00c 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f9e8 00000000 00000000 00000000 00000000 0x7788d9cf
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiFindNodeOrParent+5
81cf5102 f7401400ffffff  test    dword ptr [eax+14h],0FFFFFF00h
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!MiFindNodeOrParent+5
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4b7d1e08
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  0xA_nt!MiFindNodeOrParent+5
BUCKET_ID:  0xA_nt!MiFindNodeOrParent+5
Followup: MachineOwner
---------

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_Desktop[1].zip\Mini080410-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 Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d17c70
Debug session time: Tue Aug  3 09:32:45.614 2010 (GMT-4)
System Uptime: 0 days 0:00:44.395
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {a8234414, 1, 81cee010, 0}
Probably caused by : ntkrpamp.exe ( nt!ExAllocatePoolWithTag+4ca )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a8234414, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 81cee010, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d37868
Unable to read MiSystemVaType memory at 81d17420
 a8234414 
FAULTING_IP: 
nt!ExAllocatePoolWithTag+4ca
81cee010 895804          mov     dword ptr [eax+4],ebx
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
TRAP_FRAME:  a516d9fc -- (.trap 0xffffffffa516d9fc)
ErrCode = 00000002
eax=a8234410 ebx=83bec0a0 ecx=83bf0124 edx=8fef91a8 esi=83bec034 edi=a8fbf6f0
eip=81cee010 esp=a516da70 ebp=a516dabc 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!ExAllocatePoolWithTag+0x4ca:
81cee010 895804          mov     dword ptr [eax+4],ebx ds:0023:a8234414=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 81c4ddd4 to 81c9838d
STACK_TEXT:  
a516d9e4 81c4ddd4 00000001 a8234414 00000000 nt!MmAccessFault+0x10a
a516d9e4 81cee010 00000001 a8234414 00000000 nt!KiTrap0E+0xdc
a516dabc 81e3ee99 00000001 00000038 6d4e6f49 nt!ExAllocatePoolWithTag+0x4ca
a516db98 81e2d5e1 85318258 00000000 a5f386f0 nt!IopParseDevice+0xc6f
a516dc28 81e3ab62 00000000 a516dc80 00000040 nt!ObpLookupObjectName+0x5a8
a516dc88 81e4029c 012de600 00000000 81e3a401 nt!ObOpenObjectByName+0x13c
a516dcfc 81e06077 012de64c 00100001 012de600 nt!IopCreateFile+0x63b
a516dd44 81c4ac7a 012de64c 00100001 012de600 nt!NtOpenFile+0x2a
a516dd44 76ea5e74 012de64c 00100001 012de600 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
012de8cc 00000000 00000000 00000000 00000000 0x76ea5e74
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!ExAllocatePoolWithTag+4ca
81cee010 895804          mov     dword ptr [eax+4],ebx
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!ExAllocatePoolWithTag+4ca
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4b7d1e08
FAILURE_BUCKET_ID:  0x50_nt!ExAllocatePoolWithTag+4ca
BUCKET_ID:  0x50_nt!ExAllocatePoolWithTag+4ca
Followup: MachineOwner
---------




We will start with the causes common to both

Uninstall your antivirus completely. Use the uninstall tool if one is available from their website. Install Microsoft Security Essentials, Malwarebytes and the Windows Firewall

Unistall any new software that has been put into service prior to the problem.

Take the memtes86 memory test. Make 6 passes and then check the slots with a good stick of ram http://memtest.org/

If these suggestions do not stop the BSOD, just post the new reports and we will give you an analysis. The problems that I have mentioned are the most likely, but other possible causes for your BSOD exist.

Go to the website of your hard drive mfg and take the test for the hard drive.
 
Last edited:

My Computer

System One

  • Name
    Richard
    Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Mouse
    Dell USB 4 button optical
    Keyboard
    Dell USB
    Other Info
    DSL provided by ATT
    Country Flag
    usa
    State/Region Flag
    us connecticut
Top