|
|
|
|
Strumenti |
14-03-2011, 22:33 | #1081 |
Member
Iscritto dal: Aug 2004
Messaggi: 228
|
ciao,
da un po' di tempo il mio computer continua a dare schermate blu, ogni tanto quando fa il boot ogni tanto mentre windows funziona, potete aiutarmi a identificare il problema? premetto che ho fatto il test della ram e degli hard disk e non ho riscontrato problemi. apparentemente le schermate blu ogni volta danno un errore diverso, vi riporto cosa mi dice windbg degli ultimi 4 blue screen 1° BSOD Codice:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000001238, The subtype of the bugcheck. Arg2: fffffa80045338b0 Arg3: 0000000000000802 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_1238 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002984d9f to fffff80002895640 STACK_TEXT: fffff880`07ffd7b8 fffff800`02984d9f : 00000000`0000001a 00000000`00001238 fffffa80`045338b0 00000000`00000802 : nt!KeBugCheckEx fffff880`07ffd7c0 fffff880`01934eb2 : 00000000`00000009 fffffa80`045338b0 fffffa80`04997078 00000000`0000000a : nt!MmFreePagesFromMdl+0x5f fffff880`07ffd820 fffff880`019347df : fffffa80`04997078 00000000`00000000 fffffa80`049f3fe6 00000000`00000000 : rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x4e fffff880`07ffd880 fffff880`019334ce : fffffa80`04997010 00000000`00000001 fffffa80`04997010 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCleanup+0x183 fffff880`07ffd8c0 fffff880`01932a27 : fffffa80`04997010 00000000`00000001 fffffa80`04997010 fffff880`07ffdca0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStCleanup+0x7a fffff880`07ffd900 fffff880`0193298a : fffff880`019558f0 00000000`00000008 fffffa80`04997010 fffff880`01955870 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmStoreMgrCallback+0x4b fffff880`07ffd940 fffff880`019594b8 : fffff880`01955870 fffff880`07ffdca0 00000000`00000000 fffffa80`06aeef20 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmCleanup+0x9a fffff880`07ffd970 fffff880`0193ab26 : fffffa80`06aeef20 fffffa80`06aeef20 00000000`00000000 00000000`00000000 : rdyboost!SmdRBContextShutdown+0x94 fffff880`07ffd9b0 fffff800`02baff97 : 00000000`00000000 fffffa80`05c68ee0 fffffa80`05c68ff8 fffffa80`06aeef20 : rdyboost!SmdDispatchDeviceControl+0x3ce fffff880`07ffda10 fffff800`02bb07f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607 fffff880`07ffdb40 fffff800`028948d3 : 00000000`00000000 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!NtDeviceIoControlFile+0x56 fffff880`07ffdbb0 00000000`775b138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`01fced58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775b138a STACK_COMMAND: kb FOLLOWUP_IP: rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e fffff880`01934eb2 33d2 xor edx,edx SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e FOLLOWUP_NAME: MachineOwner MODULE_NAME: rdyboost IMAGE_NAME: rdyboost.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7982e FAILURE_BUCKET_ID: X64_0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e BUCKET_ID: X64_0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000001238, The subtype of the bugcheck. Arg2: fffffa80045338b0 Arg3: 0000000000000802 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_1238 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002984d9f to fffff80002895640 STACK_TEXT: fffff880`07ffd7b8 fffff800`02984d9f : 00000000`0000001a 00000000`00001238 fffffa80`045338b0 00000000`00000802 : nt!KeBugCheckEx fffff880`07ffd7c0 fffff880`01934eb2 : 00000000`00000009 fffffa80`045338b0 fffffa80`04997078 00000000`0000000a : nt!MmFreePagesFromMdl+0x5f fffff880`07ffd820 fffff880`019347df : fffffa80`04997078 00000000`00000000 fffffa80`049f3fe6 00000000`00000000 : rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x4e fffff880`07ffd880 fffff880`019334ce : fffffa80`04997010 00000000`00000001 fffffa80`04997010 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCleanup+0x183 fffff880`07ffd8c0 fffff880`01932a27 : fffffa80`04997010 00000000`00000001 fffffa80`04997010 fffff880`07ffdca0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStCleanup+0x7a fffff880`07ffd900 fffff880`0193298a : fffff880`019558f0 00000000`00000008 fffffa80`04997010 fffff880`01955870 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmStoreMgrCallback+0x4b fffff880`07ffd940 fffff880`019594b8 : fffff880`01955870 fffff880`07ffdca0 00000000`00000000 fffffa80`06aeef20 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmCleanup+0x9a fffff880`07ffd970 fffff880`0193ab26 : fffffa80`06aeef20 fffffa80`06aeef20 00000000`00000000 00000000`00000000 : rdyboost!SmdRBContextShutdown+0x94 fffff880`07ffd9b0 fffff800`02baff97 : 00000000`00000000 fffffa80`05c68ee0 fffffa80`05c68ff8 fffffa80`06aeef20 : rdyboost!SmdDispatchDeviceControl+0x3ce fffff880`07ffda10 fffff800`02bb07f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607 fffff880`07ffdb40 fffff800`028948d3 : 00000000`00000000 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!NtDeviceIoControlFile+0x56 fffff880`07ffdbb0 00000000`775b138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`01fced58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775b138a STACK_COMMAND: kb FOLLOWUP_IP: rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e fffff880`01934eb2 33d2 xor edx,edx SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e FOLLOWUP_NAME: MachineOwner MODULE_NAME: rdyboost IMAGE_NAME: rdyboost.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7982e FAILURE_BUCKET_ID: X64_0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e BUCKET_ID: X64_0x1a_1238_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e Followup: MachineOwner Codice:
******************************************************************************* * * * 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: ffffffffffffff96, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff880048690ff, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0e0e8 ffffffffffffff96 FAULTING_IP: dxgkrnl!DXGCONTEXT::PresentFromCdd+4c7 fffff880`048690ff 08488b or byte ptr [rax-75h],cl MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880025c6e40 -- (.trap 0xfffff880025c6e40) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000000b rbx=0000000000000000 rcx=000000000000000b rdx=fffffa800546cb60 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880048690ff rsp=fffff880025c6fd0 rbp=fffff880025c76e0 r8=0000000000000000 r9=0000000000000000 r10=fffffa8003961148 r11=fffffa800546cb60 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc dxgkrnl!DXGCONTEXT::PresentFromCdd+0x4c7: fffff880`048690ff 08488b or byte ptr [rax-75h],cl ds:58f0:ffffffff`ffffff96=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a892ac to fffff80002add640 STACK_TEXT: fffff880`025c6cd8 fffff800`02a892ac : 00000000`00000050 ffffffff`ffffff96 00000000`00000001 fffff880`025c6e40 : nt!KeBugCheckEx fffff880`025c6ce0 fffff800`02adb76e : 00000000`00000001 ffffffff`ffffff96 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4621f fffff880`025c6e40 fffff880`048690ff : 00000000`00ffffff fffffa80`056de000 fffff880`025c76e0 00000000`00000000 : nt!KiPageFault+0x16e fffff880`025c6fd0 fffff880`0484655e : 00000000`00000001 fffff880`025c76e0 fffff8a0`00000000 fffff880`025c7218 : dxgkrnl!DXGCONTEXT::PresentFromCdd+0x4c7 fffff880`025c71e0 fffff960`00674c9c : fffff900`c00c1020 00000000`00000030 00000000`00000030 fffff900`c01d87b0 : dxgkrnl!DxgkCddPresent+0x1fa fffff880`025c7270 fffff960`0067606c : ffffffff`fffd74f6 00000000`01040028 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x324 fffff880`025c79b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!PresentWorkerThread+0xd00 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgkrnl 5 errors : !dxgkrnl (fffff8800486907e-fffff88004869c7e) fffff88004869070 58 40 38 b4 24 18 01 00 00 74 37 c7 84 24 *90 02 X@8.$....t7..$.. ... fffff880048690f0 b4 24 20 01 00 00 41 ff 17 48 8b 4f 78 89 *c1 08 .$ ...A..H.Ox... ... fffff88004869530 7d 2d c7 44 24 60 0a 0a 00 00 41 8b cf ff *95 c5 }-.D$`....A..... ... fffff880048699f0 ff 0f 84 a9 00 00 00 48 8b 47 10 48 8b 50 *90 48 .......H.G.H.P.H ... fffff88004869c70 44 8a fd 4c 89 54 24 40 48 3b 81 88 02 00 *80 74 D..L.T$@H;.....t MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption --------- 2: 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: ffffffffffffff96, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff880048690ff, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: ffffffffffffff96 FAULTING_IP: dxgkrnl!DXGCONTEXT::PresentFromCdd+4c7 fffff880`048690ff 08488b or byte ptr [rax-75h],cl MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880025c6e40 -- (.trap 0xfffff880025c6e40) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000000b rbx=0000000000000000 rcx=000000000000000b rdx=fffffa800546cb60 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880048690ff rsp=fffff880025c6fd0 rbp=fffff880025c76e0 r8=0000000000000000 r9=0000000000000000 r10=fffffa8003961148 r11=fffffa800546cb60 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc dxgkrnl!DXGCONTEXT::PresentFromCdd+0x4c7: fffff880`048690ff 08488b or byte ptr [rax-75h],cl ds:58f0:ffffffff`ffffff96=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a892ac to fffff80002add640 STACK_TEXT: fffff880`025c6cd8 fffff800`02a892ac : 00000000`00000050 ffffffff`ffffff96 00000000`00000001 fffff880`025c6e40 : nt!KeBugCheckEx fffff880`025c6ce0 fffff800`02adb76e : 00000000`00000001 ffffffff`ffffff96 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4621f fffff880`025c6e40 fffff880`048690ff : 00000000`00ffffff fffffa80`056de000 fffff880`025c76e0 00000000`00000000 : nt!KiPageFault+0x16e fffff880`025c6fd0 fffff880`0484655e : 00000000`00000001 fffff880`025c76e0 fffff8a0`00000000 fffff880`025c7218 : dxgkrnl!DXGCONTEXT::PresentFromCdd+0x4c7 fffff880`025c71e0 fffff960`00674c9c : fffff900`c00c1020 00000000`00000030 00000000`00000030 fffff900`c01d87b0 : dxgkrnl!DxgkCddPresent+0x1fa fffff880`025c7270 fffff960`0067606c : ffffffff`fffd74f6 00000000`01040028 00000000`00000001 00000000`00000000 : cdd!CddPresentBlt+0x324 fffff880`025c79b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!PresentWorkerThread+0xd00 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgkrnl 5 errors : !dxgkrnl (fffff8800486907e-fffff88004869c7e) fffff88004869070 58 40 38 b4 24 18 01 00 00 74 37 c7 84 24 *90 02 X@8.$....t7..$.. ... fffff880048690f0 b4 24 20 01 00 00 41 ff 17 48 8b 4f 78 89 *c1 08 .$ ...A..H.Ox... ... fffff88004869530 7d 2d c7 44 24 60 0a 0a 00 00 41 8b cf ff *95 c5 }-.D$`....A..... ... fffff880048699f0 ff 0f 84 a9 00 00 00 48 8b 47 10 48 8b 50 *90 48 .......H.G.H.P.H ... fffff88004869c70 44 8a fd 4c 89 54 24 40 48 3b 81 88 02 00 *80 74 D..L.T$@H;.....t MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption Codice:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff9600007bc76, Address of the instruction which caused the bugcheck Arg3: fffff88009f76210, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. FAULTING_IP: win32k!RFONTOBJ::bGetGlyphMetricsPlus+216 fffff960`0007bc76 48833e00 cmp qword ptr [rsi],0 CONTEXT: fffff88009f76210 -- (.cxr 0xfffff88009f76210) rax=fffff900c21b8020 rbx=fffff88009f76e30 rcx=fffff900c21bdf00 rdx=fffff88009f76b70 rsi=0080000000000000 rdi=fffff900c0081528 rip=fffff9600007bc76 rsp=fffff88009f76bf0 rbp=fffff900c0081b7a r8=fffff960002ed860 r9=0000000000000000 r10=fffff900c1edeb3c r11=000000000000002c r12=0000000000000054 r13=fffff88009f76d00 r14=fffff900c21b8010 r15=000000000000005b iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 win32k!RFONTOBJ::bGetGlyphMetricsPlus+0x216: fffff960`0007bc76 48833e00 cmp qword ptr [rsi],0 ds:002b:00800000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff96000211cbd to fffff9600007bc76 STACK_TEXT: fffff880`09f76bf0 fffff960`00211cbd : fffff900`c0081b28 fffff900`c0081150 fffff880`09f76e30 00000000`00000000 : win32k!RFONTOBJ::bGetGlyphMetricsPlus+0x216 fffff880`09f76c70 fffff960`0007b20f : 00000000`00000001 fffff880`09f77210 00000000`00000000 fffff900`c00c0010 : win32k!ESTROBJ::vCharPos_H1+0x81 fffff880`09f76d00 fffff960`0005283e : fffff900`41800000 00000000`00000000 00000000`00000054 fffff880`09f77210 : win32k!ESTROBJ::vInit+0x27f fffff880`09f76d90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!GreExtTextOutWLocked+0xb12 FOLLOWUP_IP: win32k!RFONTOBJ::bGetGlyphMetricsPlus+216 fffff960`0007bc76 48833e00 cmp qword ptr [rsi],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!RFONTOBJ::bGetGlyphMetricsPlus+216 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d2415ea STACK_COMMAND: .cxr 0xfffff88009f76210 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!RFONTOBJ::bGetGlyphMetricsPlus+216 BUCKET_ID: X64_0x3B_win32k!RFONTOBJ::bGetGlyphMetricsPlus+216 Followup: MachineOwner Codice:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002e06bf3, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. FAULTING_IP: nt!MiApplyRawFixups+23 fffff800`02e06bf3 418b7804 mov edi,dword ptr [r8+4] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe0e8 ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a 0x%08lx ha fatto riferimento alla memoria a 0x%08lx. La memoria non poteva essere %s. BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ad9028 to fffff80002a8d640 STACK_TEXT: fffff880`07137998 fffff800`02ad9028 : 00000000`0000001e ffffffff`c0000005 fffff800`02e06bf3 00000000`00000000 : nt!KeBugCheckEx fffff880`071379a0 fffff800`02a8ccc2 : fffff880`07138178 fffff880`0394e000 fffff880`07138220 fffff880`0394e000 : nt! ?? ::FNODOBFM::`string'+0x4987d fffff880`07138040 fffff800`02a8b5ca : fffff8a0`02b3f100 fffff8a0`02ee6ee0 fffffa80`00000000 00001f80`0101feda : nt!KiExceptionDispatch+0xc2 fffff880`07138220 fffff800`02e06bf3 : 00000000`6c646d00 00000000`00001040 fffff800`02c14600 fffffa80`04db74d8 : nt!KiGeneralProtectionFault+0x10a fffff880`071383b0 fffff800`02ce8d5e : fffff880`0394e000 00800000`00000000 00000000`635b0000 fffff6fc`4001ca70 : nt!MiApplyRawFixups+0x23 fffff880`071383f0 fffff800`02d651b7 : fffffa80`00000000 fffffa80`04db73d0 00000000`00000a87 fffff8a0`02e5d000 : nt! ?? ::NNGAKEGL::`string'+0x72ea fffff880`07138450 fffff800`02abd15b : ffffffff`ffffffff fffff880`071385c0 00000000`0003b600 00000000`00000000 : nt!MiRelocateImagePfn+0xf7 fffff880`071384b0 fffff800`02a28414 : fffffa80`05991640 00000000`00000000 00000000`00000000 00000000`00000065 : nt!MiWaitForInPageComplete+0x7ef fffff880`07138590 fffff800`02ce5d2a : 00000000`00000000 fffffa80`03c7dd28 00000000`00000066 fffffa80`03c7dcd0 : nt!MiPfCompletePrefetchIos+0x54 fffff880`071385c0 fffff800`02ee701c : 00000000`00000010 00000000`0000002c fffffa80`03c7dcd0 00000000`0000002c : nt!MmPrefetchPages+0x13a fffff880`07138620 fffff800`02ee7257 : fffff880`07138740 00000000`00000001 00000000`00000000 00000000`00000000 : nt!PfSnPrefetchSections+0x43c fffff880`07138710 fffff800`02ee767f : 0000006f`8a512009 fffffa80`0626eb30 fffff8a0`02daf000 00000000`00000000 : nt!PfSnPrefetchScenario+0x187 fffff880`07138980 fffff800`02de5bff : 00000000`00000000 00000000`18acfcff fffffa80`064c40e0 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f fffff880`07138a50 fffff800`02d7b510 : fffffa80`04db73d0 fffffa80`064c40e0 00000000`14050800 00000000`7efde000 : nt! ?? ::NNGAKEGL::`string'+0x52280 fffff880`07138a80 fffff800`02a7f115 : fffff880`02fd5180 00000000`00000000 fffff800`02d7b3c8 fffffa80`04db73d0 : nt!PspUserThreadStartup+0x148 fffff880`07138ae0 fffff800`02a7f097 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16 fffff880`07138c20 00000000`76e7c500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn 00000000`0018f978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e7c500 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiApplyRawFixups+23 fffff800`02e06bf3 418b7804 mov edi,dword ptr [r8+4] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!MiApplyRawFixups+23 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!MiApplyRawFixups+23 BUCKET_ID: X64_0x1E_c0000005_nt!MiApplyRawFixups+23 Followup: MachineOwner |
15-03-2011, 07:46 | #1082 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37005
|
Stai usando il readyboost per caso, in quel caso dovresti cambiare il dispositivo che sembra incompatibile. Per il secondo problema csrss potrebbe anche essere segno di qualche malware, controlla la osizione di quel processo nel task deve stare in C/Windows/Sytem32. per il resto c'è un problema con FF. Controlla anche la ram
|
15-03-2011, 08:10 | #1083 |
Member
Iscritto dal: Aug 2004
Messaggi: 228
|
ciao, grazie per la tua risposta.
non non sto usando il readyboost. ho verificato la posizione del processo crss ma è corretta e ho fatto una verifica con l'antivirus e l'antispyware e non ha trovato nulla. per la ram ho fatto un memtest al 500% e non ha dato alcun tipo di errore. mi presentava questi continui blue screen anche prima poi ho formattato tutto e ha riniziato a darmi i blue screen. ho verificato anche gli hard disk ma nessun errore. può essere la mother board non funzionante? |
15-03-2011, 09:23 | #1084 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37005
|
Per sicurezza prova a scollegare un banco di ram alla volta.
La scheda madre non credo, ma potrebbe esserci qualche componente hw difettoso... |
15-03-2011, 20:30 | #1085 | |
Member
Iscritto dal: Dec 2008
Messaggi: 63
|
Quote:
Comunque è da un po' di giorni che non sta dando più problemi. Ti ringrazio per l'aiuto! |
|
16-03-2011, 19:09 | #1086 |
Member
Iscritto dal: Sep 2008
Messaggi: 77
|
Salve ragazzi , allora so che dovrei seguire la guida ma non riesco a fare nada sul mio pc a causa di continue schermate blu che in un primo momento mi hanno dato l'errore:
SYSTEM_SERVICE_EXCEPTION mentre ora si sono focalizzate su : irql_not_less_or_equal Ho Win 7 64 Bit A cosa può essere dovuto tale errore?? Problema di RAM forse? E se si come faccio a capirlo? |
16-03-2011, 19:47 | #1088 |
Member
Iscritto dal: Sep 2008
Messaggi: 77
|
In realtà ho provato a scollegare i due banchi ram che ho...
Smontandone uno il problema sembrava risolto , tanto è vero che rimontando quello staccato e quindi apparentemente difettoso la schermata blu è ritornata... Poi però rifacendo una prova ulteriore con il banco "apparentemente buono" l'errore si è ripresentato anche lì..... Comunque al fine di vedere se effettivamente il problema proviene dalla RAM, saresti così gentile da spiegarmi come si fa un memtest?? |
16-03-2011, 21:17 | #1089 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37005
|
Allora potrebbe essere un problema coi contatti degli slot, dovresti cercare di pulirli, o magari addirittura il voltaggio. Il memtest lo puoi fare con l'utility di windows, che quasi nessuno usa, malfidati oppure con un programma tipo memtest+86 che prima devi masterizzare su cd e quindi lanciare all'avvio del pc. Tieni presente che un memtest per essere valido deve durare parecchie ore e molti cicli
|
17-03-2011, 08:50 | #1090 |
Member
Iscritto dal: Sep 2008
Messaggi: 77
|
Allora a questo punto penso di poter escludere la RAM dal momento che oltre a provare i due banchi ram separatamente ho provato anche dei banchi che avevo sostituito con quelli attualmente in uso e niente...... Il problema ritorna: anzi ,quando non mi da la schermata blu con l errore irql_not_less_or_equal , si blocca nel caricamento di windows dopo aver cliccato su uno degli account iniziali.........
Che ne pensate???? Helpppppp |
20-03-2011, 14:10 | #1091 |
Member
Iscritto dal: Mar 2007
Messaggi: 91
|
Oggi tutto ad un tratto accendendo il pc fisso mi è comparsa la fatidica schermata blu con scritto fatal error c000021a e poi 0xc000012f.
Avete idee di come possa ripararlo? Ho il backup del pc con acronis true image, ma vorrei evitare la formattazione. grazie |
20-03-2011, 14:24 | #1092 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37005
|
Sei nella sezione giusta, ma nella pagina sbagliata leggi la guida in prima e posta il file dmp zippato
|
20-03-2011, 14:27 | #1093 |
Member
Iscritto dal: Mar 2007
Messaggi: 91
|
come faccio a fare un file in dmp?
|
20-03-2011, 14:58 | #1094 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37005
|
Non lo devi fare tu, la fa il sistema in caso di bsod, come spiegato nella prima pagina di questa discussione, leggila
|
23-03-2011, 23:25 | #1095 | |
Senior Member
Iscritto dal: Dec 2007
Città: Palermo
Messaggi: 2155
|
raga ho avuto questa schermata blu con questo errore:
Quote:
|
|
24-03-2011, 06:47 | #1096 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37005
|
|
27-03-2011, 00:53 | #1097 |
Member
Iscritto dal: Sep 2006
Messaggi: 34
|
Potrei evitare di...
Ciao a tutti innanzitutto.
Volevo chiedervi una cosa; non c'è altro modo per capire il perchè di un bsod oltre a quello spiegato nella prima pagina di questo thread? A me non avvengono spesso ma ogni tanto purtroppo sono sempre diversi. Poco fa mi sono allontanato dal pc, al mio ritorno, proprio quando stavo per sedermi nuovamente (sembrerebbe fatto apposta) nuovo bluescreen. Io uso bluescreenview per leggere i vari codici errore e le cause. Vorrei sinceramente evitare di installare Windows Debugging Tools e i symbols sarà anche facile per voi ma io non c'ho capito niente. Ho un pc senza alcun overclock. Per circa un anno e per motivi che non ho mai capito, ho solo diciamo così overclockato la ram in quanto anche se la mia scheda (una asus rampage formula) avrebbe dovuto "digerire" le mie corsair ddr2 1066 mhz me le leggeva a 800 il che ho pensato a portarle semplicemente a 1066. Ho anche fatto una marea di test alle ram con memtest ma di errori nememno l'ombra. Quando ho notato che i bluescreen mi capitavano più spesso ho resettato tutto (la mia mobo mi permette di farlo cliccando un semplice tasto posto sul retro del case) pensando di aver risolto il problema e invece di tanto in tanto ne escono di nuovi. L'ultimo poco fa: MEMORY_MANAGEMENT. Avrei preferito che si rompesse qualche pezzo, a quel punto basta cambiarlo ma quando iniziano ad uscire questi bluescreen mi cadono le braccia. |
27-03-2011, 10:36 | #1098 |
Senior Member
Iscritto dal: Jan 2010
Messaggi: 37005
|
Tanto per iniziare dai una controllata alla ram, memtest oppure scollegando un banco alla volta
|
28-03-2011, 00:18 | #1099 |
Senior Member
Iscritto dal: Feb 2008
Messaggi: 9581
|
sapreste aiutarmi?
Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\032811-20451-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`03449000 PsLoadedModuleList = 0xfffff800`0368ee90 Debug session time: Mon Mar 28 01:03:19.409 2011 (UTC + 2:00) System Uptime: 0 days 1:37:26.627 Loading Kernel Symbols ............................................................... ................................................................ ............................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {2, 2, 8, 2} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: 0000000000000002, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000000000002, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036fa0e8 0000000000000002 CURRENT_IRQL: 2 FAULTING_IP: +6238643366333963 00000000`00000002 ?? ??? PROCESS_NAME: Bioshock.exe CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: fffff80000ba24f0 -- (.trap 0xfffff80000ba24f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000403d0000 rbx=0000000000000000 rcx=fffff8000363be80 rdx=fffffa8009145250 rsi=0000000000000000 rdi=0000000000000000 rip=0000000000000002 rsp=fffff80000ba2680 rbp=fffffa8009145250 r8=fffffa8009145210 r9=000000000000003d r10=fffff8000363be80 r11=fffff80000ba2700 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc 00000000`00000002 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800034c8be9 to fffff800034c9640 FAILED_INSTRUCTION_ADDRESS: +6238643366333963 00000000`00000002 ?? ??? STACK_TEXT: fffff800`00ba23a8 fffff800`034c8be9 : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff800`00ba23b0 fffff800`034c7860 : fffffa80`09145250 fffffa80`09145210 00000000`0000003d 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`00ba24f0 00000000`00000002 : 00000000`00000000 fffffa80`09145250 fffff800`0363be80 fffff800`034d51c0 : nt!KiPageFault+0x260 fffff800`00ba2680 00000000`00000000 : fffffa80`09145250 fffff800`0363be80 fffff800`034d51c0 ffffffff`fd050f80 : 0x2 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+260 fffff800`034c7860 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: 4ce7951a FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260 Followup: MachineOwner --------- |
28-03-2011, 00:41 | #1100 |
Member
Iscritto dal: Sep 2006
Messaggi: 34
|
Che stress!
Nuovo schermata blue e nuovo messaggio di errore poco fa, allo spegnimento del pc
PFN_LIST_CORRUPT, diverso da quello di ieri. |
Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 22:04.