Ik heb een paar dagen geleden een nieuwe pc aangeschaft. En nu al drie keer een BSOD gekregen tijdens verschillende handelingen. Een keer tijdens een installatie en een keer tijdens het spelen van een spel. Natuurlijk ben ik erg gefrustreerd hierdoor. Ik heb Vista home premium. Na zoeken op het probleemrapport kwam ik uit op een Poolse site en na vertaling ben ik nog niets wijzer.
Nu heb ik de minidump laten converteren en hier is het resultaat (Ik heb wat enters eruit gehaald)
* Bugcheck Analysis
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ba7ffffc, 2, 0, 8187784c}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+a29 )
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: ba7ffffc, 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: 8187784c, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from 81979868
Unable to read MiSystemVaType memory at 81959420
ba7ffffc
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiIdentifyPfn+a29
8187784c 8b7918 mov edi,dword ptr [ecx+18h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: 8a9f07e4 -- (.trap 0xffffffff8a9f07e4)
ErrCode = 00000000
eax=01ffffff ebx=84754cc0 ecx=ba7fffe4 edx=01ffffff esi=00000058 edi=01ffffff
eip=8187784c esp=8a9f0858 ebp=8a9f08b8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!MiIdentifyPfn+0xa29:
8187784c 8b7918 mov edi,dword ptr [ecx+18h] ds:0023:ba7ffffc=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8187784c to 8189cd24
STACK_TEXT:
8a9f07e4 8187784c badb0d00 01ffffff 0000e358 nt!KiTrap0E+0x2ac
8a9f08b8 818d5cbd 8a9f0864 03754cc0 84754000 nt!MiIdentifyPfn+0xa29
8a9f08ec 81a54b79 7faf6a84 8a9f0978 00000006 nt!MmQueryPfnList+0x130
8a9f0930 81a6fc1a 00000001 7faf6a14 00000014 nt!PfpPfnPrioRequest+0xdc
8a9f09a0 81a7b199 00000000 00000001 8a9f0d30 nt!PfQuerySuperfetchInformation+0xea
8a9f0d4c 81899a1a 0000004f 01c9f29c 00000014 nt!NtQuerySystemInformation+0x2201
8a9f0d4c 774b9a94 0000004f 01c9f29c 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01c9f268 00000000 00000000 00000000 00000000 0x774b9a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIdentifyPfn+a29
8187784c 8b7918 mov edi,dword ptr [ecx+18h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiIdentifyPfn+a29
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8fb4
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiIdentifyPfn+a29
BUCKET_ID: 0xA_nt!MiIdentifyPfn+a29
Followup: MachineOwner
Mijn vraag is:
- Ligt het aan corrupt RAM geheugen;
- Aan het feit dat ik 4 GB geheugen heb en Vista-32 alleen 3 GB erkent;
- Of komt het door een driver of programma?
Nu heb ik de minidump laten converteren en hier is het resultaat (Ik heb wat enters eruit gehaald)
* Bugcheck Analysis
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ba7ffffc, 2, 0, 8187784c}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+a29 )
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: ba7ffffc, 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: 8187784c, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from 81979868
Unable to read MiSystemVaType memory at 81959420
ba7ffffc
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiIdentifyPfn+a29
8187784c 8b7918 mov edi,dword ptr [ecx+18h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: 8a9f07e4 -- (.trap 0xffffffff8a9f07e4)
ErrCode = 00000000
eax=01ffffff ebx=84754cc0 ecx=ba7fffe4 edx=01ffffff esi=00000058 edi=01ffffff
eip=8187784c esp=8a9f0858 ebp=8a9f08b8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!MiIdentifyPfn+0xa29:
8187784c 8b7918 mov edi,dword ptr [ecx+18h] ds:0023:ba7ffffc=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8187784c to 8189cd24
STACK_TEXT:
8a9f07e4 8187784c badb0d00 01ffffff 0000e358 nt!KiTrap0E+0x2ac
8a9f08b8 818d5cbd 8a9f0864 03754cc0 84754000 nt!MiIdentifyPfn+0xa29
8a9f08ec 81a54b79 7faf6a84 8a9f0978 00000006 nt!MmQueryPfnList+0x130
8a9f0930 81a6fc1a 00000001 7faf6a14 00000014 nt!PfpPfnPrioRequest+0xdc
8a9f09a0 81a7b199 00000000 00000001 8a9f0d30 nt!PfQuerySuperfetchInformation+0xea
8a9f0d4c 81899a1a 0000004f 01c9f29c 00000014 nt!NtQuerySystemInformation+0x2201
8a9f0d4c 774b9a94 0000004f 01c9f29c 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01c9f268 00000000 00000000 00000000 00000000 0x774b9a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIdentifyPfn+a29
8187784c 8b7918 mov edi,dword ptr [ecx+18h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiIdentifyPfn+a29
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8fb4
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiIdentifyPfn+a29
BUCKET_ID: 0xA_nt!MiIdentifyPfn+a29
Followup: MachineOwner
Mijn vraag is:
- Ligt het aan corrupt RAM geheugen;
- Aan het feit dat ik 4 GB geheugen heb en Vista-32 alleen 3 GB erkent;
- Of komt het door een driver of programma?
[ Voor 83% gewijzigd door Propos op 22-04-2009 00:03 ]