Eli voiko joku auttaa miten korjaan tän. Kone on pari kuukautta vanha HP DV 7 Windows vista 32bit Tulee bluescreenei ihan random aikoina. Asensin jo Vistan uusiks, mutta ei auttanut vielläkin herjaa samaa ongelmaa. Ajoin windows memory testin, mutta ei sekään löytänyt yhtäkään virhettä. Tämmöstä valittaa; Problem signature: Problem Event Name: BlueScreen OS Version: 6.0.6001.2.1.0.768.3 Locale ID: 1061 Additional information about the problem: BCCode: a BCP1: 81A12094 BCP2: 000000FF BCP3: 00000000 BCP4: 81E648FF OS Version: 6_0_6001 Service Pack: 1_0 Product: 768_1 Files that help describe the problem: C:\WINDOWS\Minidump\Mini090209-02.dmp C:\Users\Matu\AppData\Local\Temp\WER-48219-0.sysdata.xml C:\Users\Matu\AppData\Local\Temp\WER7EEF.tmp.version.txt BugCheck A, {81a12094, ff, 0, 81e648ff} Probably caused by : ntkrpamp.exe ( nt!KiInterruptDispatch+f ) 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: 81a12094, memory referenced Arg2: 000000ff, 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: 81e648ff, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 81f48868 Unable to read MiSystemVaType memory at 81f28420 81a12094 CURRENT_IRQL: 0 FAULTING_IP: nt!KiInterruptDispatch+f 81e648ff ff159420e181 call dword ptr [nt!_imp__HalBeginSystemInterrupt (81e12094)] CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: cmdagent.exe TRAP_FRAME: 8bfe7cdc -- (.trap 0xffffffff8bfe7cdc) ErrCode = 00000000 eax=000000b0 ebx=042de874 ecx=0101000a edx=00000000 esi=803d1000 edi=87485280 eip=81e648ff esp=8bfe7d50 ebp=8bfe7d64 iopl=0 nv up di ng nz ac pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010096 nt!KiInterruptDispatch+0xf: 81e648ff ff159420e181 call dword ptr [nt!_imp__HalBeginSystemInterrupt (81e12094)] ds:0023:81e12094=0036a88e Resetting default scope LAST_CONTROL_TRANSFER: from 81e648ff to 81e6bd24 STACK_TEXT: 8bfe7cdc 81e648ff badb0d00 00000000 803d1002 nt!KiTrap0E+0x2ac 8bfe7d64 01db3281 badb0d00 00000000 00000000 nt!KiInterruptDispatch+0xf WARNING: Frame IP not in any known module. Following frames may be wrong. 042de874 00000000 00000000 00000000 00000000 0x1db3281 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiInterruptDispatch+f 81e648ff ff159420e181 call dword ptr [nt!_imp__HalBeginSystemInterrupt (81e12094)] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiInterruptDispatch+f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8fb4 FAILURE_BUCKET_ID: 0xA_nt!KiInterruptDispatch+f BUCKET_ID: 0xA_nt!KiInterruptDispatch+f ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks. Arg2: 00000000, 0. Arg3: 803d1120, The PRCB address of the hung processor. Arg4: 00000001, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 1c STACK_TEXT: a7b1b8dc 81cef321 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e a7b1b910 81cef02d 0000621b 000000d1 a7b1b9a8 nt!KeUpdateRunTime+0xd5 a7b1b910 81c56f3d 0000621b 000000d1 a7b1b9a8 nt!KeUpdateSystemTime+0xed a7b1b9a8 81e7011d 00000001 978fb14c 00000053 nt!KeFlushProcessWriteBuffers+0x64 a7b1bd4c 81c8ea7a 00000053 003b6bd8 00000002 nt!NtQuerySystemInformation+0x2254 a7b1bd4c 77759a94 00000053 003b6bd8 00000002 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 00fbf45c 00000000 00000000 00000000 00000000 0x77759a94 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE ******************************************************************************* * * * 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: 12b3d074, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 83db1d82, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 81b6a868 Unable to read MiSystemVaType memory at 81b4a420 12b3d074 CURRENT_IRQL: 2 FAULTING_IP: hpdskflt+1d82 83db1d82 ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: 803ecb8c -- (.trap 0xffffffff803ecb8c) ErrCode = 00000000 eax=86c74540 ebx=86e2c538 ecx=86c74400 edx=00000004 esi=86c74488 edi=86c7451f eip=83db1d82 esp=803ecc00 ebp=803ecc34 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 hpdskflt+0x1d82: 83db1d82 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 83db1d82 to 81a8dd84 STACK_TEXT: 803ecb8c 83db1d82 badb0d00 00000004 803d51e0 nt!KiTrap0E+0x2ac WARNING: Stack unwind information not available. Following frames may be wrong. 803ecbfc 81a6d0e4 86e2c538 86c74488 86e2c5f0 hpdskflt+0x1d82 803ecc34 830bb2d7 871b4a4c 86ca9428 803ecc64 nt!IopfCompleteRequest+0x11d 803ecc44 830bbcc6 86ea00e8 86c74488 871b4a4c ataport!IdeCompleteScsiIrp+0x31 803ecc64 830b8fb2 86ea00e8 00000000 803ecc94 ataport!IdeCommonCrbCompletion+0x44 803ecc74 830bde6f 86e2d0e0 86ca9428 86ca9428 ataport!IdeTranslateCompletedRequest+0x26 803ecc94 830be0a9 86e2d0e0 86ca9428 803d1120 ataport!IdeProcessCompletedRequests+0x121 803ecce8 81ae9510 86e2d09c 86e2d028 00000000 ataport!IdePortCompletionDpc+0xab 803ecd50 81ae7f9d 00000000 0000000e 2f2f3a70 nt!KiRetireDpcList+0x147 803ecd54 00000000 0000000e 2f2f3a70 7073636f nt!KiIdleLoop+0x49 STACK_COMMAND: kb FOLLOWUP_IP: hpdskflt+1d82 83db1d82 ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: hpdskflt+1d82 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hpdskflt IMAGE_NAME: hpdskflt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 47e0331f FAILURE_BUCKET_ID: 0xD1_hpdskflt+1d82 BUCKET_ID: 0xD1_hpdskflt+1d82 Onko kellään mitään hajua mitä mun koneessa tapahtuu D
Uuden kanssa kannattaa hoitaa takuuna... Mutta jokin hp:n oma suojaussofta siellä bugittaa... Koitas tuota: http://h20000.www2.hp.com/bizsuppor...swLang=13&mode=2&taskId=135&swItem=ob-63065-1
