Bsod page_fault_in_nonpaged_area

CarlTR6 · 05 Feb 2011

I looked at your dump . It is a Verifier enabled dump and blames a Windows system core file which is very unlikely to be the real cause of the crash. Is Verifier still running? I would like to see another two or three Verifier enabled dumps.

Test your RAM with Metest86 carefully following the instructions in this tutorial: RAM - Test with Memtest86+. Run Memtest from a cold boot after your computer has been off for an hour or so. Let it run for at least seven passes; this will take 6 - 8 hours. Post back with your results.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`0309ee50
Debug session time: Sat Feb  5 11:14:09.003 2011 (GMT-5)
System Uptime: 0 days 0:00:08.798
Loading Kernel Symbols
...............................................................
..................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002ef2a83}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

1: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ef2a83, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031090e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02ef2a83 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff88002fce000 -- (.trap 0xfffff88002fce000)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002fceeb0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ef2a83 rsp=fffff88002fce190 rbp=fffff88002fce2e0
 r8=fffff88002fce298  r9=fffff88002fce290 r10=0000000000000002
r11=fffff80002ef1fa0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!IopCompleteRequest+0xae3:
fffff800`02ef2a83 488b09          mov     rcx,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed2469 to fffff80002ed2f00

STACK_TEXT:  
fffff880`02fcdeb8 fffff800`02ed2469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fcdec0 fffff800`02ed10e0 : 00000000`00000000 fffff980`02518ee0 00000000`80000000 fffff800`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fce000 fffff800`02ef2a83 : 00000000`00000002 00000000`00000001 00000000`00000000 fffff880`02fd0000 : nt!KiPageFault+0x260
fffff880`02fce190 fffff800`02eaf92f : 00000000`00000001 00000000`00000000 fffff6fc`50000100 fffff800`00000000 : nt!IopCompleteRequest+0xae3
fffff880`02fce260 fffff800`02eafce7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`02fce2e0 fffff800`02e71a94 : 00000000`0002f880 00000000`00000000 fffff880`02fce590 00000000`002e2471 : nt!KiApcInterrupt+0xd7
fffff880`02fce470 fffff800`02e71943 : fffffa80`027781f0 fffff880`00000011 00000000`00000000 fffff8a0`00000004 : nt!RtlpWalkFrameChain+0x130
fffff880`02fceb10 fffff800`0328f21c : fffffa80`02600000 00000000`0000010c fffffa80`018e5b60 fffff800`0305e440 : nt!RtlWalkFrameChain+0x73
fffff880`02fceb40 fffff800`031f2f75 : fffff8a0`00001a70 fffffa80`018e5b60 00000000`0000010c fffff8a0`00000001 : nt!ExpUpdateDebugInfo+0x1ec
fffff880`02fcebb0 fffff800`031ce968 : fffffa80`00000000 fffff8a0`003f3040 ffff0800`00000000 fffffa80`018f3f00 : nt! ?? ::NNGAKEGL::`string'+0x309aa
fffff880`02fcecc0 fffff800`03170594 : fffff880`02fcef68 00000000`00000000 fffff880`02fcee00 fffff800`02ed10fd : nt!ObOpenObjectByName+0x3f8
fffff880`02fced90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmCreateKey+0x2e1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02ed10e0 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

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

easwar2641993 · 06 Feb 2011

[QUOTE=easwar2641993;1226108]

CarlTR6 said:

I looked at your dump . It is a Verifier enabled dump and blames a Windows system core file which is very unlikely to be the real cause of the crash. Is Verifier still running? I would like to see another two or three Verifier enabled dumps.

Test your RAM with Metest86 carefully following the instructions in this tutorial: RAM - Test with Memtest86+. Run Memtest from a cold boot after your computer has been off for an hour or so. Let it run for at least seven passes; this will take 6 - 8 hours. Post back with your results.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`0309ee50
Debug session time: Sat Feb  5 11:14:09.003 2011 (GMT-5)
System Uptime: 0 days 0:00:08.798
Loading Kernel Symbols
...............................................................
..................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002ef2a83}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

1: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ef2a83, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031090e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02ef2a83 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff88002fce000 -- (.trap 0xfffff88002fce000)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002fceeb0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ef2a83 rsp=fffff88002fce190 rbp=fffff88002fce2e0
 r8=fffff88002fce298  r9=fffff88002fce290 r10=0000000000000002
r11=fffff80002ef1fa0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!IopCompleteRequest+0xae3:
fffff800`02ef2a83 488b09          mov     rcx,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed2469 to fffff80002ed2f00

STACK_TEXT:  
fffff880`02fcdeb8 fffff800`02ed2469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fcdec0 fffff800`02ed10e0 : 00000000`00000000 fffff980`02518ee0 00000000`80000000 fffff800`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fce000 fffff800`02ef2a83 : 00000000`00000002 00000000`00000001 00000000`00000000 fffff880`02fd0000 : nt!KiPageFault+0x260
fffff880`02fce190 fffff800`02eaf92f : 00000000`00000001 00000000`00000000 fffff6fc`50000100 fffff800`00000000 : nt!IopCompleteRequest+0xae3
fffff880`02fce260 fffff800`02eafce7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`02fce2e0 fffff800`02e71a94 : 00000000`0002f880 00000000`00000000 fffff880`02fce590 00000000`002e2471 : nt!KiApcInterrupt+0xd7
fffff880`02fce470 fffff800`02e71943 : fffffa80`027781f0 fffff880`00000011 00000000`00000000 fffff8a0`00000004 : nt!RtlpWalkFrameChain+0x130
fffff880`02fceb10 fffff800`0328f21c : fffffa80`02600000 00000000`0000010c fffffa80`018e5b60 fffff800`0305e440 : nt!RtlWalkFrameChain+0x73
fffff880`02fceb40 fffff800`031f2f75 : fffff8a0`00001a70 fffffa80`018e5b60 00000000`0000010c fffff8a0`00000001 : nt!ExpUpdateDebugInfo+0x1ec
fffff880`02fcebb0 fffff800`031ce968 : fffffa80`00000000 fffff8a0`003f3040 ffff0800`00000000 fffffa80`018f3f00 : nt! ?? ::NNGAKEGL::`string'+0x309aa
fffff880`02fcecc0 fffff800`03170594 : fffff880`02fcef68 00000000`00000000 fffff880`02fcee00 fffff800`02ed10fd : nt!ObOpenObjectByName+0x3f8
fffff880`02fced90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmCreateKey+0x2e1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`02ed10e0 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

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

I got 2 bsods in Windows 7 32bit edition...here are the dumps..

easwar2641993 · 07 Feb 2011

new dumps..
and a very new information..My UPS is APC Back ups ES 500VA...in site it is showing 500VA means 300W...i know i have a cooler master 35OW PSU..so is it a cause??????
I don't have anyother UPS.....is it a helpful information?What if I connect CPU only to direct power??

CarlTR6 · 07 Feb 2011

easwar2641993 said:

I got 2 bsods in Windows 7 32bit edition...here are the dumps..

easwar2641993 said:

new dumps..
and a very new information..My UPS is APC Back ups ES 500VA...in site it is showing 500VA means 300W...i know i have a cooler master 35OW PSU..so is it a cause??????
I don't have anyother UPS.....is it a helpful information?What if I connect CPU only to direct power??

Of the three dumps you uploaded, two are Driver Verifier enabled dumps. Both of these blame ntkrpamp.exe, one of the Windows system core files and highly unlikely to be the cause. Please disable Driver Verifier. When Verifier points to Windows system files, it is usually an indication of a hardware problem.

Your non-Verifier enabled dump is bugcheck 7E and it also blames ntkrpamp.exe.

Your uptimes before the crashes are 7 seconds or less. This can be an indication of a power supply problem. I don't think your UPS is the problem; but you can certainly try plugging your computer directly in to your electrical source and see if it that makes a difference. Do you have another known good PSU you can try?

Some of the files are missing from your uploads - the perfmon report and some others. Is your copy of Windows validated? I don't see any Windows updates in the files I have.

Test your RAM with Metest86 carefully following the instructions in this tutorial: RAM - Test with Memtest86+. Memtest runs outside of Windows. Run Memtest from a cold boot after your computer has been off for an hour or so. Let it run for at least seven passes; this will take 6 - 8 hours. Post back with your results.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c08000 PsLoadedModuleList = 0x82d50810
Debug session time: Sun Feb  6 22:23:37.724 2011 (GMT-5)
System Uptime: 0 days 0:00:07.519
Loading Kernel Symbols
...............................................................
.....................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 82dce3e7, 8771f434, 8771f010}

Probably caused by : ntkrpamp.exe ( nt!LdrRelocateImageWithBias+ad )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82dce3e7, The address that the exception occurred at
Arg3: 8771f434, Exception Record Address
Arg4: 8771f010, Context Record Address

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


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

FAULTING_IP: 
nt!LdrRelocateImageWithBias+ad
82dce3e7 c9              leave

EXCEPTION_RECORD:  8771f434 -- (.exr 0xffffffff8771f434)
ExceptionAddress: 82dce3e7 (nt!LdrRelocateImageWithBias+0x000000ad)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000001
Attempt to read from address 00000001

CONTEXT:  8771f010 -- (.cxr 0xffffffff8771f010)
eax=c000007b ebx=8771f5e0 ecx=8d658000 edx=00000000 esi=00000000 edi=84de3798
eip=82dce3e7 esp=8771f4fc ebp=00000001 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
nt!LdrRelocateImageWithBias+0xad:
82dce3e7 c9              leave
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000001

READ_ADDRESS: GetPointerFromAddress: unable to read from 82d70718
Unable to read MiSystemVaType memory at 82d50160
 00000001 

FOLLOWUP_IP: 
nt!LdrRelocateImageWithBias+ad
82dce3e7 c9              leave

BUGCHECK_STR:  0x7E

LOCK_ADDRESS:  82d6df60 -- (!locks 82d6df60)

Resource @ nt!PiEngineLock (0x82d6df60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x82d6df60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 82dcc078 to 82dce3e7

STACK_TEXT:  
8771f50c 82dcc078 8d63d000 8771f670 82d50810 nt!LdrRelocateImageWithBias+0xad
8771f578 82dcda27 8771f5c4 00000000 00000000 nt!MmLoadSystemImage+0x46d
8771f5f8 82dcc264 8bfbc000 8771f670 00000000 nt!MiResolveImageReferences+0x231
8771f678 82dab2c0 8771f800 00000000 00000000 nt!MmLoadSystemImage+0x659
8771f86c 82db2fe7 00000000 00000000 8771f894 nt!IopLoadDriver+0x386
8771f918 82df7e4e 8b15c108 00000001 8b15c0f4 nt!PipCallDriverAddDeviceQueryRoutine+0x34b
8771f950 82e000a2 00000001 8771fa1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8771f9bc 82db0108 40000000 80000110 8771fa38 nt!RtlQueryRegistryValues+0x31d
8771fa98 82daf876 84d934f0 8771fcc8 00000000 nt!PipCallDriverAddDevice+0x383
8771fc94 82d93a2a 84ded410 84db20d0 8771fcc8 nt!PipProcessDevNodeTree+0x15d
8771fcd4 82c1bf99 84db20d0 82d6be80 84de3798 nt!PiProcessStartSystemDevices+0x6d
8771fd00 82c75f2b 00000000 00000000 84de3798 nt!PnpDeviceActionWorker+0x241
8771fd50 82e1666d 00000001 af23c244 00000000 nt!ExpWorkerThread+0x10d
8771fd90 82cc80d9 82c75e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!LdrRelocateImageWithBias+ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

STACK_COMMAND:  .cxr 0xffffffff8771f010 ; kb

FAILURE_BUCKET_ID:  0x7E_VRF_nt!LdrRelocateImageWithBias+ad

BUCKET_ID:  0x7E_VRF_nt!LdrRelocateImageWithBias+ad

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

Debug session time: Sun Feb  6 22:31:30.566 2011 (GMT-5)
System Uptime: 0 days 0:00:08.361
Loading Kernel Symbols
...............................................................
...................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {16, 2, 0, 82e7ba5b}

Probably caused by : ntkrpamp.exe ( nt!KiSignalNotificationObject+18 )

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: 00000016, 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: 82e7ba5b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82fa7718
Unable to read MiSystemVaType memory at 82f87160
 00000016 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalNotificationObject+18
82e7ba5b 807f1601        cmp     byte ptr [edi+16h],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  00248f68

TRAP_FRAME:  87824a1c -- (.trap 0xffffffff87824a1c)
ErrCode = 00000000
eax=879234d0 ebx=00000000 ecx=00000002 edx=00000000 esi=879234d8 edi=00000000
eip=82e7ba5b esp=87824a90 ebp=87824a9c iopl=0         nv up ei pl nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010217
nt!KiSignalNotificationObject+0x18:
82e7ba5b 807f1601        cmp     byte ptr [edi+16h],1       ds:0023:00000016=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e7ba5b to 82e857eb

STACK_TEXT:  
87824a1c 82e7ba5b badb0d00 00000000 82e85646 nt!KiTrap0E+0x2cf
87824a9c 82ea675d 82f68d20 00000000 8c248f68 nt!KiSignalNotificationObject+0x18
87824ac4 82ee1351 879234d0 00000000 00000000 nt!KeSetEvent+0x98
87824b14 82ee6fa9 00248fa8 87824b40 00000000 nt!IopCompleteRequest+0x23b
87824b60 82e0d90f 00000000 00000000 87824bb4 nt!KiDeliverApc+0x111
87824b80 82e0db29 82f68c01 87824bb4 21e4725c hal!HalpDispatchSoftwareInterrupt+0x49
87824b98 82e0dcc3 1529fb94 87824bb4 82eaf5c1 hal!HalpCheckForSoftwareInterrupt+0x83
87824ba4 82eaf5c1 87824b00 000000d1 87824cdc hal!HalEndSystemInterrupt+0x67
87824ba4 852a1384 87824b00 000000d1 87824cdc nt!KeUpdateSystemTimeAssist+0x5d
87824cdc 85227210 8a964778 8c366e00 879230ec Ntfs!NtfsCommonCreate+0xd87
87824d1c 82eaf10e 87923084 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
87824d1c 82eaf205 87923084 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
87922fe8 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSignalNotificationObject+18
82e7ba5b 807f1601        cmp     byte ptr [edi+16h],1

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiSignalNotificationObject+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0xA_VRF_nt!KiSignalNotificationObject+18

BUCKET_ID:  0xA_VRF_nt!KiSignalNotificationObject+18

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

Debug session time: Mon Feb  7 06:14:07.100 2011 (GMT-5)
System Uptime: 0 days 0:00:06.895
Loading Kernel Symbols
...............................................................
..................
Loading User Symbols
0: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {c, 879234e0, 8e9f8f68, 0}

Probably caused by : ntkrpamp.exe ( nt!IovpCompleteRequest+3c )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000c, Invalid IOSB in IRP at APC IopCompleteRequest (appears to be on
    stack that was unwound)
Arg2: 879234e0, IOSB address
Arg3: 8e9f8f68, IRP address
Arg4: 00000000

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


BUGCHECK_STR:  0xc9_c

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  c

IOSB_ADDRESS: ffffffff879234e0

IRP_ADDRESS:  009f8f68

DEVICE_OBJECT: 8a57b808

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  1

LOCK_ADDRESS:  82fb4f60 -- (!locks 82fb4f60)

Resource @ nt!PiEngineLock (0x82fb4f60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x82fb4f60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8317e9f1 to 82f2bd10

STACK_TEXT:  
879236b0 8317e9f1 000000c9 0000000c 879234e0 nt!KeBugCheckEx+0x1e
879236d0 82ef115d afc42cd8 84dbad48 8e9f8fa8 nt!IovpCompleteRequest+0x3c
87923714 82ef6fa9 009f8fa8 87923740 8792374c nt!IopCompleteRequest+0x4a
87923764 82e7890e 00000000 00000000 00000000 nt!KiDeliverApc+0x111
87923778 82edc35b 00000000 c044b850 8970a02c nt!KiCheckForKernelApcDelivery+0x24
87923868 82f32a2d c044b858 00000000 00000001 nt!MiDeleteSystemPagableVm+0x635
87923880 82f35e36 897000b9 82f35c88 8970a000 nt!MiPurgeSpecialPoolPaged+0x11
87923964 82f6e0db 8970af80 8970af80 00020019 nt!MmFreeSpecialPool+0x3bb
879239c8 82ff6fc2 8970af80 00000000 87bd7a40 nt!ExFreePoolWithTag+0xd6
87923a98 82ff6876 87bd7a40 87923cc8 00000000 nt!PipCallDriverAddDevice+0x23d
87923c94 82fdaa2a 84dc4d58 84dd96a0 87923cc8 nt!PipProcessDevNodeTree+0x15d
87923cd4 82e62f99 84dd96a0 82fb2e80 84dbad48 nt!PiProcessStartSystemDevices+0x6d
87923d00 82ebcf2b 00000000 00000000 84dbad48 nt!PnpDeviceActionWorker+0x241
87923d50 8305d66d 00000001 afc4265c 00000000 nt!ExpWorkerThread+0x10d
87923d90 82f0f0d9 82ebce1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!IovpCompleteRequest+3c
8317e9f1 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!IovpCompleteRequest+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c

BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c

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

easwar2641993 · 07 Feb 2011

CarlTR6 said:

easwar2641993 said:

I got 2 bsods in Windows 7 32bit edition...here are the dumps..

easwar2641993 said:

new dumps..
and a very new information..My UPS is APC Back ups ES 500VA...in site it is showing 500VA means 300W...i know i have a cooler master 35OW PSU..so is it a cause??????
I don't have anyother UPS.....is it a helpful information?What if I connect CPU only to direct power??

Of the three dumps you uploaded, two are Driver Verifier enabled dumps. Both of these blame ntkrpamp.exe, one of the Windows system core files and highly unlikely to be the cause. Please disable Driver Verifier. When Verifier points to Windows system files, it is usually an indication of a hardware problem.

Your non-Verifier enabled dump is bugcheck 7E and it also blames ntkrpamp.exe.

Your uptimes before the crashes are 7 seconds or less. This can be an indication of a power supply problem. I don't think your UPS is the problem; but you can certainly try plugging your computer directly in to your electrical source and see if it that makes a difference. Do you have another known good PSU you can try?

Some of the files are missing from your uploads - the perfmon report and some others. Is your copy of Windows validated? I don't see any Windows updates in the files I have.

Test your RAM with Metest86 carefully following the instructions in this tutorial: RAM - Test with Memtest86+. Memtest runs outside of Windows. Run Memtest from a cold boot after your computer has been off for an hour or so. Let it run for at least seven passes; this will take 6 - 8 hours. Post back with your results.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c08000 PsLoadedModuleList = 0x82d50810
Debug session time: Sun Feb  6 22:23:37.724 2011 (GMT-5)
System Uptime: 0 days 0:00:07.519
Loading Kernel Symbols
...............................................................
.....................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 82dce3e7, 8771f434, 8771f010}

Probably caused by : ntkrpamp.exe ( nt!LdrRelocateImageWithBias+ad )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82dce3e7, The address that the exception occurred at
Arg3: 8771f434, Exception Record Address
Arg4: 8771f010, Context Record Address

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


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

FAULTING_IP: 
nt!LdrRelocateImageWithBias+ad
82dce3e7 c9              leave

EXCEPTION_RECORD:  8771f434 -- (.exr 0xffffffff8771f434)
ExceptionAddress: 82dce3e7 (nt!LdrRelocateImageWithBias+0x000000ad)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000001
Attempt to read from address 00000001

CONTEXT:  8771f010 -- (.cxr 0xffffffff8771f010)
eax=c000007b ebx=8771f5e0 ecx=8d658000 edx=00000000 esi=00000000 edi=84de3798
eip=82dce3e7 esp=8771f4fc ebp=00000001 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
nt!LdrRelocateImageWithBias+0xad:
82dce3e7 c9              leave
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000001

READ_ADDRESS: GetPointerFromAddress: unable to read from 82d70718
Unable to read MiSystemVaType memory at 82d50160
 00000001 

FOLLOWUP_IP: 
nt!LdrRelocateImageWithBias+ad
82dce3e7 c9              leave

BUGCHECK_STR:  0x7E

LOCK_ADDRESS:  82d6df60 -- (!locks 82d6df60)

Resource @ nt!PiEngineLock (0x82d6df60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x82d6df60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 82dcc078 to 82dce3e7

STACK_TEXT:  
8771f50c 82dcc078 8d63d000 8771f670 82d50810 nt!LdrRelocateImageWithBias+0xad
8771f578 82dcda27 8771f5c4 00000000 00000000 nt!MmLoadSystemImage+0x46d
8771f5f8 82dcc264 8bfbc000 8771f670 00000000 nt!MiResolveImageReferences+0x231
8771f678 82dab2c0 8771f800 00000000 00000000 nt!MmLoadSystemImage+0x659
8771f86c 82db2fe7 00000000 00000000 8771f894 nt!IopLoadDriver+0x386
8771f918 82df7e4e 8b15c108 00000001 8b15c0f4 nt!PipCallDriverAddDeviceQueryRoutine+0x34b
8771f950 82e000a2 00000001 8771fa1c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2cd
8771f9bc 82db0108 40000000 80000110 8771fa38 nt!RtlQueryRegistryValues+0x31d
8771fa98 82daf876 84d934f0 8771fcc8 00000000 nt!PipCallDriverAddDevice+0x383
8771fc94 82d93a2a 84ded410 84db20d0 8771fcc8 nt!PipProcessDevNodeTree+0x15d
8771fcd4 82c1bf99 84db20d0 82d6be80 84de3798 nt!PiProcessStartSystemDevices+0x6d
8771fd00 82c75f2b 00000000 00000000 84de3798 nt!PnpDeviceActionWorker+0x241
8771fd50 82e1666d 00000001 af23c244 00000000 nt!ExpWorkerThread+0x10d
8771fd90 82cc80d9 82c75e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!LdrRelocateImageWithBias+ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

STACK_COMMAND:  .cxr 0xffffffff8771f010 ; kb

FAILURE_BUCKET_ID:  0x7E_VRF_nt!LdrRelocateImageWithBias+ad

BUCKET_ID:  0x7E_VRF_nt!LdrRelocateImageWithBias+ad

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

Debug session time: Sun Feb  6 22:31:30.566 2011 (GMT-5)
System Uptime: 0 days 0:00:08.361
Loading Kernel Symbols
...............................................................
...................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {16, 2, 0, 82e7ba5b}

Probably caused by : ntkrpamp.exe ( nt!KiSignalNotificationObject+18 )

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: 00000016, 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: 82e7ba5b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82fa7718
Unable to read MiSystemVaType memory at 82f87160
 00000016 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalNotificationObject+18
82e7ba5b 807f1601        cmp     byte ptr [edi+16h],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  00248f68

TRAP_FRAME:  87824a1c -- (.trap 0xffffffff87824a1c)
ErrCode = 00000000
eax=879234d0 ebx=00000000 ecx=00000002 edx=00000000 esi=879234d8 edi=00000000
eip=82e7ba5b esp=87824a90 ebp=87824a9c iopl=0         nv up ei pl nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010217
nt!KiSignalNotificationObject+0x18:
82e7ba5b 807f1601        cmp     byte ptr [edi+16h],1       ds:0023:00000016=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e7ba5b to 82e857eb

STACK_TEXT:  
87824a1c 82e7ba5b badb0d00 00000000 82e85646 nt!KiTrap0E+0x2cf
87824a9c 82ea675d 82f68d20 00000000 8c248f68 nt!KiSignalNotificationObject+0x18
87824ac4 82ee1351 879234d0 00000000 00000000 nt!KeSetEvent+0x98
87824b14 82ee6fa9 00248fa8 87824b40 00000000 nt!IopCompleteRequest+0x23b
87824b60 82e0d90f 00000000 00000000 87824bb4 nt!KiDeliverApc+0x111
87824b80 82e0db29 82f68c01 87824bb4 21e4725c hal!HalpDispatchSoftwareInterrupt+0x49
87824b98 82e0dcc3 1529fb94 87824bb4 82eaf5c1 hal!HalpCheckForSoftwareInterrupt+0x83
87824ba4 82eaf5c1 87824b00 000000d1 87824cdc hal!HalEndSystemInterrupt+0x67
87824ba4 852a1384 87824b00 000000d1 87824cdc nt!KeUpdateSystemTimeAssist+0x5d
87824cdc 85227210 8a964778 8c366e00 879230ec Ntfs!NtfsCommonCreate+0xd87
87824d1c 82eaf10e 87923084 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
87824d1c 82eaf205 87923084 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
87922fe8 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSignalNotificationObject+18
82e7ba5b 807f1601        cmp     byte ptr [edi+16h],1

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiSignalNotificationObject+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0xA_VRF_nt!KiSignalNotificationObject+18

BUCKET_ID:  0xA_VRF_nt!KiSignalNotificationObject+18

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

Debug session time: Mon Feb  7 06:14:07.100 2011 (GMT-5)
System Uptime: 0 days 0:00:06.895
Loading Kernel Symbols
...............................................................
..................
Loading User Symbols
0: kd> !Analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {c, 879234e0, 8e9f8f68, 0}

Probably caused by : ntkrpamp.exe ( nt!IovpCompleteRequest+3c )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000c, Invalid IOSB in IRP at APC IopCompleteRequest (appears to be on
    stack that was unwound)
Arg2: 879234e0, IOSB address
Arg3: 8e9f8f68, IRP address
Arg4: 00000000

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


BUGCHECK_STR:  0xc9_c

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  c

IOSB_ADDRESS: ffffffff879234e0

IRP_ADDRESS:  009f8f68

DEVICE_OBJECT: 8a57b808

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  1

LOCK_ADDRESS:  82fb4f60 -- (!locks 82fb4f60)

Resource @ nt!PiEngineLock (0x82fb4f60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x82fb4f60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8317e9f1 to 82f2bd10

STACK_TEXT:  
879236b0 8317e9f1 000000c9 0000000c 879234e0 nt!KeBugCheckEx+0x1e
879236d0 82ef115d afc42cd8 84dbad48 8e9f8fa8 nt!IovpCompleteRequest+0x3c
87923714 82ef6fa9 009f8fa8 87923740 8792374c nt!IopCompleteRequest+0x4a
87923764 82e7890e 00000000 00000000 00000000 nt!KiDeliverApc+0x111
87923778 82edc35b 00000000 c044b850 8970a02c nt!KiCheckForKernelApcDelivery+0x24
87923868 82f32a2d c044b858 00000000 00000001 nt!MiDeleteSystemPagableVm+0x635
87923880 82f35e36 897000b9 82f35c88 8970a000 nt!MiPurgeSpecialPoolPaged+0x11
87923964 82f6e0db 8970af80 8970af80 00020019 nt!MmFreeSpecialPool+0x3bb
879239c8 82ff6fc2 8970af80 00000000 87bd7a40 nt!ExFreePoolWithTag+0xd6
87923a98 82ff6876 87bd7a40 87923cc8 00000000 nt!PipCallDriverAddDevice+0x23d
87923c94 82fdaa2a 84dc4d58 84dd96a0 87923cc8 nt!PipProcessDevNodeTree+0x15d
87923cd4 82e62f99 84dd96a0 82fb2e80 84dbad48 nt!PiProcessStartSystemDevices+0x6d
87923d00 82ebcf2b 00000000 00000000 84dbad48 nt!PnpDeviceActionWorker+0x241
87923d50 8305d66d 00000001 afc4265c 00000000 nt!ExpWorkerThread+0x10d
87923d90 82f0f0d9 82ebce1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!IovpCompleteRequest+3c
8317e9f1 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!IovpCompleteRequest+3c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c

BUCKET_ID:  0xc9_c_VRF_nt!IovpCompleteRequest+3c

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

I got this BSOD in a newly formatted reinstalled Windows..thats why no updates..yes this version is genuine..ohh..i really don't know what to do..i spent a lot of money for this and old system..mainly for old system which had the same problem..i have checked memory and no problems were found..ran for 7 or 8 hours and no problems found on errors and ecc errors column..i tried cpu to run from direct current..still bsod came...wen i enabled verifier..

CarlTR6 · 07 Feb 2011

Make sure Verifier is disabled. If you can try another known good PSU, do that. And please do run Memtest again from a cold boot. I suspect a hardware problem of some kind. You have reinstalled Windows; so I don't think Windows is the problem.

easwar2641993 · 07 Feb 2011

CarlTR6 said:

Make sure Verifier is disabled. If you can try another known good PSU, do that. And please do run Memtest again from a cold boot. I suspect a hardware problem of some kind. You have reinstalled Windows; so I don't think Windows is the problem.

OK..I will do it again..But This PSU is new (Cooler Master Elite 310)and I had the same issue with BSOD in my previous system..In that we have used 3 different PSUs..So Can you suspect PSU?While all other components have changed,only the UPS remains same...the very old 500VA that gives 300W of power.My PSU is of 350W..I hope this will be the problem of that UPS is not providing enough current to the power suppy unit..i bought this ups when we had a computer of Intel Pentium 3 with 256mb ram,no graphics card and with old intel 810 motherboard..if my memory is right...

CarlTR6 · 07 Feb 2011

You may well be right. Maybe it is limiting the current. Run without the UPS for a couple of days and see if it makes a difference.

easwar2641993 · 08 Feb 2011

CarlTR6 said:

You may well be right. Maybe it is limiting the current. Run without the UPS for a couple of days and see if it makes a difference.

I connected this directly to the power socket..again it showed same BSOD when verifier was enabled .So it is not the problem with PSU or UPS.Now I opened the case and removed graphics card and ran the system using onboard G41 chipset.Still it showed BSOD when verifier was enabled.Then I put the graphics card and took LAN NIC PCI card and enabled onboard LAN and ran..Again it gave me a BOSD of the same type(c9 and a) when enabled verifier.I reseated the ram,changed the sata wires,power connectors.Still it showed the same BSOD.Very strange isnt it?
Now another thing I noticed is that when I enable verifier and restart the pc,it sometimes boot normally..without any crashes.Or it gives me the BSOD (c9 or a) and reboots the system..OR DURING BOOTING,IT STOPS BOOTING ..SHOWING THE WINDOWS 7 LOGO...NO SPLASHING AND ALL..then I need to reboot the system manually..What does this mean????
I noticed another thing too.When I enable sound drivers and lan drivers only no bsod occurs and computer runs fine..if i enable graphics driver ,bsod or that hang will occur during booting..i uninstalled graphics driver and then ran driver verifier with sound and lan..no bsod or hang at that time...i suspected it would be graphics card issue..so i removed graphics card and made pc to run on onboard graphics...and enabled verifier..at that time too bsod occured...when i disabled verifier for graphics not for others,no bsod or hang..so i suspect this would be the problem of Monitor???how can assume that???

CarlTR6 · 08 Feb 2011

OK, turn off Driver Verifier and let's see how your system runs. Disable the graphics card and the sound card, run your system for a day and see how it does. If it runs smoothly, add the sound card back and run your system. If it still runs smoothly, add the graphics card. If that triggers a problem, try removing the sound card and leaving the graphics card and see what happens. Do all of this with Driver Verifier disabled.