Hi,
i often got a bluescreen ...
Here ´s the dump file -> read with the debugging tool from microsoft:
What could it be ?
steve
i often got a bluescreen ...
Here ´s the dump file -> read with the debugging tool from microsoft:
Code:
******************************************************************************* * * * 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: 000001b4, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 81b98002, address which referenced memory Debugging Details: ------------------ ***** 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 *** *** *** ************************************************************************* MODULE_NAME: nt FAULTING_MODULE: 81800000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4549ad6c WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 000001b4 CURRENT_IRQL: 2 FAULTING_IP: hal+3002 81b98002 ?? ??? CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from 81b98002 to 818494d4 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 9d85e9b8 81b98002 badb0d00 000001b4 9d85ea7c nt+0x494d4 9d85ea48 8186d1ec 993b3820 a110c0f8 824f2cf3 hal+0x3002 9d85ea64 81a14c68 84b11380 00000000 9e495470 nt+0x6d1ec 9d85ebb4 819f5347 84b11380 00000000 00001000 nt+0x214c68 9d85eccc 81a0361c 9d85ed20 000f0005 00000000 nt+0x1f5347 9d85ed40 818461fa 04e9ecb8 000f0005 00000000 nt+0x20361c 9d85ed64 76f40f34 badb0d00 04e9ec48 00000000 nt+0x461fa 9d85ed68 badb0d00 04e9ec48 00000000 00000000 0x76f40f34 9d85ed6c 04e9ec48 00000000 00000000 00000000 0xbadb0d00 9d85ed70 00000000 00000000 00000000 00000000 0x4e9ec48 STACK_COMMAND: kb FOLLOWUP_IP: nt+494d4 818494d4 833de0f7918100 cmp dword ptr [nt+0x11f7e0 (8191f7e0)],0 SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe SYMBOL_NAME: nt+494d4 BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------
steve
Comment