View Full Version : Vista/7 - Schermate blu (bsod):individuazione cause dell'errore e possibili soluzioni
Pagine :
1
2
3
[
4]
5
6
7
8
9
10
11
12
13
ragazzi qualcuno non mi aiuterebbe ad individuare che tipo di problema ho?
ho seguito la guida ma non riesco a capire sinceramente
grazie a tutti
allego minidump
http://www.mediafire.com/?ff0byc1dca8jdhs
sistema windows 7 ultimate
cpu q6600
2gb ram ddr2
Salve ragazzi, oggi si è presentata la mia prima schermata blu su Windows Vista SP2 32 bit, premetto anche che avevo già installato da prima il Debugging Tool for Windows quindi allego il file.
Leggendo questo file sembrerebbe che la causa sia stata un problema hardware, non software.
Voi che dite? Non capisco molto bene il significato di questo documento. Grazie
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini100110-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x82611000 PsLoadedModuleList = 0x82728c70
Debug session time: Fri Oct 1 12:35:59.904 2010 (UTC + 2:00)
System Uptime: 0 days 0:45:11.669
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {a6727001, 0, 826ba092, 0}
Probably caused by : hardware ( nt!KiTrap0E+dc )
Followup: MachineOwner
---------
nirvanastarr
03-10-2010, 17:10
Salve a tutti....
Ho un problemino con il software di un gruppo di continuità APC. Preciso che mi sono rivolto al forum ufficiale.....NON COMMENTO :mad: .
Veniamo al problema. Quando installo il software ufficiale di APC, Powerchute Personal Edition, accade che il sistema va in crash. Per la precisione il sistema crasha quando, durante l'installazione, il software "spegne" la gestione dell'alimentazione di windows e poi la riavvia. Quando c'è da riavviare il tutto, l'installzione di blocca.
Ho eseguito il debug del dump...ecco:
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x24
PROCESS_NAME: powercfg.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88001249e95 to fffff80002cb9740
STACK_TEXT:
fffff880`0aab1d38 fffff880`01249e95 : 00000000`00000024 00000000`000c08a2 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0aab1d40 fffff880`0125f440 : 00000002`00000000 00000000`00000000 00000001`00000000 00000000`00000000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`0aab1e40 fffff880`00d8f23f : fffffa80`0cc20560 fffffa80`0cc20010 fffffa80`0cd688b0 00000000`00000000 : Ntfs!NtfsFsdWrite+0x1f0
fffff880`0aab1f00 fffff880`00d8d6df : fffffa80`07235de0 fffffa80`07255180 fffffa80`07235d00 fffffa80`0cc20010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0aab1f90 fffff880`01c79d5e : 00000000`60000001 fffffa80`07686960 fffffa80`00000020 fffffa80`07255180 : fltmgr!FltpDispatch+0xcf
fffff880`0aab1ff0 fffff880`01c7874c : fffffa80`07255180 fffffa80`07686960 00000000`60000001 fffffa80`0cc20010 : tdrpm258+0x4dd5e
fffff880`0aab2020 fffff880`01c78da1 : fffffa80`0cc20560 fffffa80`0cc20010 fffffa80`07255180 fffffa80`07686960 : tdrpm258+0x4c74c
fffff880`0aab2050 fffff880`01c76792 : fffffa80`0cc20560 fffff880`0aab2100 fffffa80`0cdfa010 fffffa80`07216f80 : tdrpm258+0x4cda1
fffff880`0aab2090 fffff880`00d8f23f : fffff880`0aab2170 fffff880`00d8ebe9 fffff880`0aab2100 00000000`00000000 : tdrpm258+0x4a792
fffff880`0aab20c0 fffff880`00d8d6df : fffffa80`0b84fde0 fffffa80`0ca2e920 fffffa80`0b84fd00 fffffa80`0cc20010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0aab2150 fffff800`02ca82ff : fffffa80`0cc20010 fffffa80`07511000 fffffa80`0cc420d0 fffff880`03364180 : fltmgr!FltpDispatch+0xcf
fffff880`0aab21b0 fffff800`030db4af : 00000000`00000001 fffffa80`07511000 00000000`00001000 00000000`00000001 : nt!IoSynchronousPageWrite+0x24f
fffff880`0aab2230 fffff800`0311e624 : 00000000`00000000 00000000`00000000 fffff880`0aab3c01 fffffa80`0ca2e920 : nt!PopClearHiberFileSignature+0x9f
fffff880`0aab22a0 fffff800`02f78117 : 00000000`00000000 fffff880`0aab3ca0 00000000`00000000 00000000`00000001 : nt!PopEnableHiberFile+0x274
fffff880`0aab22e0 fffff800`02cb8993 : fffffa80`07665b30 00000000`00000001 fffffa80`076616d0 fffff800`02fcf414 : nt!NtPowerInformation+0x957
fffff880`0aab3bb0 00000000`77ad034a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0025ddb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ad034a
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsPagingFileIo+155
fffff880`01249e95 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsPagingFileIo+155
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155
BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155
Followup: MachineOwner
Qualcuno ha qualche idea su come poter risolvere l'errore???
PRECISO: ho windows 7 64bit, il sistema è quello che vedete in firma. Ho eseguito tutti gli update di microsoft, e dei vari driver del sistema. Tutto funzia alla perfezione: quando gioco, quando lavoro, quando faccio editing....insomma questo è l'unico problema.
Spero tanto che riusciate ad aiutarmi ;)
Non ti resta che leggere qui :D
http://support.microsoft.com/search/default.aspx?qid=138328&query=ntfs.sys+schermata+blu&mode=r&catalog=LCID%3D1040
nirvanastarr
04-10-2010, 13:54
Si....ho scritto al forum di microsoft e infatti mi hanno confermato che il software di APC ha dei gravi conflitti con il sistema di gestione dell'alimentazione di Windows 7.
Ho scritto allora al forum di APC e a quanto pare stanno cercando di risolvere il problema.....speriamo bene....
Grazie comunque a tutti! ;)
ciao,
al computer di una mia amica con window vista installato da un errore quando tenta di aggiornarsi .
Errore 80071AA7 , il problema grosso è che window ad ogni avvio tenta di aggiornarsi , ci sta mezz'ora per poi dare questo errore ; quindi il pc è inusabile ..
Qualcuno può aiutarla ?
Vedi qui
http://www.vistaheads.com/forums/microsoft-public-windowsupdate/216000-error-80071aa7-when-updating.html
Jeremy01
16-10-2010, 01:12
ragazzi non riesco a trovare il percorso dei symbols.....qual'è dopo aver installato quel file da 200mb?
Jeremy01
16-10-2010, 01:21
rgazzi sapreste aiutarmi a capire la causa del mio crash?...mi è capitato durante un gioco (arma) ma non'è quello il problema in quanto si è verificato anche in un altra situazione
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {1, 2, 8, 1}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
1: 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: 0000000000000001, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000001, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330e0e0
0000000000000001
CURRENT_IRQL: 2
FAULTING_IP:
+6363336564653465
00000000`00000001 ?? ???
PROCESS_NAME: ARMA2.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff88003522580 -- (.trap 0xfffff88003522580)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000400 rbx=0000000000000000 rcx=0000000040b50000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000001 rsp=fffff88003522718 rbp=00000000009f2180
r8=0000000006173ea8 r9=00000000fffffa80 r10=fffff80003066000
r11=fffff88003522760 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
00000000`00000001 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030d5ca9 to fffff800030d6740
FAILED_INSTRUCTION_ADDRESS:
+6363336564653465
00000000`00000001 ?? ???
STACK_TEXT:
fffff880`03522438 fffff800`030d5ca9 : 00000000`0000000a 00000000`00000001 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`03522440 fffff800`030d4920 : fffffa80`08c4b128 fffff880`035227b0 fffffa80`08c4b120 fffffa80`08c4b060 : nt!KiBugCheckDispatch+0x69
fffff880`03522580 00000000`00000001 : fffff800`030e229e fffffa80`058af8e0 fffff880`04639f79 fffffa80`06112400 : nt!KiPageFault+0x260
fffff880`03522718 fffff800`030e229e : fffffa80`058af8e0 fffff880`04639f79 fffffa80`06112400 00000000`00000001 : 0x1
fffff880`03522720 fffff800`030e1dd6 : fffffa80`08c4b168 fffffa80`08c4b168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff880`03522790 fffffa80`05fd8a10 : 00000000`00000000 fffffa80`06173d20 fffffa80`06173d20 fffff880`046365c2 : nt!KiProcessExpiredTimerList+0xc6
fffff880`03522de0 00000000`00000000 : fffffa80`06173d20 fffffa80`06173d20 fffff880`046365c2 fffff880`010cecc0 : 0xfffffa80`05fd8a10
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`030d4920 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: 4c1c44a9
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
---------
Hai aggiornato qualche driver ultimamamente, mobo, sv ecc?
Nel caso di no prova ad aggiornare i driver principali.
Oppure prova a disabilitare AV e simili come firewall ecc.. se non sono MS
Jeremy01
16-10-2010, 10:34
Hai aggiornato qualche driver ultimamamente, mobo, sv ecc?
Nel caso di no prova ad aggiornare i driver principali.
Oppure prova a disabilitare AV e simili come firewall ecc.. se non sono MS
si ho aggiornato vari drivers....non si riesce a capire qual'è quello incriminato?
Inizia da quello della scheda video
Jeremy01
17-10-2010, 12:38
Inizia da quello della scheda video
in che senso.....disinstallo pulisco e reinstallo? (se si lo stesso o un altra versione)....
p.s. ma non si è in grado di sapere qual'è il driver in questione?
se si analizza il log di appcrashview che ne dite?
Version=1
EventType=BlueScreen
EventTime=129316564244818011
ReportType=4
Consent=1
UploadTime=129316564295518100
ReportIdentifier=19f2f058-d8ae-11df-b597-e0cb4e1f780f
IntegratorReportIdentifier=101610-24570-01
Response.type=4
Response.AnalysisBucket=X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
DynamicSig[1].Name=Versione SO
DynamicSig[1].Value=6.1.7600.2.0.0.256.1
DynamicSig[2].Name=ID impostazioni locali
DynamicSig[2].Value=1040
UI[2]=C:\Windows\system32\wer.dll
UI[3]=Windows è stato ripristinato in seguito a un arresto imprevisto del sistema
UI[4]=Windows: è possibile ricercare online una soluzione al problema.
UI[5]=&Cerca una soluzione
UI[6]=&Controlla in un secondo momento
UI[7]=Annulla
UI[8]=Windows è stato ripristinato in seguito a un arresto imprevisto del sistema
UI[9]=Si è verificato un problema che impedisce il funzionamento corretto di Windows. Se è disponibile una soluzione, si riceverà una notifica automatica.
UI[10]=Chiudi
Sec[0].Key=BCCode
Sec[0].Value=d1
Sec[1].Key=BCP1
Sec[1].Value=0000000000000001
Sec[2].Key=BCP2
Sec[2].Value=0000000000000002
Sec[3].Key=BCP3
Sec[3].Value=0000000000000008
Sec[4].Key=BCP4
Sec[4].Value=0000000000000001
Sec[5].Key=OS Version
Sec[5].Value=6_1_7600
Sec[6].Key=Service Pack
Sec[6].Value=0_0
Sec[7].Key=Product
Sec[7].Value=256_1
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=CA
State[1].Value=1
State[2].Key=BLOB
State[2].Value=CHKSUM=DA8C07C231AA8E4066132AA3C54B3ED8;BID=OCATAG;ID=248869b7-b777-4ac6-b1df-8110c529d6fe;SUB=10//15//2010 3:47:17 PM
File[0].CabName=101610-24570-01.dmp
File[0].Path=101610-24570-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\101610-24570-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-57720-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\DIGITAL\AppData\Local\Temp\WER-57720-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WER2386.tmp.WERInternalMetadata.xml
File[2].Flags=589827
File[2].Type=5
File[2].Original.Path=C:\Users\DIGITAL\AppData\Local\Temp\WER2386.tmp.WERInternalMetadata.xml
File[3].CabName=Report.cab
File[3].Path=Report.cab
File[3].Flags=196608
File[3].Type=7
File[3].Original.Path=Report.cab
FriendlyEventName=Arresto imprevisto del sistema
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
in che senso.....disinstallo pulisco e reinstallo? (se si lo stesso o un altra versione)....
Per ora disisntalla quallo nuovo e lascia quello precedente poi controlli come vanno le cose
Falcodicento
22-10-2010, 20:16
Un saluti a tutti, sono nuovo e spero di non fare casini!!:D
Ho comprato da qualche tempo una ati hd 5850 e installato win 7. Da allora sono cominciati i guai, di tanto in tanto mi crasha il pc e mi viene fuori la solita schermata blu. Ho seguito le istruzioni del primo post, ecco il risultato:
WARNING: Whitespace at end of path element
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e57e50
Debug session time: Fri Oct 22 14:15:06.607 2010 (UTC + 0:00)
System Uptime: 0 days 1:24:12.059
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - Operazione completata.
FAULTING_IP:
+3232393466623864
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f1b198 -- (.exr 0xfffff88002f1b198)
ExceptionAddress: fffff880017470f9 (NETIO!RtlGetNextExpiredTimerWheelEntry+0x00000000000000ea)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f1b240 -- (.trap 0xfffff88002f1b240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80049b9188 rbx=0000000000000000 rcx=fffffa80049b9188
rdx=effffa80049b9188 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017470f9 rsp=fffff88002f1b3d8 rbp=0000000000000000
r8=000000000007b58e r9=fffffa80049b9000 r10=fffff880009ee180
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
NETIO!RtlGetNextExpiredTimerWheelEntry+0xea:
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h] ds:effffa80`049b9198=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8246e to fffff80002c8a710
STACK_TEXT:
fffff880`02f1a288 fffff800`02c8246e : 00000000`00000000 00000000`00000000 fffff880`02f1aa00 fffff800`02cb7668 : nt!KeBugCheck
fffff880`02f1a290 fffff800`02cb040d : fffff800`02e98b7c fffff800`02dd2e84 fffff800`02c1a000 fffff880`02f1b198 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1a2c0 fffff800`02cb7a90 : fffff800`02dd9b14 fffff880`02f1a338 fffff880`02f1b198 fffff800`02c1a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1a2f0 fffff800`02cc49ef : fffff880`02f1b198 fffff880`02f1aa00 fffff880`00000000 fffffa80`048f09e8 : nt!RtlDispatchException+0x410
fffff880`02f1a9d0 fffff800`02c89d82 : fffff880`02f1b198 00000000`00000000 fffff880`02f1b240 00000000`0007b593 : nt!KiDispatchException+0x16f
fffff880`02f1b060 fffff800`02c8868a : fffffa80`049f6f30 00000000`95adc70c fffffa80`00000002 fffff880`02f1b2d0 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b240 fffff880`017470f9 : fffff880`01874183 fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1b3d8 fffff880`01874183 : fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 00000000`0007b593 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xea
fffff880`02f1b3e0 fffff880`01873c65 : fffffa80`04903bc8 00000000`00000001 00000000`002a3726 00000000`00000001 : tcpip!TcpProcessExpiredTcbTimers+0x83
fffff880`02f1b4b0 fffff800`02c9629e : fffff880`02f1b5c0 00000000`0004c26c 00000000`00000001 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x265
fffff880`02f1b530 fffff800`02c95dd6 : fffffa80`076b2168 fffffa80`076b2168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff880`02f1b5a0 fffff800`02c964be : 0000000b`c3431be5 fffff880`02f1bc18 00000000`0004f107 fffff880`009f0668 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02f1bbf0 fffff800`02c95cb7 : 00000003`412742c3 00000003`0004f107 00000003`4127428c 00000000`00000007 : nt!KiTimerExpiration+0x1be
fffff880`02f1bc90 fffff800`02c92eea : fffff880`009ee180 fffff880`009f8fc0 00000000`00000000 fffffa80`055d60f0 : nt!KiRetireDpcList+0x277
fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!RtlGetNextExpiredTimerWheelEntry+ea
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+ea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
FAILURE_BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - Operazione completata.
FAULTING_IP:
+3232393466623864
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f1b198 -- (.exr 0xfffff88002f1b198)
ExceptionAddress: fffff880017470f9 (NETIO!RtlGetNextExpiredTimerWheelEntry+0x00000000000000ea)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f1b240 -- (.trap 0xfffff88002f1b240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80049b9188 rbx=0000000000000000 rcx=fffffa80049b9188
rdx=effffa80049b9188 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017470f9 rsp=fffff88002f1b3d8 rbp=0000000000000000
r8=000000000007b58e r9=fffffa80049b9000 r10=fffff880009ee180
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
NETIO!RtlGetNextExpiredTimerWheelEntry+0xea:
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h] ds:effffa80`049b9198=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8246e to fffff80002c8a710
STACK_TEXT:
fffff880`02f1a288 fffff800`02c8246e : 00000000`00000000 00000000`00000000 fffff880`02f1aa00 fffff800`02cb7668 : nt!KeBugCheck
fffff880`02f1a290 fffff800`02cb040d : fffff800`02e98b7c fffff800`02dd2e84 fffff800`02c1a000 fffff880`02f1b198 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1a2c0 fffff800`02cb7a90 : fffff800`02dd9b14 fffff880`02f1a338 fffff880`02f1b198 fffff800`02c1a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1a2f0 fffff800`02cc49ef : fffff880`02f1b198 fffff880`02f1aa00 fffff880`00000000 fffffa80`048f09e8 : nt!RtlDispatchException+0x410
fffff880`02f1a9d0 fffff800`02c89d82 : fffff880`02f1b198 00000000`00000000 fffff880`02f1b240 00000000`0007b593 : nt!KiDispatchException+0x16f
fffff880`02f1b060 fffff800`02c8868a : fffffa80`049f6f30 00000000`95adc70c fffffa80`00000002 fffff880`02f1b2d0 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b240 fffff880`017470f9 : fffff880`01874183 fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1b3d8 fffff880`01874183 : fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 00000000`0007b593 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xea
fffff880`02f1b3e0 fffff880`01873c65 : fffffa80`04903bc8 00000000`00000001 00000000`002a3726 00000000`00000001 : tcpip!TcpProcessExpiredTcbTimers+0x83
fffff880`02f1b4b0 fffff800`02c9629e : fffff880`02f1b5c0 00000000`0004c26c 00000000`00000001 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x265
fffff880`02f1b530 fffff800`02c95dd6 : fffffa80`076b2168 fffffa80`076b2168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff880`02f1b5a0 fffff800`02c964be : 0000000b`c3431be5 fffff880`02f1bc18 00000000`0004f107 fffff880`009f0668 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02f1bbf0 fffff800`02c95cb7 : 00000003`412742c3 00000003`0004f107 00000003`4127428c 00000000`00000007 : nt!KiTimerExpiration+0x1be
fffff880`02f1bc90 fffff800`02c92eea : fffff880`009ee180 fffff880`009f8fc0 00000000`00000000 fffffa80`055d60f0 : nt!KiRetireDpcList+0x277
fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!RtlGetNextExpiredTimerWheelEntry+ea
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+ea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
FAILURE_BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - Operazione completata.
FAULTING_IP:
+3232393466623864
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f1b198 -- (.exr 0xfffff88002f1b198)
ExceptionAddress: fffff880017470f9 (NETIO!RtlGetNextExpiredTimerWheelEntry+0x00000000000000ea)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f1b240 -- (.trap 0xfffff88002f1b240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80049b9188 rbx=0000000000000000 rcx=fffffa80049b9188
rdx=effffa80049b9188 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017470f9 rsp=fffff88002f1b3d8 rbp=0000000000000000
r8=000000000007b58e r9=fffffa80049b9000 r10=fffff880009ee180
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
NETIO!RtlGetNextExpiredTimerWheelEntry+0xea:
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h] ds:effffa80`049b9198=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8246e to fffff80002c8a710
STACK_TEXT:
fffff880`02f1a288 fffff800`02c8246e : 00000000`00000000 00000000`00000000 fffff880`02f1aa00 fffff800`02cb7668 : nt!KeBugCheck
fffff880`02f1a290 fffff800`02cb040d : fffff800`02e98b7c fffff800`02dd2e84 fffff800`02c1a000 fffff880`02f1b198 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1a2c0 fffff800`02cb7a90 : fffff800`02dd9b14 fffff880`02f1a338 fffff880`02f1b198 fffff800`02c1a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1a2f0 fffff800`02cc49ef : fffff880`02f1b198 fffff880`02f1aa00 fffff880`00000000 fffffa80`048f09e8 : nt!RtlDispatchException+0x410
fffff880`02f1a9d0 fffff800`02c89d82 : fffff880`02f1b198 00000000`00000000 fffff880`02f1b240 00000000`0007b593 : nt!KiDispatchException+0x16f
fffff880`02f1b060 fffff800`02c8868a : fffffa80`049f6f30 00000000`95adc70c fffffa80`00000002 fffff880`02f1b2d0 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b240 fffff880`017470f9 : fffff880`01874183 fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1b3d8 fffff880`01874183 : fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 00000000`0007b593 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xea
fffff880`02f1b3e0 fffff880`01873c65 : fffffa80`04903bc8 00000000`00000001 00000000`002a3726 00000000`00000001 : tcpip!TcpProcessExpiredTcbTimers+0x83
fffff880`02f1b4b0 fffff800`02c9629e : fffff880`02f1b5c0 00000000`0004c26c 00000000`00000001 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x265
fffff880`02f1b530 fffff800`02c95dd6 : fffffa80`076b2168 fffffa80`076b2168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff880`02f1b5a0 fffff800`02c964be : 0000000b`c3431be5 fffff880`02f1bc18 00000000`0004f107 fffff880`009f0668 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02f1bbf0 fffff800`02c95cb7 : 00000003`412742c3 00000003`0004f107 00000003`4127428c 00000000`00000007 : nt!KiTimerExpiration+0x1be
fffff880`02f1bc90 fffff800`02c92eea : fffff880`009ee180 fffff880`009f8fc0 00000000`00000000 fffffa80`055d60f0 : nt!KiRetireDpcList+0x277
fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!RtlGetNextExpiredTimerWheelEntry+ea
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+ea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
FAILURE_BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - Operazione completata.
FAULTING_IP:
+3232393466623864
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f1b198 -- (.exr 0xfffff88002f1b198)
ExceptionAddress: fffff880017470f9 (NETIO!RtlGetNextExpiredTimerWheelEntry+0x00000000000000ea)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f1b240 -- (.trap 0xfffff88002f1b240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80049b9188 rbx=0000000000000000 rcx=fffffa80049b9188
rdx=effffa80049b9188 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017470f9 rsp=fffff88002f1b3d8 rbp=0000000000000000
r8=000000000007b58e r9=fffffa80049b9000 r10=fffff880009ee180
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
NETIO!RtlGetNextExpiredTimerWheelEntry+0xea:
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h] ds:effffa80`049b9198=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8246e to fffff80002c8a710
STACK_TEXT:
fffff880`02f1a288 fffff800`02c8246e : 00000000`00000000 00000000`00000000 fffff880`02f1aa00 fffff800`02cb7668 : nt!KeBugCheck
fffff880`02f1a290 fffff800`02cb040d : fffff800`02e98b7c fffff800`02dd2e84 fffff800`02c1a000 fffff880`02f1b198 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1a2c0 fffff800`02cb7a90 : fffff800`02dd9b14 fffff880`02f1a338 fffff880`02f1b198 fffff800`02c1a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1a2f0 fffff800`02cc49ef : fffff880`02f1b198 fffff880`02f1aa00 fffff880`00000000 fffffa80`048f09e8 : nt!RtlDispatchException+0x410
fffff880`02f1a9d0 fffff800`02c89d82 : fffff880`02f1b198 00000000`00000000 fffff880`02f1b240 00000000`0007b593 : nt!KiDispatchException+0x16f
fffff880`02f1b060 fffff800`02c8868a : fffffa80`049f6f30 00000000`95adc70c fffffa80`00000002 fffff880`02f1b2d0 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b240 fffff880`017470f9 : fffff880`01874183 fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1b3d8 fffff880`01874183 : fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 00000000`0007b593 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xea
fffff880`02f1b3e0 fffff880`01873c65 : fffffa80`04903bc8 00000000`00000001 00000000`002a3726 00000000`00000001 : tcpip!TcpProcessExpiredTcbTimers+0x83
fffff880`02f1b4b0 fffff800`02c9629e : fffff880`02f1b5c0 00000000`0004c26c 00000000`00000001 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x265
fffff880`02f1b530 fffff800`02c95dd6 : fffffa80`076b2168 fffffa80`076b2168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff880`02f1b5a0 fffff800`02c964be : 0000000b`c3431be5 fffff880`02f1bc18 00000000`0004f107 fffff880`009f0668 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02f1bbf0 fffff800`02c95cb7 : 00000003`412742c3 00000003`0004f107 00000003`4127428c 00000000`00000007 : nt!KiTimerExpiration+0x1be
fffff880`02f1bc90 fffff800`02c92eea : fffff880`009ee180 fffff880`009f8fc0 00000000`00000000 fffffa80`055d60f0 : nt!KiRetireDpcList+0x277
fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!RtlGetNextExpiredTimerWheelEntry+ea
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+ea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
FAILURE_BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - Operazione completata.
FAULTING_IP:
+3232393466623864
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f1b198 -- (.exr 0xfffff88002f1b198)
ExceptionAddress: fffff880017470f9 (NETIO!RtlGetNextExpiredTimerWheelEntry+0x00000000000000ea)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f1b240 -- (.trap 0xfffff88002f1b240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80049b9188 rbx=0000000000000000 rcx=fffffa80049b9188
rdx=effffa80049b9188 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880017470f9 rsp=fffff88002f1b3d8 rbp=0000000000000000
r8=000000000007b58e r9=fffffa80049b9000 r10=fffff880009ee180
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
NETIO!RtlGetNextExpiredTimerWheelEntry+0xea:
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h] ds:effffa80`049b9198=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8246e to fffff80002c8a710
STACK_TEXT:
fffff880`02f1a288 fffff800`02c8246e : 00000000`00000000 00000000`00000000 fffff880`02f1aa00 fffff800`02cb7668 : nt!KeBugCheck
fffff880`02f1a290 fffff800`02cb040d : fffff800`02e98b7c fffff800`02dd2e84 fffff800`02c1a000 fffff880`02f1b198 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1a2c0 fffff800`02cb7a90 : fffff800`02dd9b14 fffff880`02f1a338 fffff880`02f1b198 fffff800`02c1a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1a2f0 fffff800`02cc49ef : fffff880`02f1b198 fffff880`02f1aa00 fffff880`00000000 fffffa80`048f09e8 : nt!RtlDispatchException+0x410
fffff880`02f1a9d0 fffff800`02c89d82 : fffff880`02f1b198 00000000`00000000 fffff880`02f1b240 00000000`0007b593 : nt!KiDispatchException+0x16f
fffff880`02f1b060 fffff800`02c8868a : fffffa80`049f6f30 00000000`95adc70c fffffa80`00000002 fffff880`02f1b2d0 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b240 fffff880`017470f9 : fffff880`01874183 fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1b3d8 fffff880`01874183 : fffffa80`048f9a70 00000000`0007b593 fffffa80`048f09e8 00000000`0007b593 : NETIO!RtlGetNextExpiredTimerWheelEntry+0xea
fffff880`02f1b3e0 fffff880`01873c65 : fffffa80`04903bc8 00000000`00000001 00000000`002a3726 00000000`00000001 : tcpip!TcpProcessExpiredTcbTimers+0x83
fffff880`02f1b4b0 fffff800`02c9629e : fffff880`02f1b5c0 00000000`0004c26c 00000000`00000001 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x265
fffff880`02f1b530 fffff800`02c95dd6 : fffffa80`076b2168 fffffa80`076b2168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff880`02f1b5a0 fffff800`02c964be : 0000000b`c3431be5 fffff880`02f1bc18 00000000`0004f107 fffff880`009f0668 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02f1bbf0 fffff800`02c95cb7 : 00000003`412742c3 00000003`0004f107 00000003`4127428c 00000000`00000007 : nt!KiTimerExpiration+0x1be
fffff880`02f1bc90 fffff800`02c92eea : fffff880`009ee180 fffff880`009f8fc0 00000000`00000000 fffffa80`055d60f0 : nt!KiRetireDpcList+0x277
fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!RtlGetNextExpiredTimerWheelEntry+ea
fffff880`017470f9 8b4210 mov eax,dword ptr [rdx+10h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: NETIO!RtlGetNextExpiredTimerWheelEntry+ea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
FAILURE_BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
BUCKET_ID: X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
Followup: MachineOwner
---------
Ho il sospetto che siano i driver video perchè ho notato che con alcune versioni il problema si accentua di molto.
Help!!!!
Se i problemi sono iniziati in precisa coincidenza con l'installazione della scheda ati sembra quello il problema, possono essere i drive stessi della scheda video a procurare il problema
http://social.technet.microsoft.com/Forums/en/itprovistasp/thread/d1a3d449-c454-4022-9768-0a058a526c3d
Falcodicento
23-10-2010, 09:39
Ciao Eress, grazie per la risposta. Tu cosa mi consigli di fare? Ho installato la scheda video quando avevo xp ma non mi dava problemi, poi ho messo Win 7 e i relativi driver per il 64 bit e sono iniziati i problemi. Al momento i driver più stabili sono i 10.7, ho provato anche gli ultimi, i 10.10, ma niente da fare; i crash aumentano in modo esponenziale!:muro:
Probabilmnete dovrai aspettare l'uscita di nuovi driver per Seven
francesco88888
25-10-2010, 17:29
Salve a tutti voi ragazzi.
Sono un nuovo utente e mi sono imbattuto su questo forum grazie a google.
Ho un grandissimo problema,una schermata blu che mi ossessiona da quando ho acquistato il pc.:muro: :muro:
Il pc è stato inviato in assistenza formattato e riformattato e ho cercato ovunque la firma del problema ma niente!!!ho fatto controlli con BurnInTest e controlli sulla ram ma il pc dal punto di vista hardware sembra apposto.
Ho windows 7 pro 64 bit assulatemente originale.
Ecco la firma:
Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.256.48
ID impostazioni locali: 1040
Ulteriori informazioni sul problema:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8005CC2598
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\101710-19250-01.dmp
C:\Users\FraMarGia\AppData\Local\Temp\WER-72384-0.sysdata.xml
Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410
Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt
Scusate ma non so mettetterlo sottoforma di codice.
Ringrazio anticipatamente tutti voi!
massa_9219
26-10-2010, 11:55
Scusate sono nuovo, devo capire bene cm funziona ancora quì xD...cmq ho un problema relativo alla schermata blu...ho windows 7 home premium, quando accendo il computer dopo un pò che sta spento per esempio dalla sera lo riaccendo la mattina dopo mi fa la schermata blu e devo spegnere per forza, se riavvio continua a farci lo devo proprio spegnere...non so che fare, sarà qualche periferica qualche driver? ci fa solo quando è qualche ora che non lo accendo...
please help me! :cry:
Ragazzi leggete il primo post ;)
Loading89
27-10-2010, 20:39
Ragazzi chiedo scusa...
è possibile che il mio errore non c'è su http://support.microsoft.com/gp/errormessage ?
Errore:
********************************************************
STOP: 0x0000008E (0xC0000005, 0x92f27DCF, 0x99970968, 0x00000000)
win32k.sys - Address 92f27DCF base at 92E40000, Datestamp 49431a3f
********************************************************
Identico al tuo pare non ci sia, beh dovresti essere orgoglioso di questo; sei l'unico al mondo con quell'errore :D
Però vedi qui
http://www.faqwindows.com/schermata-blu-windows-vista-win32k-sys-blue-screen-win32k-sys-windows-vista.html
Loading89
27-10-2010, 23:01
Ho trovato quel link ieri... non è nulla di tutto ciò, continua a farlo...
paperottola
28-10-2010, 22:41
Da ieri senza un motivo apparente il pc si spegne da solo.
E' un portatile hp con windows 7.
Virus pare non ce ne siano.
Al riavvio ho provato a fare il ripristino ma nulla da fare.
Nel registro eventi ho trovato questo.
Nome registro: System
Origine: Microsoft-Windows-Kernel-Power
Data: 28/10/2010 20:54:16
ID evento: 41
Categoria attività:(63)
Livello: Critico
Parole chiave: (2)
Utente: SYSTEM
Computer: shadow-PC
Descrizione:
Riavvio del sistema senza un regolare arresto. Questo errore può essere causato da un'interruzione, un arresto anomalo o un'interruzione dell'alimentazione imprevista del sistema.
XML evento:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2010-10-28T18:54:16.438815700Z" />
<EventRecordID>254504</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>shadow-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">30</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>
Da ieri senza un motivo apparente il pc si spegne da solo.
E' un portatile hp con windows 7.
Virus pare non ce ne siano.
Al riavvio ho provato a fare il ripristino ma nulla da fare.
Nel registro eventi ho trovato questo.
Qui siamo nella sezione delle bsod :D e comunque dal log si capisce poco o nulla, potrebbe essere un problema hw come sw, magari hai un problema all'alimentatore :rolleyes:
paperottola
29-10-2010, 13:18
uhm in quale sezione devo postare?
la schermata blu mi ha dato questo errore:
STOP 0X000007E (0XFFFFFFFFC0000005,0X FFFFF80002C8A685, 0XFFFFF88005FB0648.0 XFFFFF88005FAFEB0)
Mettila su altre discussioni sull'informatica oppure nella sezione del tuo SO
Salve a tutti, ho un problema con il PC fisso, che si presenta saltuariamente. Il mouse comincia a muoversi a scatti, la musica anche a scatti fino al blocco totale del pc. A volte lo schermo diventa totalmente nero, a volta si blocca sull'ultima schermata visualizzata senza darmi possibilità di fare niente, e altre volte si spegne, come se avessi cliccato arresta il sistema, da Start. Alcune volte mi visualizza la famosa schermata blu e dopo essersi riavviato mi dice che Windows è stato ripristinato in seguito ad un arresto inaspettato. L'unica soluzione è spegnere il PC dal pulsante dell'alimentazione oppure, prima che si blocca totalmente, sospendere il PC (Standby) e riaccenderlo. Queste sono le caratteristiche del PC:
Intel Core i7 920
Asus Rampage II Gene
Ati Radeon HD5870
6 GB di RAM
Windows 7 Professional 64-bit
Norton Antivirus 2010
Dopo di ciò, ho formattato l'intero disco è ho reinstallato da zero Windows 7. Ho eseguito gli aggiornamenti da Windows Update e ho installato i driver della scheda video, senza installare il CCC. Non ho installato il Norton, ma Microsoft Security Essentials. Per fare in modo che il sistema non fosse influenzato da qualcosa, ho evitato di installare qualsiasi tipo di programma. Ho solo installato il Flash Player Adobe per Internet Explorer. Per il resto il PC è interamente pulito (non ho installato Office, Windows essentials, programmi aggiuntivi della scheda madre, niente di niente). L'indice prestazioni ottengo un ponteggio complessivo di 5,9.
http://img163.imageshack.us/img163/1212/immagineqqj.png
Nonostante tutto, il problema si è ripresentato oggi pomeriggio (ho formattato ieri intorno alle 22). Solito problema seguito dalla seguente BSOD.
http://img214.imageshack.us/img214/6289/img3040n.jpg
Analizzando con bluescreenview: http://img219.imageshack.us/img219/5052/immaginejp.png
Cosa posso fare?
E' appena succeso di nuovo.
Schermata blu: http://img837.imageshack.us/img837/4081/immagineccy.png
Bluescreenview: http://img155.imageshack.us/img155/8813/immaginegl.png
paperottola
30-10-2010, 19:08
Mettila su altre discussioni sull'informatica oppure nella sezione del tuo SO
io l'ho inserita nell'altra sezione ma vedo che in questa tutti parlano di schermate blu e windows7:confused: . Dove avrei sbagliato?
fraussantin
31-10-2010, 17:03
oggi ho avuto di nuovo questa bsod al ripristino di un'ibernazione http://d.imagehost.org/0412/Cattura.jpg
bsw
mi da sto bordello quaCrash List
Created by using BlueScreenView
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path
ntkrnlpa.exe ntkrnlpa.exe+44531 0x82234000 0x825ed000 0x003b9000 0x4c0e557c 08/06/2010 15.36.44 Microsoft® Windows® Operating System NT Kernel & System 6.0.6002.18267 (vistasp2_gdr.100608-0458) Microsoft Corporation C:\Windows\system32\ntkrnlpa.exe
hal.dll 0x82201000 0x82234000 0x00033000 0x49e018d9 11/04/2009 5.13.13 Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\hal.dll
kdcom.dll 0x80607000 0x8060e000 0x00007000 0x49e037d9 11/04/2009 7.25.29 Microsoft® Windows® Operating System Kernel Debugger HW Extension DLL 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\kdcom.dll
mcupdate_GenuineIntel.dll 0x8060e000 0x8067e000 0x00070000 0x49e03757 11/04/2009 7.23.19 Microsoft® Windows® Operating System Intel Microcode Update Library 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\mcupdate_GenuineIntel.dll
PSHED.dll 0x8067e000 0x8068f000 0x00011000 0x49e037dc 11/04/2009 7.25.32 Sistema operativo Microsoft® Windows® Driver errori hardware specifici di piattaforma 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\PSHED.dll
BOOTVID.dll 0x8068f000 0x80697000 0x00008000 0x4791a653 19/01/2008 8.27.15 Microsoft® Windows® Operating System VGA Boot Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\BOOTVID.dll
CLFS.SYS 0x80697000 0x806d8000 0x00041000 0x49e018ff 11/04/2009 5.13.51 Microsoft® Windows® Operating System Common Log File System Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\CLFS.SYS
CI.dll 0x806d8000 0x807b8000 0x000e0000 0x49e037d2 11/04/2009 7.25.22 Sistema operativo Microsoft® Windows® Modulo di controllo dell'integrità del codice 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\CI.dll
Wdf01000.sys 0x8a406000 0x8a477000 0x00071000 0x4a5bbf28 14/07/2009 0.11.36 Sistema operativo Microsoft® Windows® Runtime framework driver modalità kernel 1.9.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\Wdf01000.sys
WDFLDR.SYS 0x8a477000 0x8a485000 0x0000e000 0x4a5bbf1d 14/07/2009 0.11.25 Microsoft® Windows® Operating System Kernel Mode Driver Framework Loader 1.9.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\drivers\WDFLDR.SYS
sptd.sys 0x8a485000 0x8a585000 0x00100000 0x47cf3bb9 06/03/2008 1.32.57 C:\Windows\system32\drivers\sptd.sys
WMILIB.SYS 0x8a585000 0x8a58e000 0x00009000 0x47919044 19/01/2008 6.53.08 Microsoft® Windows® Operating System WMILIB WMI support library Dll 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\WMILIB.SYS
SCSIPORT.SYS 0x8a58e000 0x8a5b4000 0x00026000 0x47918f78 19/01/2008 6.49.44 Microsoft® Windows® Operating System SCSI Port Driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\SCSIPORT.SYS
acpi.sys 0x8a5b4000 0x8a5fa000 0x00046000 0x49e01a37 11/04/2009 5.19.03 Sistema operativo Microsoft® Windows® Driver ACPI per NT 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\acpi.sys
msisadrv.sys 0x807b8000 0x807c0000 0x00008000 0x47918b83 19/01/2008 6.32.51 Microsoft® Windows® Operating System ISA Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\msisadrv.sys
pci.sys 0x807c0000 0x807e7000 0x00027000 0x49e01a44 11/04/2009 5.19.16 Sistema operativo Microsoft® Windows® Enumeratore PCI Plug and Play per NT 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\pci.sys
partmgr.sys 0x807e7000 0x807f6000 0x0000f000 0x49e01ef7 11/04/2009 5.39.19 Microsoft® Windows® Operating System Partition Management Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\partmgr.sys
compbatt.sys 0x8a5fa000 0x8a5fc900 0x00002900 0x47918b7f 19/01/2008 6.32.47 Microsoft® Windows® Operating System Composite Battery Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\compbatt.sys
BATTC.SYS 0x807f6000 0x80800000 0x0000a000 0x47918b7d 19/01/2008 6.32.45 Microsoft® Windows® Operating System Battery Class Driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\BATTC.SYS
volmgr.sys 0x8a608000 0x8a617000 0x0000f000 0x47918f7f 19/01/2008 6.49.51 Microsoft® Windows® Operating System Volume Manager Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\volmgr.sys
volmgrx.sys 0x8a617000 0x8a661000 0x0004a000 0x49e01efd 11/04/2009 5.39.25 Microsoft® Windows® Operating System Volume Manager Extension Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\volmgrx.sys
intelide.sys 0x8a661000 0x8a668000 0x00007000 0x47918f76 19/01/2008 6.49.42 Microsoft® Windows® Operating System Intel PCI IDE Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\intelide.sys
PCIIDEX.SYS 0x8a668000 0x8a676000 0x0000e000 0x49e01eed 11/04/2009 5.39.09 Microsoft® Windows® Operating System PCI IDE Bus Driver Extension 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\PCIIDEX.SYS
mountmgr.sys 0x8a676000 0x8a686000 0x00010000 0x47918f59 19/01/2008 6.49.13 Microsoft® Windows® Operating System Mount Point Manager 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\mountmgr.sys
iastorv.sys 0x8a686000 0x8a726000 0x000a0000 0x45269a04 06/10/2006 19.01.40 Intel Matrix Storage Manager driver (base) Intel Matrix Storage Manager driver (base) 6.2.0.1015 Intel Corporation C:\Windows\system32\drivers\iastorv.sys
iastor.sys 0x8a726000 0x8a7e4000 0x000be000 0x45d0d237 12/02/2007 21.46.47 Intel Matrix Storage Manager driver Intel Matrix Storage Manager driver - ia32 7.0.0.1020 Intel Corporation C:\Windows\system32\drivers\iastor.sys
atapi.sys 0x8a7e4000 0x8a7ec000 0x00008000 0x49e01eed 11/04/2009 5.39.09 Microsoft® Windows® Operating System ATAPI IDE Miniport Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\atapi.sys
ataport.SYS 0x8a80e000 0x8a82c000 0x0001e000 0x49e01eee 11/04/2009 5.39.10 Microsoft® Windows® Operating System ATAPI Driver Extension 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\ataport.SYS
fltmgr.sys 0x8a82c000 0x8a85e000 0x00032000 0x49e01907 11/04/2009 5.13.59 Sistema operativo Microsoft® Windows® Gestione filtri file system Microsoft 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\fltmgr.sys
fileinfo.sys 0x8a85e000 0x8a86e000 0x00010000 0x47918be3 19/01/2008 6.34.27 Microsoft® Windows® Operating System FileInfo Filter Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\fileinfo.sys
psdfilter.sys 0x8a86e000 0x8a877000 0x00009000 0x47b98d02 18/02/2008 14.49.54 Acer eDataSecurity Management Acer eDataSecurity Management PSD Filter Driver 3, 0, 0, 0 Egis Incorporated C:\Windows\system32\drivers\psdfilter.sys
ksecdd.sys 0x8a877000 0x8a8e8000 0x00071000 0x4a364335 15/06/2009 13.48.53 Microsoft® Windows® Operating System Kernel Security Support Provider Interface 6.0.6002.18051 (vistasp2_gdr.090615-0258) Microsoft Corporation C:\Windows\system32\drivers\ksecdd.sys
ndis.sys 0x8a8e8000 0x8a9f3000 0x0010b000 0x49e02080 11/04/2009 5.45.52 Microsoft® Windows® Operating System NDIS 6.0 wrapper driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\ndis.sys
msrpc.sys 0x8aa05000 0x8aa30000 0x0002b000 0x00000000 Microsoft® Windows® Operating System Kernel Remote Procedure Call Provider 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\msrpc.sys
NETIO.SYS 0x8aa30000 0x8aa6b000 0x0003b000 0x49e0209d 11/04/2009 5.46.21 Microsoft® Windows® Operating System Network I/O Subsystem 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\NETIO.SYS
tcpip.sys 0x8aa6b000 0x8ab55000 0x000ea000 0x4c18d585 16/06/2010 14.45.41 Microsoft® Windows® Operating System TCP/IP Driver 6.0.6002.18272 (vistasp2_gdr.100616-0352) Microsoft Corporation C:\Windows\system32\drivers\tcpip.sys
fwpkclnt.sys 0x8ab55000 0x8ab70000 0x0001b000 0x49e02076 11/04/2009 5.45.42 Microsoft® Windows® Operating System FWP/IPsec Kernel-Mode API 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\fwpkclnt.sys
Ntfs.sys 0x8ac0e000 0x8ad1e000 0x00110000 0x49e0192a 11/04/2009 5.14.34 Sistema operativo Microsoft® Windows® Driver file system NT 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\Ntfs.sys
volsnap.sys 0x8ad1e000 0x8ad57000 0x00039000 0x49e01f09 11/04/2009 5.39.37 Sistema operativo Microsoft® Windows® Driver copia shadow del volume 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\volsnap.sys
spldr.sys 0x8ad57000 0x8ad5f000 0x00008000 0x467b17dd 22/06/2007 1.29.17 Microsoft® Windows® Operating System loader for security processor 6.0.6001.16606 (lh_security(sepbld-s).070621-1657) Microsoft Corporation C:\Windows\system32\drivers\spldr.sys
mup.sys 0x8ad5f000 0x8ad6e000 0x0000f000 0x49e01914 11/04/2009 5.14.12 Microsoft® Windows® Operating System Multiple UNC Provider driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\mup.sys
giveio.sys 0x8ad6e000 0x8ad6e680 0x00000680 0x316334f5 04/04/1996 3.33.25 C:\Windows\system32\giveio.sys
ecache.sys 0x8ad6f000 0x8ad96000 0x00027000 0x49e01f2c 11/04/2009 5.40.12 Microsoft® Windows® Operating System Special Memory Device Cache 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\ecache.sys
disk.sys 0x8ad96000 0x8ada7000 0x00011000 0x49e01ef2 11/04/2009 5.39.14 Microsoft® Windows® Operating System PnP Disk Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\disk.sys
CLASSPNP.SYS 0x8ada7000 0x8adc8000 0x00021000 0x49e01ee9 11/04/2009 5.39.05 Microsoft® Windows® Operating System SCSI Class System Dll 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\CLASSPNP.SYS
crcdisk.sys 0x8adc8000 0x8add1000 0x00009000 0x4549b1cb 02/11/2006 9.52.27 Microsoft® Windows® Operating System Disk Block Verification Filter Driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\crcdisk.sys
tunnel.sys 0x8eac7000 0x8ead2000 0x0000b000 0x4b7d244d 18/02/2010 12.28.13 Microsoft® Windows® Operating System Microsoft Tunnel Interface Driver 6.0.6002.18209 (vistasp2_gdr.100218-0019) Microsoft Corporation C:\Windows\system32\drivers\tunnel.sys
tunmp.sys 0x8ead2000 0x8eadb000 0x00009000 0x479190dc 19/01/2008 6.55.40 Microsoft® Windows® Operating System Microsoft Tunnel Interface Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\tunmp.sys
intelppm.sys 0x8eadb000 0x8eaea000 0x0000f000 0x47918a38 19/01/2008 6.27.20 Microsoft® Windows® Operating System Processor Device Driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\intelppm.sys
nvlddmkm.sys 0x8ec0b000 0x8f5a0420 0x00995420 0x4caebf95 08/10/2010 7.52.05 NVIDIA Windows Kernel Mode Driver, Version 260.89 NVIDIA Windows Kernel Mode Driver, Version 260.89 8.17.12.6089 NVIDIA Corporation C:\Windows\system32\drivers\nvlddmkm.sys
nvBridge.kmd 0x8f5a1000 0x8f5a2040 0x00001040 0x4caebf30 08/10/2010 7.50.24 NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 260.89 NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 260.89 8.17.12.6089 NVIDIA Corporation C:\Windows\system32\drivers\nvBridge.kmd
dxgkrnl.sys 0x8eaea000 0x8eb8b000 0x000a1000 0x4abc1c72 25/09/2009 2.27.14 Microsoft® Windows® Operating System DirectX Graphics Kernel 7.0.6002.18107 (vistasp2_gdr_win7ip_dgt(wmbla).090924-1550) Microsoft Corporation C:\Windows\system32\drivers\dxgkrnl.sys
watchdog.sys 0x8f5a3000 0x8f5af000 0x0000c000 0x49e01b13 11/04/2009 5.22.43 Microsoft® Windows® Operating System Watchdog Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\watchdog.sys
usbuhci.sys 0x8f5af000 0x8f5ba000 0x0000b000 0x47919050 19/01/2008 6.53.20 Microsoft® Windows® Operating System UHCI USB Miniport Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\usbuhci.sys
USBPORT.SYS 0x8f5ba000 0x8f5f8000 0x0003e000 0x49e01fcf 11/04/2009 5.42.55 Microsoft® Windows® Operating System USB 1.1 & 2.0 Port Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\USBPORT.SYS
usbehci.sys 0x8eb8b000 0x8eb9a000 0x0000f000 0x49e01fcc 11/04/2009 5.42.52 Microsoft® Windows® Operating System EHCI eUSB Miniport Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\usbehci.sys
HDAudBus.sys 0x8ab70000 0x8abfd000 0x0008d000 0x49e01fc1 11/04/2009 5.42.41 Microsoft® Windows® Operating System High Definition Audio Bus Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\HDAudBus.sys
NETw5v32.sys 0x8f601000 0x8f98a000 0x00389000 0x49219062 17/11/2008 16.40.18 Intel® Wireless WiFi Link Adapter Intel® Wireless WiFi Link Driver 12.2.0.11 Intel Corporation C:\Windows\system32\drivers\NETw5v32.sys
b57nd60x.sys 0x8f98a000 0x8f9e0000 0x00056000 0x4bf61ed6 21/05/2010 6.49.10 Broadcom NetXtreme Gigabit Ethernet Driver Broadcom NetXtreme Gigabit Ethernet NDIS6.x Unified Driver. 14.2.0.5 (cbuild.05202010-2246,b57nd6x-main-lhdepot1106.CL-113441) Broadcom Corporation C:\Windows\system32\drivers\b57nd60x.sys
ohci1394.sys 0x8f9e0000 0x8f9ef300 0x0000f300 0x49e01fd8 11/04/2009 5.43.04 Microsoft® Windows® Operating System 1394 OpenHCI Port Driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\ohci1394.sys
1394BUS.SYS 0x8f9f0000 0x8f9fd080 0x0000d080 0x47919057 19/01/2008 6.53.27 Microsoft® Windows® Operating System 1394 Bus Device Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\1394BUS.SYS
sdbus.sys 0x8eb9a000 0x8ebb4000 0x0001a000 0x49e01a42 11/04/2009 5.19.14 Microsoft® Windows® Operating System SecureDigital Bus Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\sdbus.sys
rimmptsk.sys 0x8ebb4000 0x8ebc3000 0x0000f000 0x45dfd03d 24/02/2007 6.42.21 RICOH SD/MMC Driver RICOH SD Driver 6.00.02.03 REDC C:\Windows\system32\drivers\rimmptsk.sys
rimsptsk.sys 0x8ebc3000 0x8ebd7000 0x00014000 0x45b5bbe3 23/01/2007 8.40.19 Ricoh Memorystick Controller RICOH MS Driver 6.00.01.10 REDC C:\Windows\system32\drivers\rimsptsk.sys
rixdptsk.sys 0x8fc09000 0x8fc5a000 0x00051000 0x46012cca 21/03/2007 14.02.02 R5C852 Ricoh xD Controller RICOH XD SM Driver 6.00.01.12 REDC C:\Windows\system32\drivers\rixdptsk.sys
winbondcir.sys 0x8fc5a000 0x8fc6f000 0x00015000 0x460a0264 28/03/2007 6.51.32 Winbond CIR Transceiver Winbond MCE CIR Port Driver 7.0.62.2012 build version 6000 built by: WinDDK Winbond Electronics Corporation C:\Windows\system32\drivers\winbondcir.sys
i8042prt.sys 0x8fc6f000 0x8fc82000 0x00013000 0x47918f5d 19/01/2008 6.49.17 Sistema operativo Microsoft® Windows® Driver della porta i8042 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\i8042prt.sys
DKbFltr.sys 0x8fc82000 0x8fc8c000 0x0000a000 0x4537363c 19/10/2006 9.24.28 Dritek Keyboard Filter Driver Dritek PS2 Keyboard Filter Driver 2, 0, 0, 119 Dritek System Inc. C:\Windows\system32\drivers\DKbFltr.sys
kbdclass.sys 0x8fc8c000 0x8fc97000 0x0000b000 0x47918f5a 19/01/2008 6.49.14 Sistema operativo Microsoft® Windows® Driver classe tastiera 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\kbdclass.sys
SynTP.sys 0x8fc97000 0x8fcd0b00 0x00039b00 0x4b7e06ec 19/02/2010 4.35.08 Synaptics Pointing Device Driver Synaptics Touchpad Driver 15.0.9 18Feb10 Synaptics Incorporated C:\Windows\system32\drivers\SynTP.sys
USBD.SYS 0x8fcd1000 0x8fcd2700 0x00001700 0x4791904d 19/01/2008 6.53.17 Microsoft® Windows® Operating System Universal Serial Bus Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\USBD.SYS
mouclass.sys 0x8fcd3000 0x8fcde000 0x0000b000 0x47918f5a 19/01/2008 6.49.14 Sistema operativo Microsoft® Windows® Driver Mouse Class 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\mouclass.sys
cdrom.sys 0x8fcde000 0x8fcf6000 0x00018000 0x49e01ef5 11/04/2009 5.39.17 Microsoft® Windows® Operating System SCSI CD-ROM Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\cdrom.sys
NTIDrvr.sys 0x8fcf6000 0x8fcf7800 0x00001800 0x41c8888a 21/12/2004 21.33.14 NTI CD-ROM Filter Driver 1, 0, 0, 6 NewTech Infosystems, Inc. C:\Windows\system32\drivers\NTIDrvr.sys
apq42nk2.SYS 0x8fcf8000 0x8fd2f000 0x00037000 0x4883d566 21/07/2008 1.16.38
CmBatt.sys 0x8fd2f000 0x8fd32780 0x00003780 0x47918b7f 19/01/2008 6.32.47 Microsoft® Windows® Operating System Control Method Battery Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\CmBatt.sys
wmiacpi.sys 0x8fd33000 0x8fd3c000 0x00009000 0x47918b7f 19/01/2008 6.32.47 Microsoft® Windows® Operating System Windows Management Interface for ACPI 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\wmiacpi.sys
msiscsi.sys 0x8fd3c000 0x8fd6b000 0x0002f000 0x49e01f27 11/04/2009 5.40.07 Microsoft® Windows® Operating System Microsoft iSCSI Initiator Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\msiscsi.sys
storport.sys 0x8fd6b000 0x8fdac000 0x00041000 0x49e01ef7 11/04/2009 5.39.19 Microsoft® Windows® Operating System Microsoft Storage Port Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\storport.sys
TDI.SYS 0x8fdac000 0x8fdb7000 0x0000b000 0x47919136 19/01/2008 6.57.10 Microsoft® Windows® Operating System TDI Wrapper 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\TDI.SYS
tbhsd.sys 0x8fdb7000 0x8fdc3000 0x0000c000 0x4a952768 26/08/2009 13.15.36 Tunebite High-Speed Dubbing Tunebite High-Speed Dubbing 6,0,1500,0 RapidSolution Software AG C:\Windows\system32\drivers\tbhsd.sys
portcls.sys 0x8fdc3000 0x8fdf0000 0x0002d000 0x49e01fc8 11/04/2009 5.42.48 Microsoft® Windows® Operating System Port Class (Class Driver for Port/Miniport Devices) 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\portcls.sys
drmk.sys 0x8ebd7000 0x8ebfc000 0x00025000 0x47919e4e 19/01/2008 7.53.02 Microsoft® Windows® Operating System Microsoft Kernel DRM Descrambler Filter 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\drmk.sys
ks.sys 0x90209000 0x90233000 0x0002a000 0x49e01ed7 11/04/2009 5.38.47 Microsoft® Windows® Operating System Kernel CSA Library 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\ks.sys
rasl2tp.sys 0x90233000 0x9024a000 0x00017000 0x47919111 19/01/2008 6.56.33 Microsoft® Windows® Operating System RAS L2TP mini-port/call-manager driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\rasl2tp.sys
ndistapi.sys 0x9024a000 0x90255000 0x0000b000 0x47919108 19/01/2008 6.56.24 Microsoft® Windows® Operating System NDIS 3.0 connection wrapper driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\ndistapi.sys
ndiswan.sys 0x90255000 0x90278000 0x00023000 0x49e020a7 11/04/2009 5.46.31 Microsoft® Windows® Operating System MS PPP Framing Driver (Strong Encryption) 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\ndiswan.sys
raspppoe.sys 0x90278000 0x90287000 0x0000f000 0x49e020a6 11/04/2009 5.46.30 Microsoft® Windows® Operating System RAS PPPoE mini-port/call-manager driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\raspppoe.sys
raspptp.sys 0x90287000 0x9029b000 0x00014000 0x47919112 19/01/2008 6.56.34 Microsoft® Windows® Operating System Peer-to-Peer Tunneling Protocol 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\raspptp.sys
rassstp.sys 0x9029b000 0x902b0000 0x00015000 0x49e020b0 11/04/2009 5.46.40 Microsoft® Windows® Operating System RAS SSTP Miniport Call Manager 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\rassstp.sys
termdd.sys 0x902b0000 0x902c0000 0x00010000 0x49e021c2 11/04/2009 5.51.14 Microsoft® Windows® Operating System Terminal Server Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\termdd.sys
swenum.sys 0x902c0000 0x902c1380 0x00001380 0x47918f60 19/01/2008 6.49.20 Microsoft® Windows® Operating System Plug and Play Software Device Enumerator 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\swenum.sys
circlass.sys 0x902c2000 0x902d0000 0x0000e000 0x47919054 19/01/2008 6.53.24 Microsoft® Windows® Operating System Consumer IR Class Driver for eHome 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\circlass.sys
mssmbios.sys 0x902d0000 0x902da000 0x0000a000 0x47918b87 19/01/2008 6.32.55 Microsoft® Windows® Operating System System Management BIOS Driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\mssmbios.sys
umbus.sys 0x902da000 0x902e7000 0x0000d000 0x47919064 19/01/2008 6.53.40 Microsoft® Windows® Operating System User-Mode Bus Enumerator 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\umbus.sys
usbhub.sys 0x902e7000 0x9031c000 0x00035000 0x49e01fe2 11/04/2009 5.43.14 Microsoft® Windows® Operating System Default Hub Driver for USB 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\usbhub.sys
NDProxy.SYS 0x9031c000 0x9032d000 0x00011000 0x4791910c 19/01/2008 6.56.28 Microsoft® Windows® Operating System NDIS Proxy 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\NDProxy.SYS
HdAudio.sys 0x9032d000 0x9036c000 0x0003f000 0x49e01fd5 11/04/2009 5.43.01 Microsoft® Windows® Operating System High Definition Audio Function Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\HdAudio.sys
HSXHWAZL.sys 0x9036c000 0x903a9000 0x0003d000 0x45e750ac 01/03/2007 23.16.12 SoftK56 Modem Driver HSF_HWAZL WDM driver 7.64.00 built by: WinDDK Conexant Systems, Inc. C:\Windows\system32\drivers\HSXHWAZL.sys
HSX_DPV.sys 0x90400000 0x90503000 0x00103000 0x45e750fb 01/03/2007 23.17.31 SoftK56 Modem Driver HSF_DP driver 7.64.00 built by: WinDDK Conexant Systems, Inc. C:\Windows\system32\drivers\HSX_DPV.sys
HSX_CNXT.sys 0x90503000 0x905b8000 0x000b5000 0x45e750a2 01/03/2007 23.16.02 SoftK56 Modem Driver HSF_CNXT driver 7.64.00 built by: WinDDK Conexant Systems, Inc. C:\Windows\system32\drivers\HSX_CNXT.sys
modem.sys 0x905b8000 0x905c5000 0x0000d000 0x4791913c 19/01/2008 6.57.16 Sistema operativo Microsoft® Windows® Driver del modem 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\modem.sys
hidir.sys 0x905c5000 0x905d0000 0x0000b000 0x4791904e 19/01/2008 6.53.18 Microsoft® Windows® Operating System Infrared Miniport Driver for Input Devices 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\hidir.sys
HIDCLASS.SYS 0x905d0000 0x905e0000 0x00010000 0x49e01fc7 11/04/2009 5.42.47 Microsoft® Windows® Operating System Hid Class Library 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\HIDCLASS.SYS
HIDPARSE.SYS 0x905e0000 0x905e6380 0x00006380 0x4791904c 19/01/2008 6.53.16 Microsoft® Windows® Operating System Hid Parsing Library 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\HIDPARSE.SYS
kbdhid.sys 0x905e7000 0x905f0000 0x00009000 0x49e01ed0 11/04/2009 5.38.40 Sistema operativo Microsoft® Windows® Driver del filtro della tastiera HID 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\kbdhid.sys
mouhid.sys 0x905f0000 0x905f8000 0x00008000 0x47918f5c 19/01/2008 6.49.16 Sistema operativo Microsoft® Windows® Driver del filtro del mouse HID 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\mouhid.sys
usbccgp.sys 0x903a9000 0x903c0000 0x00017000 0x4643c746 11/05/2007 2.30.46 Microsoft® Windows® Operating System USB Common Class Generic Parent Driver 6.0.6000.20596 (vista_ldr.070510-1510) Microsoft Corporation C:\Windows\system32\drivers\usbccgp.sys
usbvideo.sys 0x903c0000 0x903e0500 0x00020500 0x4549b278 02/11/2006 9.55.20 Microsoft® Windows® Operating System USB Video Class Driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\usbvideo.sys
AVerA310USB.sys 0x905f8000 0x905fe880 0x00006880 0x4a00e98d 06/05/2009 2.36.13 AVerMedia USB Class Device Driver AVerMedia USB driver 1, 1, 0, 30 AVerMedia TECHNOLOGIES, Inc. C:\Windows\system32\drivers\AVerA310USB.sys
AVerA310Cap.sys 0x903e1000 0x903ec800 0x0000b800 0x4a00e988 06/05/2009 2.36.08 AVerMedia DVB-T USB2.0 adapter BDA driver AVerMedia DVB-T BDA driver 1, 1, 0, 30 AVerMedia TECHNOLOGIES, Inc. C:\Windows\system32\drivers\AVerA310Cap.sys
BdaSup.SYS 0x903ed000 0x903f0000 0x00003000 0x4791905a 19/01/2008 6.53.30 Microsoft® Windows® Operating System Microsoft BDA Driver Support Library 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\BdaSup.SYS
Fs_Rec.SYS 0x903f0000 0x903f9000 0x00009000 0x47918a5d 19/01/2008 6.27.57 Microsoft® Windows® Operating System File System Recognizer Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\Fs_Rec.SYS
Null.SYS 0x903f9000 0x90400000 0x00007000 0x00000000 Microsoft® Windows® Operating System NULL Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\Null.SYS
Beep.SYS 0x90200000 0x90207000 0x00007000 0x47918f56 19/01/2008 6.49.10 Microsoft® Windows® Operating System BEEP Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\Beep.SYS
vga.sys 0x8fdf0000 0x8fdfc000 0x0000c000 0x47919006 19/01/2008 6.52.06 Microsoft® Windows® Operating System VGA/Super VGA Video Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\vga.sys
VIDEOPRT.SYS 0x8adde000 0x8adff000 0x00021000 0x4791900a 19/01/2008 6.52.10 Microsoft® Windows® Operating System Video Port Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\VIDEOPRT.SYS
RDPCDD.sys 0x8fc00000 0x8fc08000 0x00008000 0x47919224 19/01/2008 7.01.08 Microsoft® Windows® Operating System RDP Miniport 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\RDPCDD.sys
rdpencdd.sys 0x8f5f8000 0x8f600000 0x00008000 0x47919225 19/01/2008 7.01.09 Microsoft® Windows® Operating System RDP Miniport 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\rdpencdd.sys
Msfs.SYS 0x8ec00000 0x8ec0b000 0x0000b000 0x47918a68 19/01/2008 6.28.08 Microsoft® Windows® Operating System Mailslot driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\Msfs.SYS
Npfs.SYS 0x8ac00000 0x8ac0e000 0x0000e000 0x49e01909 11/04/2009 5.14.01 Microsoft® Windows® Operating System NPFS Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\Npfs.SYS
rasacd.sys 0x8ea00000 0x8ea09000 0x00009000 0x4791910f 19/01/2008 6.56.31 Microsoft® Windows® Operating System RAS Automatic Connection Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\rasacd.sys
tdx.sys 0x91c03000 0x91c19000 0x00016000 0x49e02084 11/04/2009 5.45.56 Microsoft® Windows® Operating System TDI Translation Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\tdx.sys
smb.sys 0x91c19000 0x91c2d000 0x00014000 0x49e02062 11/04/2009 5.45.22 Microsoft® Windows® Operating System SMB Transport driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\smb.sys
afd.sys 0x91c2d000 0x91c75000 0x00048000 0x49e020c5 11/04/2009 5.47.01 Sistema operativo Microsoft® Windows® Ancillary Function Driver for WinSock 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\afd.sys
netbt.sys 0x91c75000 0x91ca7000 0x00032000 0x49e0206f 11/04/2009 5.45.35 Microsoft® Windows® Operating System MBT Transport driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\netbt.sys
pacer.sys 0x91ca7000 0x91cbd000 0x00016000 0x49e0207f 11/04/2009 5.45.51 Sistema operativo Microsoft® Windows® Utilità di pianificazione pacchetti QoS 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\pacer.sys
netbios.sys 0x91cbd000 0x91ccb000 0x0000e000 0x479190e1 19/01/2008 6.55.45 Microsoft® Windows® Operating System NetBIOS interface driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\netbios.sys
wanarp.sys 0x91ccb000 0x91cde000 0x00013000 0x4791910f 19/01/2008 6.56.31 Microsoft® Windows® Operating System MS Remote Access and Routing ARP Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\wanarp.sys
ssmdrv.sys 0x91cde000 0x91ce3a00 0x00005a00 0x4a000f5e 05/05/2009 11.05.18 AVIRA SnapShot Driver 7.00.02.02 Avira GmbH C:\Windows\system32\drivers\ssmdrv.sys
rdbss.sys 0x91ce4000 0x91d20000 0x0003c000 0x49e01922 11/04/2009 5.14.26 Microsoft® Windows® Operating System Redirected Drive Buffering SubSystem Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\rdbss.sys
nsiproxy.sys 0x91d20000 0x91d2a000 0x0000a000 0x479190e6 19/01/2008 6.55.50 Microsoft® Windows® Operating System NSI Proxy 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\nsiproxy.sys
dfsc.sys 0x91d2a000 0x91d41000 0x00017000 0x49e01914 11/04/2009 5.14.12 Microsoft® Windows® Operating System DFS Namespace Client Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\dfsc.sys
avipbb.sys 0x91d41000 0x91d5d000 0x0001c000 0x49c9008b 24/03/2009 16.47.23 Avira Driver for RootKit Detection 1.0.2.86 Avira GmbH C:\Windows\system32\drivers\avipbb.sys
avgio.sys 0x91d5d000 0x91d5e800 0x00001800 0x45ddaf5c 22/02/2007 15.57.32
hidusb.sys 0x91d6b000 0x91d74000 0x00009000 0x49e01fc8 11/04/2009 5.42.48 Microsoft® Windows® Operating System USB Miniport Driver for Input Devices 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\hidusb.sys
xusb21.sys 0x91d74000 0x91d81c80 0x0000dc80 0x49dcb4df 08/04/2009 15.29.51 Windows Common Controller Driver Windows Common Controller 9.18.1015.0 (XUSB_MAIN(dxblder).090408-0729) Microsoft Corporation C:\Windows\system32\drivers\xusb21.sys
LHidFilt.Sys 0x91d82000 0x91d89080 0x00007080 0x4a391e80 17/06/2009 17.49.04 Logitech SetPoint(TM) Logitech HID Filter Driver. 4.82.4.00 Logitech, Inc. C:\Windows\system32\drivers\LHidFilt.Sys
LMouFilt.Sys 0x91d8a000 0x91d91800 0x00007800 0x4a391e84 17/06/2009 17.49.08 Logitech SetPoint(TM) Logitech Mouse Filter Driver. 4.82.4.00 Logitech, Inc. C:\Windows\system32\drivers\LMouFilt.Sys
crashdmp.sys 0x91d92000 0x91d9f000 0x0000d000 0x49e01ef0 11/04/2009 5.39.12 Microsoft® Windows® Operating System Crash Dump Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\crashdmp.sys
dump_iaStor.sys 0x8ea09000 0x8eac7000 0x000be000 0x45d0d237 12/02/2007 21.46.47
win32k.sys 0x9ae10000 0x9b013000 0x00203000 0x4c7d033d 31/08/2010 14.27.25 Sistema operativo Microsoft® Windows® Driver Win32 multiutente 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\win32k.sys
Dxapi.sys 0x91d9f000 0x91da9000 0x0000a000 0x47918c4c 19/01/2008 6.36.12 Microsoft® Windows® Operating System DirectX API Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\Dxapi.sys
monitor.sys 0x91da9000 0x91db8000 0x0000f000 0x47919013 19/01/2008 6.52.19 Microsoft® Windows® Operating System Monitor Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\monitor.sys
TSDDD.dll 0x9b030000 0x9b039000 0x00009000 0x47919225 19/01/2008 7.01.09 Microsoft® Windows® Operating System Framebuffer Display Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\TSDDD.dll
cdd.dll 0x9b050000 0x9b05e000 0x0000e000 0x00000000 Microsoft® Windows® Operating System Canonical Display Driver 7.0.6002.18107 (vistasp2_gdr_win7ip_dgt(wmbla).090924-1550) Microsoft Corporation C:\Windows\system32\cdd.dll
ATMFD.DLL 0x9b060000 0x9b0ac000 0x0004c000 0x4bfd348d 26/05/2010 15.47.41 Adobe Type Manager Windows NT OpenType/Type 1 Font Driver 5.1 Build 228 Adobe Systems Incorporated C:\Windows\system32\ATMFD.DLL
luafv.sys 0x91db8000 0x91dd3000 0x0001b000 0x47918afb 19/01/2008 6.30.35 Sistema operativo Microsoft® Windows® Driver filtro virtualizzazione file LUA 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\luafv.sys
avgntflt.sys 0x91dd3000 0x91de7000 0x00014000 0x4b052f89 19/11/2009 12.44.09 AntiVir Workstation Avira Minifilter Driver 9.00.03.17 Avira GmbH C:\Windows\system32\drivers\avgntflt.sys
spsys.sys 0xa0a03000 0xa0ab3000 0x000b0000 0x49b69f04 10/03/2009 18.10.28 Microsoft® Windows® Operating System security processor 6.0.6002.17040 (longhorn(sepbld-s).090310-1002) Microsoft Corporation C:\Windows\system32\drivers\spsys.sys
lltdio.sys 0xa0ab3000 0xa0ac3000 0x00010000 0x479190b7 19/01/2008 6.55.03 Microsoft® Windows® Operating System Link-Layer Topology Mapper I/O Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\lltdio.sys
nwifi.sys 0xa0ac3000 0xa0aed000 0x0002a000 0x49e01fef 11/04/2009 5.43.27 Microsoft® Windows® Operating System NativeWiFi Miniport Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\nwifi.sys
ndisuio.sys 0xa0aed000 0xa0af7000 0x0000a000 0x479190dc 19/01/2008 6.55.40 Microsoft® Windows® Operating System NDIS User mode I/O driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\ndisuio.sys
rspndr.sys 0xa0af7000 0xa0b0a000 0x00013000 0x479190b7 19/01/2008 6.55.03 Microsoft® Windows® Operating System Link-Layer Topology Responder Driver for NDIS 6 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\rspndr.sys
HTTP.sys 0xa0b0a000 0xa0b77000 0x0006d000 0x4b804bcb 20/02/2010 21.53.31 Sistema operativo Microsoft® Windows® Stack del protocollo HTTP 6.0.6002.18136 (vistasp2_gdr.091102-2300) Microsoft Corporation C:\Windows\system32\drivers\HTTP.sys
srvnet.sys 0xa0b77000 0xa0b94000 0x0001d000 0x4c84f06e 06/09/2010 14.45.18 Microsoft® Windows® Operating System Server Network driver 6.0.6002.18306 (vistasp2_gdr.100906-0403) Microsoft Corporation C:\Windows\system32\drivers\srvnet.sys
bowser.sys 0xa0b94000 0xa0bad000 0x00019000 0x47918a7a 19/01/2008 6.28.26 Microsoft® Windows® Operating System NT Lan Manager Datagram Receiver Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\bowser.sys
mpsdrv.sys 0xa0bad000 0xa0bc2000 0x00015000 0x479190a5 19/01/2008 6.54.45 Microsoft® Windows® Operating System Microsoft Protection Service Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\mpsdrv.sys
mrxdav.sys 0xa0bc2000 0xa0be3000 0x00021000 0x49e0192f 11/04/2009 5.14.39 Microsoft® Windows® Operating System Windows NT WebDav Minirdr 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\mrxdav.sys
mrxsmb.sys 0xa3409000 0xa3428000 0x0001f000 0x4b83b794 23/02/2010 12.10.12 Microsoft® Windows® Operating System Windows NT SMB Minirdr 6.0.6002.18213 (vistasp2_gdr.100223-0035) Microsoft Corporation C:\Windows\system32\drivers\mrxsmb.sys
mrxsmb10.sys 0xa3428000 0xa3461000 0x00039000 0x4b83b799 23/02/2010 12.10.17 Microsoft® Windows® Operating System Longhorn SMB Downlevel SubRdr 6.0.6002.18213 (vistasp2_gdr.100223-0035) Microsoft Corporation C:\Windows\system32\drivers\mrxsmb10.sys
mrxsmb20.sys 0xa3461000 0xa3479000 0x00018000 0x4b83b794 23/02/2010 12.10.12 Microsoft® Windows® Operating System Longhorn SMB 2.0 Redirector 6.0.6002.18213 (vistasp2_gdr.100223-0035) Microsoft Corporation C:\Windows\system32\drivers\mrxsmb20.sys
srv2.sys 0xa3479000 0xa34a1000 0x00028000 0x4c84f071 06/09/2010 14.45.21 Microsoft® Windows® Operating System Smb 2.0 Server driver 6.0.6002.18306 (vistasp2_gdr.100906-0403) Microsoft Corporation C:\Windows\system32\drivers\srv2.sys
srv.sys 0xa34a1000 0xa34ef000 0x0004e000 0x4c84f080 06/09/2010 14.45.36 Microsoft® Windows® Operating System Server driver 6.0.6000.16386 (vista_rtm.061101-2205) Microsoft Corporation C:\Windows\system32\drivers\srv.sys
atksgt.sys 0xa3507000 0xa354a000 0x00043000 0x4a06e9d2 10/05/2009 15.50.58 C:\Windows\system32\drivers\atksgt.sys
cdfs.sys 0xa354a000 0xa3560000 0x00016000 0x47918a62 19/01/2008 6.28.02 Microsoft® Windows® Operating System CD-ROM File System Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\cdfs.sys
int15.sys 0xa3560000 0xa3567000 0x00007000 0x4689ae6c 03/07/2007 3.03.24 int15 int15 1.00.0001,0001 built by: WinDDK Acer, Inc. C:\Windows\system32\drivers\int15.sys
lirsgt.sys 0xa3567000 0xa356b880 0x00004880 0x49b29007 07/03/2009 16.17.27 C:\Windows\system32\drivers\lirsgt.sys
mdmxsdk.sys 0xa356c000 0xa356f180 0x00003180 0x449716a3 19/06/2006 22.26.59 Diagnostic Interface x86 Driver Diagnostic Interface x86 Driver 1.0.2.012 Conexant C:\Windows\system32\drivers\mdmxsdk.sys
peauth.sys 0xab80a000 0xab8e8000 0x000de000 0x453c8384 23/10/2006 9.55.32 Microsoft® Windows® Operating System Protected Environment Authentication and Authorization Export Driver 6.0.5840.16385 (VISTA_RTM_CLIENT_akaDMD.061022-1800) Microsoft Corporation C:\Windows\system32\drivers\peauth.sys
PSDNServ.sys 0xab8e8000 0xab8f1000 0x00009000 0x47b98d2b 18/02/2008 14.50.35 Acer eDataSecurity Management Acer eDataSecurity Management PSD Named Pipe Driver 3, 0, 0, 0 Egis Incorporated C:\Windows\system32\drivers\PSDNServ.sys
psdvdisk.sys 0xab8f1000 0xab903000 0x00012000 0x47b98d40 18/02/2008 14.50.56 Acer eDataSecurity Management Acer eDataSecurity Management PSD Virtual Disk Driver 3, 0, 0, 0 Egis Incorporated C:\Windows\system32\drivers\psdvdisk.sys
secdrv.SYS 0xab903000 0xab90d000 0x0000a000 0x45080528 13/09/2006 14.18.32 Macrovision SECURITY Driver Macrovision SECURITY Driver 4.03.086 Macrovision Corporation, Macrovision Europe Limited, and Macrovision Japan and Asia K.K. C:\Windows\system32\drivers\secdrv.SYS
tcpipreg.sys 0xab90d000 0xab919000 0x0000c000 0x4b1e8c3a 08/12/2009 18.26.18 Microsoft® Windows® Operating System TCP/IP Registry Compatibility Driver 6.0.6002.18160 (vistasp2_gdr.091208-0542) Microsoft Corporation C:\Windows\system32\drivers\tcpipreg.sys
xaudio.sys 0xab919000 0xab921000 0x00008000 0x45bfa940 30/01/2007 21.23.28 SoftK56 Modem Driver Modem Audio Device Driver 1.00.04.00 built by: WinDDK Conexant Systems, Inc. C:\Windows\system32\drivers\xaudio.sys
000.fcl 0xab921000 0xab94d000 0x0002c000 0x48dcdf70 26/09/2008 14.11.12
000.fcl 0xab94d000 0xab96e000 0x00021000 0x479872f8 24/01/2008 12.14.00
RTCore32.sys 0xab96e000 0xab96f200 0x00001200 0x42941d89 25/05/2005 7.39.05
cpuz_x32.sys 0xab970000 0xab972680 0x00002680 0x47beadd3 22/02/2008 12.11.15
tdtcp.sys 0xab973000 0xab97e000 0x0000b000 0x47919224 19/01/2008 7.01.08 Microsoft® Windows® Operating System TCP Transport Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\tdtcp.sys
tssecsrv.sys 0xab97e000 0xab98a000 0x0000c000 0x4791922b 19/01/2008 7.01.15 Microsoft® Windows® Operating System TS Security Filter Driver 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft Corporation C:\Windows\system32\drivers\tssecsrv.sys
RDPWD.SYS 0xab98a000 0xab9bd000 0x00033000 0x49e021ca 11/04/2009 5.51.22 Microsoft® Windows® Operating System RDP Terminal Stack Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\RDPWD.SYS
fastfat.SYS 0xab9bf000 0xab9e7000 0x00028000 0x49e01900 11/04/2009 5.13.52 Microsoft® Windows® Operating System Fast FAT File System Driver 6.0.6002.18005 (lh_sp2rtm.090410-1830) Microsoft Corporation C:\Windows\system32\drivers\fastfat.SYS
RivaTuner32.sys 0xab9e7000 0xab9e9380 0x00002380 0x469d14dd 17/07/2007 20.13.33
InfoOMatic987
02-11-2010, 16:37
Salve, la mia preparazione è al livello medio, quindi spero che nel rispondere a a questo dubbio teniate conto che non riuscirò a capire tutto
e che alcuni termini non li conosco. Ma passiamo alla domanda:
Allora, verso novembre 2007 mi è stato regalato un computer con le seguenti caratteristiche:
Modello: Acer Aspire M5620
HDD: 320GB ripartito in 2 sezioni
RAM: 2 schede ram da 1GB, Samsung DDR2 e successivamente altre 2 schede ram da 1GB, Kingstone DDR2 assicuro che l'unica differenza è il nome
Scheda madre: Acer G33T-AM
Chipset: Intel Bearlake G33
Processore: QuadCore Intel Core 2 Quad Q6600, 2400Mhz (9x267) 64 bit compatible o capable
Scheda video: GeForce 8600GS 512MB
OS: Windows vista 32 bit successivamente Windows 7 64 bit
Antivirus: Nortin antivirus per vista a 32 bit, successivamente Symantec security per windows 7 a 64 bit e successivamente Avast!
Network Adapter: Atheros AR5007UG Wireless
Allora la mia storia è questa, da poco più di 2 settimane, dopo l’upgrade a WIN7, è apparso il mio primo bsod, se non sbaglio in quel momento ero su internet a guardare un'episodio di C.S.I. Miami. La risoluzione dei problemi di windows mi diceva di installare un prodotto della intel: "Intel rapid storage" (o forse più conosciuto come) RAID. Non ho mai dato molta importanza ai bsod, pensavo che fossero temporanei quindi non ho assolutamente guardato cosa volesse dire al momento (in quanto era attivo il riavvio automatico di windows) e ho installato il programma (che poco dopo ho disinstallato in quanto ho notato che non risolveva nulla).
A partire dal secondo (inaspettato) bsod, ho deciso di capire cosa significavano e da cosa erano causati. Su internet ho trovato un programma "BlueScreenView" (che va bene come tool?) che mi ha permesso di vedere che la causa del problema era ntoskrnl.exe e che (a volte) era accompagnato da altri "file" come ntfs.sys etc. Allora ho chiesto aiuto all'amico (di cui mi fido molto, essendo esperto in tutto ciò che è informatico, ovvero babytecnico!) che mi ha spiegato che il ntoskrnl.exe non è "nient'altro" che il cuore del sistema operativo, e che quindi c'era qualcosa di harware o sofware o driver che entrava in conflitto con altro e faceva crashare il kernel.
Allora ho fatto TUTTI ma prorio TUTTI i controlli del caso con TUTTI possibili tools e software. (quali memtest/scheda video stress/HDD etc..)
Non avendo riscontrato problemi a livello hardware, ci siamo concentrati sul livello software, togliendo dai programmi "più strani" ai più insoliti e controllando UNO PER UNO tutti i driver alla ricerca di quello outdate o non funzionante. (ho usato anche un programma chiamato DriverEasy) che mi ha aiutato parecchio. Ma dopo tutto l'umanamente possibile io (anche se il mio amico no) ho rinunciato a capire le cause del problema. (tranne qualche ideuzza astrusa che non dava il risultato sperato).
Sottolineo che in quel periodo fino ad oggi ho sempre avuto bsod mentre usavo il pc non solo per guardare C.S.I. Miami (cosa che facevo e stò facendo continuamente) ma anche quando guardavo l'e-mail, mentre non facevo assolutamente nulla, installo qualcosa o se inserisco un disco esterno da 1TB per salvare alcuni dati del computer.
La mia domanda finale è: qualcuno ha la più pallida idea che cosa deve fare un poveraccio per risolvere questo "problemino"?
Le soluzioni più "dirette" sono le più gradite, ma anche quelle indirette vanno bene però evidenzio che:
1) converrebbe formattare il pc? entrembe le ripartizioni? o solo quella con win7?
2) non ho mai formattato la ripartizione 2 e ho paura che il problema sia li
3) non posso fornire tutti i nomi de bsod avuti perchè BlueScreenView mi fa vedere solo i più recenti
4) l'ultimo (il più "specifico") era Bugcode_Usb_Driver 0x0..0fe
5) tutti i bsod sono random e imprevedibili e che tra uno e l'altro il tempo che li separa è sempre diverso
6) Non dispongo di un'altra network adapter o della possibilità di collegarmi a internet via cavo
7) Assicuro che non ci sono virus nel mio sitema
non so cosa altro aggiungere, ringrazio tutti in anticipo per l'attenzione e le possibili soluzioni
perchè non so più dove sbattere la testa! grazie!
babytecnico
02-11-2010, 16:41
scusate l'off-topic... :ot:
il problema del mio amico, InfoOMatic987, è molto molto... strano.
insieme a lui, ho controllato gli aspetti più svariati, senza denotare nulla di anomalo.
Ifrit_90
04-11-2010, 07:29
Aiutatemi ragazzi vi prego ecco il mio problema:
http://i53.tinypic.com/2qdtqw0.jpg
Ho Windows vista e il problema si è presentato una volta all'avvio del pc.
Per analizzare il file minidump ho usato "BlueScreenView" ed ecco il problema:
http://i56.tinypic.com/2z53amr.jpg
E questa è la terza schermata blu in un anno che fortuna :(
Questa volta sembra avast il problema; ormai neanche più degli antivirus ti puoi fidare.
Ragazzi vi prego aiutatemi :help: :help:
Grazie a chi mi risponderà.
Da agosto il pc in firma con vista 64 ultimate ha cominciato a dare qualche BSOD...all'inizio non ci ho dato peso, imputando a qualche gioco magari non ben ottimizzato, ma ora i problemi stanno diventando seri! Praticamente ogni applicazione (diciamo gioco) 3D ha la tendenza a chiudersi con qualche errore e spesso mi spara fuori un bel BSOD...se non succede durante il gioco mi è capitato anche all'uscita da windows.
Se non uso giochi (direi D3D), il problema pare non ci sia.
Ho aggiornato drivers audio e video all'ultima versione e il SO è aggiornatissimo, così come le DX.
Ho iniziato a monitorare i drivers incriminati con Driver Verifier, ma non ci capisco molto, anzi nulla!
Vi allego i dump presi con bluescreenview
==================================================
Dump File : Mini110210-01.dmp
Crash Time : 02/11/2010 22.52.22
Bug Check String :
Bug Check Code : 0x0000010e
Caused By Driver : watchdog.sys
Full Path : C:\Windows\Minidump\Mini110210-01.dmp
==================================================
==================================================
Dump File : Mini110110-02.dmp
Crash Time : 01/11/2010 10.48.54
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Caused By Driver : ntoskrnl.exe
Full Path : C:\Windows\Minidump\Mini110110-02.dmp
==================================================
==================================================
Dump File : Mini110110-01.dmp
Crash Time : 01/11/2010 0.45.41
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Caused By Driver : afd.sys
Full Path : C:\Windows\Minidump\Mini110110-01.dmp
==================================================
==================================================
Dump File : Mini103110-01.dmp
Crash Time : 31/10/2010 17.52.50
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Caused By Driver : ntoskrnl.exe
Full Path : C:\Windows\Minidump\Mini103110-01.dmp
==================================================
==================================================
Dump File : Mini102310-01.dmp
Crash Time : 23/10/2010 12.54.24
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Caused By Driver : ntoskrnl.exe
Full Path : C:\Windows\Minidump\Mini102310-01.dmp
==================================================
==================================================
Dump File : Mini102010-01.dmp
Crash Time : 20/10/2010 21.32.31
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Caused By Driver : dxgkrnl.sys
Full Path : C:\Windows\Minidump\Mini102010-01.dmp
==================================================
==================================================
Dump File : Mini101610-01.dmp
Crash Time : 16/10/2010 15.22.30
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Caused By Driver : dxgkrnl.sys
Full Path : C:\Windows\Minidump\Mini101610-01.dmp
==================================================
==================================================
Dump File : Mini101010-01.dmp
Crash Time : 10/10/2010 11.14.00
Bug Check String :
Bug Check Code : 0x0000010e
Caused By Driver : watchdog.sys
Full Path : C:\Windows\Minidump\Mini101010-01.dmp
==================================================
==================================================
Dump File : Mini100510-01.dmp
Crash Time : 05/10/2010 18.38.16
Bug Check String :
Bug Check Code : 0x0000010e
Caused By Driver : watchdog.sys
Full Path : C:\Windows\Minidump\Mini100510-01.dmp
==================================================
Any idea? :muro:
IL_DUCA_91
05-11-2010, 18:21
Ciao a tutti ho un problema al pc che non riesco a risolvere... in pratica quando gioco, spesso mi capita che il pc si blocca e compare la schermata blu accompagnata da uno stordente rumore alle casse, dopo il pc si riavvia e mi appare una finestra di windows che allego qui sotto.
Questa è la mia configurazione hardware:
scheda madre asus P5QL-E
scheda video Ati HD5850 1 GB
processore Intel Core 2 Duo E7300 2.66Ghz, 260Mhz
Ram 2 GB ddr2
Hard disk Maxtor 6 L250R0 SCSI
Ho notato che quando succede ciò al riavvio EPU-6 engine non è aperto e lo devo andare ad attivare io!!
Quale potrebbe essere il problema?
IL_DUCA_91
05-11-2010, 18:21
Ciao a tutti ho un problema al pc che non riesco a risolvere... in pratica quando gioco, spesso mi capita che il pc si blocca e compare la schermata blu accompagnata da uno stordente rumore alle casse, dopo il pc si riavvia e mi appare una finestra di windows che allego qui sotto.
Questa è la mia configurazione hardware:
scheda madre asus P5QL-E
scheda video Ati HD5850 1 GB
processore Intel Core 2 Duo E7300 2.66Ghz, 260Mhz
Ram 2 GB ddr2
Hard disk Maxtor 6 L250R0 SCSI
Ho notato che quando succede ciò al riavvio EPU-6 engine non è aperto e lo devo andare ad attivare io!!
Quale potrebbe essere il problema?
IL_DUCA_91
05-11-2010, 18:24
Ecco l'altra parte della finestra:)
Da quelle finestre non si può capire nulla, segui la guida del primo post di questa discussione e analizza il file dmp o postalo qui zippato
Mi hanno detto di postare qui, discussione che tra l'altro l'ho cercata ma non la trovavo e mi scuso.
http://www.hwupgrade.it/forum/showpost.php?p=33566119&postcount=1
Qualcuno sa da cosa è causato e da cosa lo capisco?
Vedi qui
http://www.computerhope.com/issues/ch000646.htm
InfoOMatic987
08-11-2010, 18:25
A partire dalla descrizione poco sopra, aggiungo che ieri 8/11/2010 mi è comparso un bsod abbastanza (credo) grave che diceva: DRIVER_CORRUPTED_EXPOOL. Questo messaggio è comparso mentre guardavo una puntata di un telefilm su megavideo. poco fa invece mi è comparso un'altro errore CACHE_MANAGER. E' vero che sono entrambi problemi di memoria ma assicuro che la mia memoria va benissimo. Di fatto ho fatto fare al computer 12h ININTERROTTE di memtest e il programma no ha segnalato errori! qualcuno ha qualche nuova idea?
edit: mi sono dimenticato le immagini (ma non so come fare) dei bsod (sono riuscito ad avere un'elenco dei bsod fino a 10 giorni fa):
29/10 NTFS_FILE_SYSTEM 0x0..024 - file segnalati: ntoskrnl.exe+6f94c e Ntfs.sys+213d8
30/10 REFERENCE_BY_POINTER 0x0..018 - file segnalati: ntoskrnl.exe+634c
01/11 BAD_POOL_HEADER 0x0..019 - file segnalati: ntoskrnl.exe+19b10b
01/11 BUGCODE_USB_DRIVER 0x0..0fe - file segnalati: USBPORT.SYS+2d14d
01/11 BAD_POOL_HEADER 0x0..019 - file segnalati: ntoskrnl.exe+19b6d3, USBPORT.SYS+25c2 e ndis.sys+8695
02/11 KMODE_EXCEPTION_NOT_HANDLE 0x0..01e - file segnalati: ntoskrnl.exe+5e2ae
06/11 KMODE_EXCEPTION_NOT_HANDLE 0x0..01e - file segnalati: ntoskrnl.exe+a7789
07/11 DRIVER_CORRUPTED_EXPOOL 0x0..0c5 (quello citato sopra) - file segnalati: ntoskrnl.exe+19c90d e nvlddmkm.sys+1992c4
08/11 CACHE_MANAGER 0x0..034 (sempre quello sopra) - file segnalati: ntoskrnl.exe+4de82
08/11 SYSTEM_SERVICE_EXCEPTION 0x0..03b (quelli nuovi) - file segnalati: ntoskrnl.exe+72322
08/11 SYSTEM_SERVICE_EXCEPTION 0x0..03b - file segnalati: ntoskrnl.exe+65ae9 e nvlddmkm.sys+1e4eb7
09/11 SYSTEM_SERVICE_EXCEPTION 0x0..03b - file segnalati: ntoskrnl.exe+65ae9
cosa particolare sempre ed esclusivamente dopo le 18:00! (e accendo il pc alle 15.15, sempre! tutti i giorni!)
note aggiuntive: stranamente, noto sempre una cosa dopo che ho avuto il bosd:
le cose come "kepp me signed" o "remenber me" (per restare collegato a qualcosa senza fare il login tutte le volte) esclusivamente per hotmail si cancella e non si ricorda più di me. Altra cosa strana, premettendo che trovo molto comodi i pulsanti dell'avvio veloce sulla barra, noto che ogni tanto scompare e la devo reinserire.
grazie in anticipio!!
spero che le nuove infiormazioni aiutino a capirci qualcosa!
Ho problemi di riavvio e schermate nere da diverso tempo ma, purtroppo, solo adesso ho avuto modo di fare qualche prova...
Da WinDbg mi viene fuori questo:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\110910-20625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Users\Alve\Desktop\Symbols1
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e86e50
Debug session time: Tue Nov 9 20:11:53.531 2010 (UTC + 1:00)
System Uptime: 0 days 0:05:52.000
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1, {7716feba, 0, ffff, fffff8800651aca0}
***** 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!_KTHREAD ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+70740 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000000007716feba, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffff8800651aca0, Previous KernelApcDisable
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!_KTHREAD ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002c49000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAULTING_IP:
+3564666661343331
00000000`7716feba ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002cb8ca9 to fffff80002cb9740
STACK_TEXT:
fffff880`0651aa68 fffff800`02cb8ca9 : 00000000`00000001 00000000`7716feba 00000000`00000000 00000000`0000ffff : nt+0x70740
fffff880`0651aa70 00000000`00000001 : 00000000`7716feba 00000000`00000000 00000000`0000ffff fffff880`0651aca0 : nt+0x6fca9
fffff880`0651aa78 00000000`7716feba : 00000000`00000000 00000000`0000ffff fffff880`0651aca0 00000000`00000004 : 0x1
fffff880`0651aa80 00000000`00000000 : 00000000`0000ffff fffff880`0651aca0 00000000`00000004 00000000`00000000 : 0x7716feba
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70740
fffff800`02cb9740 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+70740
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Mentre da Bluescreenview questo:
http://img574.imageshack.us/img574/1743/crasha.th.jpg (http://img574.imageshack.us/i/crasha.jpg/)
http://img825.imageshack.us/img825/6210/crash1q.th.jpg (http://img825.imageshack.us/i/crash1q.jpg/)
Se non ricordo male anche con linux dava problemi di riavvio....secondo voi potrebbe essere l'alimentatore?
Jeremy01
13-11-2010, 18:06
ho avuto un riavvio improvviso con questo messaggio successivo:
http://www.pctunerup.com/up/results/_201011/th_20101113190428_1.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101113190428_1.jpg)
http://www.pctunerup.com/up/results/_201011/th_20101113190517_2.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101113190517_2.jpg)
ma non riesco a trovare nessuno dei 2 files indicati per maggiori dettagli, nemmeno facendo una ricerca in tutto il pc.....come posso fare ?
Jeremy01
14-11-2010, 00:27
ecco, posso essere piu completo ora che mi è ricapitato e si è creato il minidump (inoltre questa volta mi è capitato nel medesimo modo in cui è successo ultimamente ed ho postato a pag 39 dal post 766):
questo è l'elenco degli eventi con i tre errori al momento del riavvio mentre ero in game, e mi sembra di aver capito che "critico" è levento del crash
http://www.pctunerup.com/up/results/_201011/th_20101114010151_1.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101114010151_1.jpg)
http://www.pctunerup.com/up/results/_201011/th_20101114010232_2.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101114010232_2.jpg)
poi in orine cronologico questo avviso
http://www.pctunerup.com/up/results/_201011/th_20101114010307_3.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101114010307_3.jpg)
http://www.pctunerup.com/up/results/_201011/th_20101114010331_4.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101114010331_4.jpg)
poi l'ultimo è l'avviso relativo al risultato del controllo errori con la segnalazione dello stesso e il salvataggio nel minidunp
http://www.pctunerup.com/up/results/_201011/th_20101114010413_5.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101114010413_5.jpg)
http://www.pctunerup.com/up/results/_201011/th_20101114010516_6.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101114010516_6.jpg)
ecco il minidump (mi da solo queste cose: non'è incompleto?):
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\111410-24024-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03003000 PsLoadedModuleList = 0xfffff800`03240e50
Debug session time: Sun Nov 14 00:45:37.731 2010 (UTC + 1:00)
System Uptime: 0 days 7:10:34.606
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {24, 2, 0, fffff8000307d34b}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )
Followup: MachineOwner
eccone un altro dello stesso dump con altri symnols:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\111410-24024-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03003000 PsLoadedModuleList = 0xfffff800`03240e50
Debug session time: Sun Nov 14 00:45:37.731 2010 (UTC + 1:00)
System Uptime: 0 days 7:10:34.606
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {24, 2, 0, fffff8000307d34b}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )
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: 0000000000000024, 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: fffff8000307d34b, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ab0e0
0000000000000024
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiTimerWaitTest+22b
fffff800`0307d34b 418b4624 mov eax,dword ptr [r14+24h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: arma2oa.exe
TRAP_FRAME: fffff88003122580 -- (.trap 0xfffff88003122580)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000307d34b rsp=fffff88003122718 rbp=fffffa8007e1f588
r8=fffff880009f4301 r9=0000000000000002 r10=00000000000000f5
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x22b:
fffff800`0307d34b 418b4624 mov eax,dword ptr [r14+24h] ds:5128:00000000`00000024=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003072ca9 to fffff80003073740
STACK_TEXT:
fffff880`03122438 fffff800`03072ca9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03122440 fffff800`03071920 : fffffa80`0818ea10 fffffa80`07e1f588 fffffa80`0818ea10 00000000`0000001b : nt!KiBugCheckDispatch+0x69
fffff880`03122580 fffff800`0307d34b : fffff880`01a730a1 00000000`00000021 00000000`00276b9b 00000000`00276be2 : nt!KiPageFault+0x260
fffff880`03122718 fffff880`03163180 : fffffa80`07e1f580 00000000`00000000 fffffa80`03f96060 00000000`00000102 : nt!KiTimerWaitTest+0x22b
fffff880`03122798 fffffa80`07e1f580 : 00000000`00000000 fffffa80`03f96060 00000000`00000102 00000000`0000000c : 0xfffff880`03163180
fffff880`031227a0 00000000`00000000 : fffffa80`03f96060 00000000`00000102 00000000`0000000c 00000000`00000000 : 0xfffffa80`07e1f580
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTimerWaitTest+22b
fffff800`0307d34b 418b4624 mov eax,dword ptr [r14+24h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiTimerWaitTest+22b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+22b
BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+22b
Followup: MachineOwner
questo invece è quello che mi dice l'utility bluscreen view:
http://www.pctunerup.com/up/results/_201011/th_20101114015732_8.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101114015732_8.jpg)
http://www.pctunerup.com/up/results/_201011/th_20101114015758_7.jpg (http://www.pctunerup.com/up/image.php?src=_201011/20101114015758_7.jpg)
IL_DUCA_91
16-11-2010, 11:47
Raga come risolvo??????non ne posso +!!!
IL_DUCA_91
16-11-2010, 11:49
I file che dovrebbero causare il problema
Jeremy01
19-11-2010, 15:21
sapreste dirmi se questa BSOD è stata provocata dallo stesso motivo di quella riportata da me 2 post fa (post 801-802) ?
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\111910-19344-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: D:\Symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03297e50
Debug session time: Fri Nov 19 16:10:25.002 2010 (UTC + 1:00)
System Uptime: 0 days 3:58:07.266
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8, 2, 1, fffff88002a0895e}
Unable to load image \SystemRoot\system32\DRIVERS\nwifi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nwifi.sys
*** ERROR: Module load completed but symbols could not be loaded for nwifi.sys
Probably caused by : hardware ( nwifi+895e )
Followup: MachineOwner
---------
1: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88002a0895e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800033020e0
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
nwifi+895e
fffff880`02a0895e 68488b97c0 push 0FFFFFFFFC0978B48h
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: EFLC.exe
TRAP_FRAME: fffff88003122440 -- (.trap 0xfffff88003122440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003122570
rdx=0000000001eaafb8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002a0895e rsp=fffff880031225d0 rbp=0000000000000000
r8=0000000000000000 r9=fffffa80065b462e r10=466cedf76ebf7249
r11=fffffa80065b4060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nwifi+0x895e:
fffff880`02a0895e 68488b97c0 push 0FFFFFFFFC0978B48h
Resetting default scope
MISALIGNED_IP:
nwifi+895e
fffff880`02a0895e 68488b97c0 push 0FFFFFFFFC0978B48h
LAST_CONTROL_TRANSFER: from fffff800030c9ca9 to fffff800030ca740
STACK_TEXT:
fffff880`031222f8 fffff800`030c9ca9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03122300 fffff800`030c8920 : fffffa80`06111102 fffffa80`043b42f0 fffffa80`06111102 fffffa80`06111102 : nt!KiBugCheckDispatch+0x69
fffff880`03122440 fffff880`02a0895e : fffffa80`0881e010 00000000`000005ce fffffa80`043b42f0 fffffa80`00000000 : nt!KiPageFault+0x260
fffff880`031225d0 fffffa80`0881e010 : 00000000`000005ce fffffa80`043b42f0 fffffa80`00000000 00000000`00000000 : nwifi+0x895e
fffff880`031225d8 00000000`000005ce : fffffa80`043b42f0 fffffa80`00000000 00000000`00000000 fffff880`04239f79 : 0xfffffa80`0881e010
fffff880`031225e0 fffffa80`043b42f0 : fffffa80`00000000 00000000`00000000 fffff880`04239f79 00000000`c000000d : 0x5ce
fffff880`031225e8 fffffa80`00000000 : 00000000`00000000 fffff880`04239f79 00000000`c000000d fffffa80`0892fa70 : 0xfffffa80`043b42f0
fffff880`031225f0 00000000`00000000 : fffff880`04239f79 00000000`c000000d fffffa80`0892fa70 fffffa80`08000302 : 0xfffffa80`00000000
STACK_COMMAND: kb
FOLLOWUP_IP:
nwifi+895e
fffff880`02a0895e 68488b97c0 push 0FFFFFFFFC0978B48h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nwifi+895e
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nwifi.sys
BUCKET_ID: X64_IP_MISALIGNED_nwifi.sys
Followup: MachineOwner
---------
Vedi qui
http://www.techsupportforum.com/microsoft-support/windows-vista-windows-7-support/363498-bsod-nwifi-sys.html
e qui
http://forums.techarena.in/video-games/1327913.htm
Jammed_Death
20-11-2010, 09:43
ciao, è già il secondo giorno che mi capitano schermate blu, prima 0x000007e mentre stamattina 0x0000019 bad_pool_header
non ho cambiato driver o fatto altro e non riesco a individuare il problema...l'unica cosa strana è che quando capita dopo un po la schermata blu si rovina (appaiono righe bianche su alcune scritte) e dalle casse inizia un fischio...potrebbe essere la scheda audio?
edit: un'altra, 0x000003b system_service_exception
il dump si blocca al 40% e poi inizia a fischiare :(
update: ho testato la ram ed è ok, ho lanciato il test della ciambella per la scheda video (non ricordo il nome) e raggiunti i 60 gradi il pc ha crashato...ho una gtx 460 gs-glh con driver 260.99 ufficiali...non ho mai avuto problemi e non ho mai cambiato nulla. La schermata blu che mi è uscita mentre facevo questo test era 0x000003b win32k.sys, col solito problema che non mi fa salvare il crash dump
Jeremy01
20-11-2010, 11:18
Vedi qui
http://www.techsupportforum.com/microsoft-support/windows-vista-windows-7-support/363498-bsod-nwifi-sys.html
e qui
http://forums.techarena.in/video-games/1327913.htm
a me sembra di capire che la causa della bsod è nwifi.sys e il file che è crashato è EFLC.exe e infatti è crashato mentre giocavo....però non ho capito questo nwifi.sys (driver wifi nativo di windows....così ho trovato in giro) cge centra e perchè mi ha fatto il danno
Jeremy01
20-11-2010, 15:15
questa bsod mi è capitata mentre collegavo i jack degli altoparlanti alla scheda audio:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112010-18158-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03060000 PsLoadedModuleList = 0xfffff800`0329de50
Debug session time: Sat Nov 20 15:58:56.315 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:09.205
Loading Kernel Symbols
.....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004d928f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004d928f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`035a16f0 fffff800`0331aa89 : fffffa80`04d928d0 fffffa80`03d0eb60 fffff8a0`00000005 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`035a1c10 fffff800`031fc667 : fffffa80`04d928d0 fffff800`032755f8 fffffa80`03d0eb60 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`035a1c40 fffff800`03164c45 : fffff800`032d7360 fffffa80`04d7d888 fffffa80`04d7d880 fffffa80`03d0eb60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`035a1c80 fffff800`030dd961 : fffff880`01430e00 fffff800`03164c20 fffffa80`03d0eb60 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`035a1cb0 fffff800`03374c06 : 4d000000`b4ea81c1 fffffa80`03d0eb60 00000000`00000080 fffffa80`03cef040 : nt!ExpWorkerThread+0x111
fffff880`035a1d40 fffff800`030aec26 : fffff880`03363180 fffffa80`03d0eb60 fffff880`0336dfc0 8b4420eb`c148da8b : nt!PspSystemThreadStartup+0x5a
fffff880`035a1d80 00000000`00000000 : fffff880`035a2000 fffff880`0359c000 fffff880`009ce540 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Followup: MachineOwner
---------
:confused: :confused: :confused: :help: :help: :help:
Ciao, ho un portatile HP pavilion 1115el da quasi 2 anni e per ben 3 volte e' stato in assistenza sempre per lo stesso errore uno STOP 0x0000124 che puntualmente si verifica dopo 5 mesi dalla riparazione.....da una settimana si e' ripresentato il problema sempre il solito stop 124.....non so piu' come risolvere.....
Ho letto un po' in giro che dovrei istallare un Hotfix per risolvere questo problema...ma per fare questo dovrei formattare il pc perche' dovrei reistallare il VISTA originale invece io da quando l'ho preso ho istallato il SEVEN e l'HOTFIX per il SEVEN non sono riuscito a trovarlo....
Vi preciso che il problema si verifica anche con VISTA originale..quindi non e' un problema di sistema operativo....
vi posto la stringa del problema
http://img219.imageshack.us/img219/4464/cattura2y.png
JoK3r943
22-11-2010, 18:00
aiutatemi non so piu ke pesci pigliare,
e da un po di mesi ke windows 7 mi crasha causando un blue screan dandomi l'errore sopra indicato il tutto accade quando gioco e visualizzo video vi prego aiutatemi
la mia conf:
p5q deluxe
Q9550 non overcloccato
4gb ddr2 di ram corsair dominator
500 gb di hard disk
HD 4890 1 gb ddr5
corsair 850 watt
windows 7 ultimate 64 bit
:muro:
Beh segui la guida alla prima pagina di questa discussione per estrarre il file dmp
Seguendo la guida cercate almeno di estrarre il file dmp e poi postatelo qui
DevilOfSky
26-11-2010, 20:17
esattamente qualcuno sa cosa possa significare questo errore?
Preferences ReadPrefs
err=2
what=XMLException
where=4
name=Preferences
premetto che non sono espertissimo.
ieri mentre guardavo un video da youtube e oggi mentre scannerizzavo un documento mi è comparsa la fatidica finestra blu con successivo riavvio (pc acquistato a novembre 2009).
ieri, dopo la prima schermata blu sono andato ad aggiornare da win update anche le cose facoltative, ma poco fa di nuovo stesso errore.
mio hardware:
Case:
Thermaltake Element T Middle Tower
Alimentatore:
Chieftec 650Watt
Processore:
Intel® Core™ i5 750 2.66GHz
Ram:
4GB Kingmax Kit 2*2GB DDR3-1600
Scheda Madre:
MSI P55-CD53
Chipset:
Intel P55
Hard Disk:
WD 500GB SATA2 7200rpm
Scheda Grafica:
NVIDIA GeForce GTX275
Memoria Video:
896Mb Gddr3 448bit
Lan:
10/100/1000Tx integrata
Masterizzatore:
Sony NEC DVDRW 24x SATA
Audio:
Codec 8 Canali HDI/O
questa è la finestra che mi compare nel centro sicurezza:
http://img547.imageshack.us/img547/3386/tcopia.png (http://img547.imageshack.us/i/tcopia.png/)
l'analisi dei dmp mi dice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112910-21013-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
Debug session time: Mon Nov 29 13:23:03.575 2010 (UTC + 1:00)
System Uptime: 0 days 0:01:58.011
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002abb866, fffff88003316938, fffff880033161a0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112710-22105-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Sat Nov 27 15:41:33.557 2010 (UTC + 1:00)
System Uptime: 0 days 0:10:58.993
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002aadb7f, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
Followup: MachineOwner
---------
che può essere? la memoria che è andata?
che altri controlli posso fare?
Comincia a cambiare le ram o scollegarne una alla volta
il problema xò è che la schermata blu non si verifica sempre. x esempio ieri sera e oggi pomeriggio ho usato il pc x ore senza alcun problema.
non esiste qualcosa che "testa" i blocchi ram e mi dia un responso certo?
C'è memtest 86, ma per un responso sicuro al 100% meglio staccare fisicamente i vari slot di ram uno alla volta
Zlatan90
30-11-2010, 16:44
Ragazzi anche a me purtroppo è apparsa la schermata blu qualche giorno fà quando avevo ancora XP, siccome è successo 2-3 volte pensai che era qualche problema da virus, perciò pensai bene di formattare e passare a Windows 7, però anche formattando la schermata blu si è ripetuta....vi riporto tra i tag il messaggio di Windows 7 e l'analisi del dmp:
Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.768.3
ID impostazioni locali: 1040
Ulteriori informazioni sul problema:
BCCode: 124
BCP1: 00000000
BCP2: 857D1024
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\112810-28968-01.dmp
C:\Users\Leanza\AppData\Local\Temp\WER-65250-0.sysdata.xml
Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0410
Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt
Ecco l'analisi del dmp:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112810-28968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82843000 PsLoadedModuleList = 0x82982570
Debug session time: Sun Nov 28 23:18:05.234 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:16.984
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 857d1024, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
leggo al penultimo rigo, prabably caused by hardware, ma mi sembra un pò troppo generico.....secondo voi quale può essere il problema??? Grazie mille a tutti!
Inizia a controllare HD e ram, hdtune per l'hd e memtestx86 per la ram, ma per un test più sicuro ti conviene rimnuovere uno slot alla volta
Zlatan90
30-11-2010, 19:59
Inizia a controllare HD e ram, hdtune per l'hd e memtestx86 per la ram, ma per un test più sicuro ti conviene rimnuovere uno slot alla volta
Ciao! ti ringrazio, sto iniziando a testare l'HD....comunque io oltre al fisso ho anche un portatile con Win 7 installato originale, strano ma vero anche sul portatile ha dato lo stesso errore di bluescreen O.o
Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.768.3
ID impostazioni locali: 1040
Ulteriori informazioni sul problema:
BCCode: d1
BCP1: 00000001
BCP2: 00000002
BCP3: 00000008
BCP4: 00000001
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\113010-29203-01.dmp
C:\Users\Beppe\AppData\Local\Temp\WER-77516-0.sysdata.xml
Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410
Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt
Può essere qualcosa di windows che causa questo problema???
Ciao ragazzi,problemino su pc nuovo,PAGE_FAULT_IN_NONPAGED_AREA con sopra NTFS.sys ho paura che sia l'HDD (un maxtor 250Gb),però siccome ho da poco montato 2.1Gb di Corsair XMS3 (DDR3 1333MHz) che hanno passato 6 cicli di memtest 86+ vorrei qualche consiglio.
Grazie.
DevilOfSky
01-12-2010, 13:57
esattamente qualcuno sa cosa possa significare questo errore?
Preferences ReadPrefs
err=2
what=XMLException
where=4
name=Preferences nessuno?
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Mon Dec 6 22:05:03.094 2010 (UTC + 1:00)
System Uptime: 0 days 1:41:44.811
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {1, 2, 8, 1}
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+70740 )
Followup: MachineOwner
mi dà errore di symbols eppure ho selezionato la path giusta...
In ogni caso si riesce a capire qualcosa? ho fatto test con memtest e hdtune e non ci son stati errori
qualcuno mi da una mano?
http://www.pctunerup.com/up/results/_201012/th_20101207225649_bsod.jpg (http://www.pctunerup.com/up/image.php?src=_201012/20101207225649_bsod.jpg)
os windows 7 64
cpu i5-750
mobo msi gd-80
ram gskill ripjaws 2000
ssd intel g2 80
western digital velociraptor 150
western digital caviar black 1 tera
2 gtx 460 1024
dvd rw lg
psu lc-power legion x2 1000watt
le ram sono ok testate da dos con memtest 200%
la cpu anche 30 cicli di linx e varie ore di prime modalita blend
lo sli testato con furmark occt
questa configurazione era stabile su msi gd65 (il resto uguale ) e mai nessun problema
da quando ho cambiato mobo e messo win 64 si sono presentati questi bsod random anche senza fare niente ....
disabilitando il c-state nel bios sembrano essere spariti..........resta cmq il fatto che mi serve il c-state attivo....
Jeremy01
08-12-2010, 13:38
ultimamente ho delle bsod random sul notebook e spulciando nel visualizzatore di eventi ho notato continui errori relativi al protocollo PNRT...sapete di cosa si tratta e come posso risolvere?
http://www.pctunerup.com/up/results/_201012/th_20101208142819_Immagine2.jpg (http://www.pctunerup.com/up/image.php?src=_201012/20101208142819_Immagine2.jpg)
Jeremy01
08-12-2010, 22:19
questo invece sul desktop:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120810-20389-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`03450e50
Debug session time: Wed Dec 8 22:32:49.086 2010 (UTC + 1:00)
System Uptime: 0 days 1:55:46.351
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, 100000040, 8, 100000040}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000100000040, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000100000040, 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:
+3764663965323138
00000001`00000040 ?? ???
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 0000000100000040
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bb0e0
0000000100000040
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: arma2oa.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff8800a8ab248 -- (.exr 0xfffff8800a8ab248)
ExceptionAddress: 0000000100000040
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 0000000100000040
Attempt to execute non-executable address 0000000100000040
TRAP_FRAME: fffff8800a8ab2f0 -- (.trap 0xfffff8800a8ab2f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800811b050
rdx=000000006fa9c000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000100000040 rsp=fffff8800a8ab480 rbp=fffff8a00b0a0db0
r8=0000000000000800 r9=fffffa8008503000 r10=0000000000000001
r11=0000000000008300 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
00000001`00000040 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032bda39 to fffff80003283740
STACK_TEXT:
fffff880`0a8aaa78 fffff800`032bda39 : 00000000`0000001e ffffffff`c0000005 00000001`00000040 00000000`00000008 : nt!KeBugCheckEx
fffff880`0a8aaa80 fffff800`03282d82 : fffff880`0a8ab248 fffff8a0`0b8ad000 fffff880`0a8ab2f0 fffff880`0a8ab5f0 : nt!KiDispatchException+0x1b9
fffff880`0a8ab110 fffff800`032818fa : 00000000`00000008 fffff8a0`0b8ad000 fffff880`0a8ab300 fffff880`04f95f00 : nt!KiExceptionDispatch+0xc2
fffff880`0a8ab2f0 00000001`00000040 : fffff8a0`0b8ad000 fffff880`0a8abb30 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x23a
fffff880`0a8ab480 fffff8a0`0b8ad000 : fffff880`0a8abb30 00000000`00000000 00000000`00000001 00000000`00000000 : 0x1`00000040
fffff880`0a8ab488 fffff880`0a8abb30 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffff8a0`0b8ad000
fffff880`0a8ab490 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`0a8abca0 : 0xfffff880`0a8abb30
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDispatchException+1b9
fffff800`032bda39 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiDispatchException+1b9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KiDispatchException+1b9
BUCKET_ID: X64_0x1E_c0000005_nt!KiDispatchException+1b9
Followup: MachineOwner
---------
Sembrerebbe qualcosa collegato con steam e con le patch :rolleyes:
Jeremy01
09-12-2010, 12:13
Sembrerebbe qualcosa collegato con steam e con le patch :rolleyes:
il gioco è in versione retail (si dice così giusto?) ... dove si capisce il riferimento a steam o alle patch (che invece sono installate)?
(...mi ha crashato proprio in una bella sessione in multiplayer :muro: )
Jeremy01
09-12-2010, 14:01
eccone un altra (non so piu cosa pensare):
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120910-17706-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`03489e50
Debug session time: Thu Dec 9 14:06:55.126 2010 (UTC + 1:00)
System Uptime: 0 days 1:12:46.016
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8, 2, 1, fffff88002e5a95e}
Unable to load image \SystemRoot\system32\DRIVERS\netr7364.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr7364.sys
*** ERROR: Module load completed but symbols could not be loaded for netr7364.sys
Probably caused by : hardware ( nwifi!Pt6RepackRecvNBL+2fa )
Followup: MachineOwner
---------
1: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88002e5a95e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f40e0
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
nwifi!Pt6RepackRecvNBL+2fa
fffff880`02e5a95e 68488b97c0 push 0FFFFFFFFC0978B48h
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: LP2DX9.exe
TRAP_FRAME: fffff88003322440 -- (.trap 0xfffff88003322440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003322570
rdx=0000000003ed5628 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002e5a95e rsp=fffff880033225d0 rbp=0000000000000000
r8=0000000000000000 r9=fffffa8004542ad9 r10=f5bc2f32e757d9b7
r11=fffffa80045429f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nwifi!Pt6RepackRecvNBL+0x2fa:
fffff880`02e5a95e 68488b97c0 push 0FFFFFFFFC0978B48h
Resetting default scope
MISALIGNED_IP:
nwifi!Pt6RepackRecvNBL+2fa
fffff880`02e5a95e 68488b97c0 push 0FFFFFFFFC0978B48h
LAST_CONTROL_TRANSFER: from fffff800032bbca9 to fffff800032bc740
STACK_TEXT:
fffff880`033222f8 fffff800`032bbca9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03322300 fffff800`032ba920 : 00000000`00000000 fffffa80`04356b10 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03322440 fffff880`02e5a95e : fffffa80`0885d010 00000000`000000e9 fffffa80`04356b10 fffffa80`00000000 : nt!KiPageFault+0x260
fffff880`033225d0 fffff880`02e5b6c8 : 00000000`00000000 00000000`00000004 fffffa80`07c101b0 fffffa80`0885d010 : nwifi!Pt6RepackRecvNBL+0x2fa
fffff880`033226d0 fffff880`018489e9 : fffffa80`083171a0 00000000`00000000 00000000`00000001 fffffa80`07c101b0 : nwifi!Pt6Receive+0x170
fffff880`03322730 fffff880`01848980 : fffffa80`0837f328 fffff880`01c300c7 fffff880`01c31340 fffff880`055b1cab : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`03322770 fffff880`01c2c9c0 : fffff880`01c33110 00000000`00000000 00000000`00000001 fffffa80`0837fd78 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`033227b0 fffff880`018602b7 : fffffa80`07d351a0 fffffa80`0823d650 fffffa80`0823d650 00000000`00000001 : vwififlt!FilterReceiveNetBufferLists+0x158
fffff880`03322810 fffff880`0427118f : fffffa80`0822f8c0 00000000`00000000 fffffa80`0841802e 00000000`00000000 : ndis! ?? ::FNODOBFM::`string'+0xccef
fffff880`03322860 fffffa80`0822f8c0 : 00000000`00000000 fffffa80`0841802e 00000000`00000000 fffffa80`00000002 : netr7364+0x518f
fffff880`03322868 00000000`00000000 : fffffa80`0841802e 00000000`00000000 fffffa80`00000002 fffffa80`08202878 : 0xfffffa80`0822f8c0
STACK_COMMAND: kb
FOLLOWUP_IP:
nwifi!Pt6RepackRecvNBL+2fa
fffff880`02e5a95e 68488b97c0 push 0FFFFFFFFC0978B48h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nwifi!Pt6RepackRecvNBL+2fa
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nwifi.sys
BUCKET_ID: X64_IP_MISALIGNED_nwifi.sys
Followup: MachineOwner
---------
Jeremy01
09-12-2010, 16:04
sto impazzendo...un altra bsod....e sempre e solo mentre gioco
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120910-19468-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03201000 PsLoadedModuleList = 0xfffff800`0343ee50
Debug session time: Thu Dec 9 16:15:21.449 2010 (UTC + 1:00)
System Uptime: 0 days 2:06:56.713
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8005ee1028, be000000, 800400}
Probably caused by : hardware
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005ee1028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: LP2DX9.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff800`04b92a98 fffff800`037ef903 : 00000000`00000124 00000000`00000000 fffffa80`05ee1028 00000000`be000000 : nt!KeBugCheckEx
fffff800`04b92aa0 fffff800`03387593 : 00000000`00000001 fffffa80`058fbcb0 00000000`00000000 fffffa80`058fbd00 : hal!HalBugCheckSystem+0x1e3
fffff800`04b92ae0 fffff800`037ef5c8 : 00000000`00000728 fffffa80`058fbcb0 fffff800`04b92e70 fffff800`04b92e00 : nt!WheaReportHwError+0x263
fffff800`04b92b40 fffff800`037eef1a : fffffa80`058fbcb0 fffff800`04b92e70 fffffa80`058fbcb0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`04b92c90 fffff800`037eedd5 : 00000000`00000004 00000000`00000001 fffff800`04b92ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`04b92cd0 fffff800`037e2e88 : 00000000`058cdcdc 00000000`ffffffff 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`04b92d00 fffff800`0326ffec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`04b92d30 fffff800`0326fe53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`04b92e70 00000000`004481e5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0018bcbc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4481e5
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
---------
beh almeno tu lo sai che in game io ho bsod con il pc in idle ed esuper rock solid linx e prime95-....
Jeremy01
09-12-2010, 23:00
una curiosità: è piu affidabile la lettura del minidump tramite "windbg" oppure "bluscreenview"? ....non'è che possono dare informazioni contrastanti quanto alla causa della bsod?
basta confrontare i risultati ;) a me sembra che coincidano sempre
http://forums.nvidia.com/index.php?showtopic=177267
cambiamento
12-12-2010, 12:07
Salve a tutti vi posto le analisi dei miei minidump.
Quasi tutti fanno riferimento a "memory corrupted..." e AVG :|
Deduco che è un problema di ram e software?
Le blu scree le fa principalmente in avvio, solo poche volta durante le attività su win.
Tutti i miei drivers sono aggiornati, come win7.
Grazie dell'aiuto :)
Il Mio PC in firma
1)
WARNING: Inaccessible path: 'C:\Symbols'
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120510-19250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'C:\Symbols'
Symbol search path is: C:\Symbols;SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`0309be50
Debug session time: Sun Dec 5 15:34:50.328 2010 (UTC + 1:00)
System Uptime: 0 days 0:06:12.405
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {48, 2, 1, fffff80002f80b1f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
Followup: MachineOwner
2)
WARNING: Inaccessible path: 'C:\Symbols'
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120610-19874-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'C:\Symbols'
Symbol search path is: C:\Symbols;SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`03096e50
Debug session time: Mon Dec 6 09:53:29.367 2010 (UTC + 1:00)
System Uptime: 0 days 0:02:56.818
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa99842e0918, 2, 1, fffff80002eea3a4}
Probably caused by : win32k.sys ( win32k!NtGdiEnumFonts+f1 )
Followup: MachineOwner
3)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120910-19094-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Thu Dec 9 17:08:59.374 2010 (UTC + 1:00)
System Uptime: 0 days 0:01:28.826
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa80f557aed8, 2, 1, fffff80002ee1cd8}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+6a8 )
Followup: MachineOwner
---------
4)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120910-20545-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Thu Dec 9 17:06:24.516 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:09.968
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff68000012780, c570000241ae4867, 426d45d40763a4fe}
Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
Probably caused by : avgldx64.sys ( avgldx64+1779a )
Followup: MachineOwner
---------
5)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121010-22479-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030a5e50
Debug session time: Fri Dec 10 17:55:17.342 2010 (UTC + 1:00)
System Uptime: 0 days 0:05:40.793
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {80000003, fffff80002eea70b, fffff8800a9e20e0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
6)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121110-24102-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`0304de50
Debug session time: Sat Dec 11 11:59:00.245 2010 (UTC + 1:00)
System Uptime: 0 days 0:07:08.697
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa8c600a8028, 2, 0, fffff80002eff4d8}
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+25 )
Followup: MachineOwner
---------
7)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121210-23509-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`0309fe50
Debug session time: Sun Dec 12 11:59:03.421 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:10.873
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800402cb69, fffff880009a8848, fffff880009a80b0}
Probably caused by : avgldx64.sys ( avgldx64+2cb69 )
Followup: MachineOwner
---------
8)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121210-24382-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`0308be50
Debug session time: Sun Dec 12 12:01:18.231 2010 (UTC + 1:00)
System Uptime: 0 days 0:01:11.683
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff68000225308, 0, 0, fffff80002fc4ef7}
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )
Followup: MachineOwner
---------
qualcuno mi da una mano?
http://www.pctunerup.com/up/results/_201012/th_20101207225649_bsod.jpg (http://www.pctunerup.com/up/image.php?src=_201012/20101207225649_bsod.jpg)
os windows 7 64
cpu i5-750
mobo msi gd-80
ram gskill ripjaws 2000
ssd intel g2 80
western digital velociraptor 150
western digital caviar black 1 tera
2 gtx 460 1024
dvd rw lg
psu lc-power legion x2 1000watt
le ram sono ok testate da dos con memtest 200%
la cpu anche 30 cicli di linx e varie ore di prime modalita blend
lo sli testato con furmark occt
questa configurazione era stabile su msi gd65 (il resto uguale ) e mai nessun problema
da quando ho cambiato mobo e messo win 64 si sono presentati questi bsod random anche senza fare niente ....
disabilitando il c-state nel bios sembrano essere spariti..........resta cmq il fatto che mi serve il c-state attivo....
ultimamente ho delle bsod random sul notebook e spulciando nel visualizzatore di eventi ho notato continui errori relativi al protocollo PNRT...sapete di cosa si tratta e come posso risolvere?
http://www.pctunerup.com/up/results/_201012/th_20101208142819_Immagine2.jpg (http://www.pctunerup.com/up/image.php?src=_201012/20101208142819_Immagine2.jpg)
a titolo informativo con 1 step in piu di voltaggio vtt i bsod sono scomparsi...
Riposto qui:
-
Salve, per analizzare il problema che sto avendo, cerchero' di essere il piu' dettagliato possibile.
Come avrete capito il sistema (W7 Ultimate x64) va in crash con BSOD presentando l'errore di cui sopra. Non ci sono altri dettagli, se non lo STOP: 0x0000000A abbastanza generico.
La cosa mi sta creando problemi nell'identificazione del malfunzionamento in quanto alcune caratteristiche indicherebbero un problema software, altre hardware.
Il problema si presenta solo ed esclusivamente dopo l'accesso (login) in Windows, ovvero il caricamento fino alla schermata di login avviene sempre senza interruzioni.
Dopo il login il sistema per il 90% delle volte si blocca in pochi secondi, per il rimanente 10% mi lascia lavorare per alcuni minuti prima di presentarsi.
La schermata blu appare indifferentemente sia in modalita' normale, che in "safe mode", anche se appare che in safe mode riesca a lavorare qualche secondo piu' (probabilmente per meno carico su ram/processore).
Ho gia' rimosso tutti i drivers sospetti, e scollegato tutte le periferiche (oltre ovviamente alla tastiera, mouse, scheda video, quest'ultima l'ho pure sostituita per prova), ho disabilitato inoltre tutti i servizi, senza apparenti risultati.
Il problema si e' presentato all'improvviso, cioe' senza che avessi implementato alcuna modifica hardware o software (nuove installazioni, ecc.).
All'inizio ho pensato che fosse un banco di RAM, ho cosi' provato il sistema con un banco alla volta (2GB), il problema rimane. Ho verificato la RAM con memtest86+ e tutti i banchi risultano integri.
Sono quindi passato all'HD, l'ho verificato e pure questo risulta perfettamente integro. Ho provato ad utilizzare una diversa porta SATA, anche qui senza risultati.
Ho verificato nel BIOS che qualcosa non fosse andato fuori posto, e non c'e' niente che non vada, il processore (i7 920) attualmente e' alla velocita' stock, con i voltaggi corretti (che comunque non avevo cambiato), e cosi' pure le RAM (voltaggi e timings). Ho comunque aggiornato il BIOS all'ultima versione, stesso problema.
I voltaggi forniti dall'alimentatore (Corsair HX850) sembrano corretti, anche se di questo non ne ho la certezza assoluta visto che sono quelli indicati dalla mobo, e non li giudico affidabili specialmente quando il PC e' sotto stress.
Il fatto che il problema si presenti solo dopo il login, mi faceva pensare ad un problema sw, ma siccome il problema non avviene sempre nello stesso momento (anzi, rarissimamente non c'e'), escludo che possa trattarsi di un driver o libreria corrotti (li caricherebbe sempre). Ma passando a quelli hw, la ram risulta integra e cosi' pure l'HD... pero' vi chiedo: vi e' mai capitato che un memtest dia responso positivo, quando la ram e' invece da buttare (ma poi 3 banchi di ram che si rompono insieme?); idem per l'hd: potrebbe passare il chdsk pur essendo danneggiato?
Naturalmente vorrei evitare di reinstallare Windows da zero (dovrei reinstallare tutte le applicazioni che uso per lavoro), possibilita' che relego come ultima spiaggia (tra l'altro sarebbe la mia prima reinstallazione di un OS causa crash, mai fatta in 20 anni con nessun OS... ma c'e' sempre una prima volta).
Per evitare di non lasciare nulla intentato (e per chiarire quanto sia importante non dover reinstallare) ho acquistato nuovi banchi di ram, e addirittura una nuova CPU, che dovrebbero arrivarmi (saranno soldi sprecati se il problema dovesse essere altrove...), ma intanto mi informo nel caso non risolvessi il problema (fasciarsi la testa prima...).
Secondo voi c'e' qualcosa che ho trascurato? Mi converrebbe montare un nuovo alimentatore per provare intanto? Operazione non proprio semplicissima, visto che dovrei smontarlo dal mio PC di backup (questo con cui sto scrivendo).
Alla fine resterebbe la mobo (RampageII Extreme) ...ma non si bloccherebbe pure durante il caricamento? Almeno occasionalmente...
Consigli? Grazie.
(Il minidump nel mio caso ha poca valenza, riferendosi genericamente al kernel, comunque):
On Sun 12/12/2010 1.25.57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\121210-117967-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A49A71, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Jeremy01
13-12-2010, 11:01
a titolo informativo con 1 step in piu di voltaggio vtt i bsod sono scomparsi...
ma l'avevi testato precedentemente l'overclock?
cambiamento
14-12-2010, 12:43
Test su Hd completo con esito positivo senza errori
Test su 8GB di ram con memtest fatto girare su cd con boot in avvio con esito positivo senza errori
Bios loaddato in default e fatta la modifica sul riavvio delle blu screen.
Sull'ultima schermata il codice di errorre era quello generico
STOP 0x0000001A: Memory_managment
Sulle info mi descriveva un possibile problema dovuto ai drivers della stampante HP :|
Per sicurezza ho rimosso tutto e provo a vedere come va.
Sinceramente però mi sembra strano...
Qualcuno sa aiutarmi?
Riposto le 8 analisi dei minudump :)
Salve a tutti vi posto le analisi dei miei minidump.
Quasi tutti fanno riferimento a "memory corrupted..." e AVG :|
Deduco che è un problema di ram e software?
Le blu scree le fa principalmente in avvio, solo poche volta durante le attività su win.
Tutti i miei drivers sono aggiornati, come win7.
Grazie dell'aiuto :)
Il Mio PC in firma
1)
WARNING: Inaccessible path: 'C:\Symbols'
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120510-19250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'C:\Symbols'
Symbol search path is: C:\Symbols;SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`0309be50
Debug session time: Sun Dec 5 15:34:50.328 2010 (UTC + 1:00)
System Uptime: 0 days 0:06:12.405
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {48, 2, 1, fffff80002f80b1f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
Followup: MachineOwner
2)
WARNING: Inaccessible path: 'C:\Symbols'
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120610-19874-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'C:\Symbols'
Symbol search path is: C:\Symbols;SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`03096e50
Debug session time: Mon Dec 6 09:53:29.367 2010 (UTC + 1:00)
System Uptime: 0 days 0:02:56.818
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa99842e0918, 2, 1, fffff80002eea3a4}
Probably caused by : win32k.sys ( win32k!NtGdiEnumFonts+f1 )
Followup: MachineOwner
3)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120910-19094-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Thu Dec 9 17:08:59.374 2010 (UTC + 1:00)
System Uptime: 0 days 0:01:28.826
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa80f557aed8, 2, 1, fffff80002ee1cd8}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+6a8 )
Followup: MachineOwner
---------
4)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\120910-20545-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Thu Dec 9 17:06:24.516 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:09.968
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff68000012780, c570000241ae4867, 426d45d40763a4fe}
Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
Probably caused by : avgldx64.sys ( avgldx64+1779a )
Followup: MachineOwner
---------
5)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121010-22479-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030a5e50
Debug session time: Fri Dec 10 17:55:17.342 2010 (UTC + 1:00)
System Uptime: 0 days 0:05:40.793
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {80000003, fffff80002eea70b, fffff8800a9e20e0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
6)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121110-24102-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`0304de50
Debug session time: Sat Dec 11 11:59:00.245 2010 (UTC + 1:00)
System Uptime: 0 days 0:07:08.697
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa8c600a8028, 2, 0, fffff80002eff4d8}
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+25 )
Followup: MachineOwner
---------
7)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121210-23509-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`0309fe50
Debug session time: Sun Dec 12 11:59:03.421 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:10.873
Loading Kernel Symbols
...............................................................
.......................
Loading User Symbols
Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800402cb69, fffff880009a8848, fffff880009a80b0}
Probably caused by : avgldx64.sys ( avgldx64+2cb69 )
Followup: MachineOwner
---------
8)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121210-24382-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`0308be50
Debug session time: Sun Dec 12 12:01:18.231 2010 (UTC + 1:00)
System Uptime: 0 days 0:01:11.683
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff68000225308, 0, 0, fffff80002fc4ef7}
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )
Followup: MachineOwner
---------
Inizia testando le ram, scollegane una alla volta e vedi come va il pc, poi elimina definitivamente quel cesso di AVG :asd:
Per l'ultimo errore PCIIDEX.SYS vedi qui
http://www.velocityreviews.com/forums/t634610-pciidex-sys-bsod.html
cambiamento
14-12-2010, 14:14
Inizia testando le ram, scollegane una alla volta e vedi come va il pc, poi elimina definitivamente quel cesso di AVG :asd:
Per l'ultimo errore PCIIDEX.SYS vedi qui
http://www.velocityreviews.com/forums/t634610-pciidex-sys-bsod.html
In effetti AVG mi aveva segnalato errori... Vedrò di metterne uno diverso allora :)
Ho letto sul link ma non è che abbia capito esattamente cosa fare :(
Grazie!
Per iniziare dovresti scollegare tutti i dispositivi esterni usb ecc. che hai eventualmente collegati al pc, poi prova ad attacarne una alla volta per vedere se una in particolare ti possa procurare le bsod.
Poi scollega i banchi di ram uno alla volta e vedi come va il pc
cambiamento
14-12-2010, 22:09
Per iniziare dovresti scollegare tutti i dispositivi esterni usb ecc. che hai eventualmente collegati al pc, poi prova ad attacarne una alla volta per vedere se una in particolare ti possa procurare le bsod.
Poi scollega i banchi di ram uno alla volta e vedi come va il pc
Il problema è che la cosa avviene in random, cioè non ho alcun riferimento per dire quando o se accade in un momento particolare.
Anche perchè non è una cosa molto frequente, ad esempio oggi dopo aver cancellato i driver della stampante e avg non ne ho più avute :| Però magari domani mi alzo e di nuovo schermata blu.
Inizio con lo scollegare quelle che non uso molto. Però forse prima dovrei vedere se ricapita una nuova schermata... che dite?
cambiamento
19-12-2010, 11:34
4 banchi di ram fungono tutti e 4.
Non so se combinazioni o spostamente possano risolvere il problema :(
Ho tolto AVG e disintallato il driver della stampante.
Ho aggiornato win.
Ho ritestato l'hd.
Niente continuano a comparire le generiche sulla memoria...
Si può fare altro oltre memtest?
Grazie :)
cambiamento
19-12-2010, 15:28
un altro 0X00000050 che fa riferimento ad un danno sulla ram :|
Dopo aver resettato non si avviava e il monitor lampeggiava...
:(
Misà che è la ram, anche se devo ammettere che non ci sto capendo più nulla, ogni volta è una blue screen diversa :|
cambiamento
20-12-2010, 19:17
Ho fatto memtes con procedura tramite cd in fase di boot.
Ho sperato i banchi di memoria in modo tale da testarli separatamente.
I test hanno dato tutti esito posivo con 0 errori rilevati...
A questo punto non so proprio dove sbattere la testa... Provo a formattare?
Secondo me il maggior indiziato rimane la ram, i banchi sono uguali o compatibili? A volte può esesre anche un banale contatto tra le memorie e la superficie degli slot, prova a pulirli o anche al limite a cambiare la disposizione delle ram
cambiamento
21-12-2010, 15:02
Secondo me il maggior indiziato rimane la ram, i banchi sono uguali o compatibili? A volte può esesre anche un banale contatto tra le memorie e la superficie degli slot, prova a pulirli o anche al limite a cambiare la disposizione delle ram
sono tutti banchi uguali e in teoria compatibili tra loro (tutte Corsair).
Stesso modello.
Ho provato a scambiarle di posto ieri sera, oggi vedrò di testarlo un po'. La cosa strana è che le schermate avvengono sempre all'avvio, cioè al primo avvio della giornata, dopo sembra che tutto si stabilizzi.
Come pulisco le slot e la ram? C'è un metodo particolare?
Stesera al primo riavvio vedrò se il cambio è stato utile in qualocosa...
Grazie per l'aiuto :)
Come pulisco le slot e la ram? C'è un metodo particolare?
Alcuni puliscono il connettore con una semplice gomma da cancellare :D oppure con aspirapolvere e un pennellino sintetico appena umido di ammoniaca
Jeremy01
22-12-2010, 10:46
sapete come mai i files nella cartella minidump spariscono e non vengono conservati nel tempo?
cambiamento
22-12-2010, 11:01
Alcuni puliscono il connettore con una semplice gomma da cancellare :D oppure con aspirapolvere e un pennellino sintetico appena umido di ammoniaca
Grazie mille. Ho avuto poco tempo per testare il pc ma devo dire che sui 3 avvii fatti in 3 momenti diversi non c'è stato problema.
Facendo mente locale ho anche ricordato che il softwerino dell'asus (express gate) un giorno si è impallato in avvio (non so se lo conosci, ma si avvia come fosse da boot e compare una schermata con alcuni applicativi che si chiude in 10 sec).
Se non ricordo male da dopo quell'impallamento sono cominciate le schermate blu e il programma ha smesso di fungere. Così oltre a scambiare i banchi ho disintallato e reinstallato il programma che ora riparte senza errori.
Essendo un prog della scheda madre magari può essere stato quello?
Mi auguro che i due inteventi (ram e asus express gate) siano risolutivi. :rolleyes:
Grazie ancora dell'aiuto
cambiamento
22-12-2010, 11:05
sapete come mai i files nella cartella minidump spariscono e non vengono conservati nel tempo?
Alcuni software come TUNEUP o CCleaner cancellano i minidump (se non ricordo male nel mio caso fu GAMEBOOSTER che serve ad ottimizzare il sistema per gamer e nelle varie applicazioni, come pulizia del disco, c'è presente anche la scelta di cancellare i minidump.
In ogni caso, software di questo tipo, dovrebbero avvisare e non dare in automatico la cancellazione di file temporanei che riguardano le informazioni di sistema.
:)
cambiamento
22-12-2010, 15:45
Altra schermata :(
STOP 0x000000d1
Address dxgmms1.sys
Non sono riuscito a capire però cos'è stavolta...
Altra schermata :(
STOP 0x000000d1
Address dxgmms1.sys
Non sono riuscito a capire però cos'è stavolta...
Prova ad aggiornare i driver video
Mi iscrivo giacché è un paio di giorni che mi va in bsod il pc QUANDO NON CI SONO DAVANTI
3 volte è successo 3 volte quando non ci sono stato davanti per più di 1 ora almeno, in caso di utilizzo non si verifica, quantomeno ieri dopo la bsod son stato più o meno costantemente davanti al pc per 5/6 ore (tra forum giochi serie tv) e non si son verificate.
Ho formattato pensando che magari fosse stato un mio errore durante l'installazione di qualche driver, di qualche aggiornamento, non lo so. Niente, questa sera il bsod s'è verificato.
Purtroppo non riesco ad installare il programma di debug di windows (dice che non riesce a trovare il file.. dal suo download manager.).
In caso allego il minidump, visto che me lo sono salvato.
L'unica differenza tra PRIMA che mi venissero fuori le BSOD e dopo è l'aggiornamento ai driver della VGA dai 10.10e ai 10.12.
Allego il minidump : http://www.mediafire.com/?7a212828sebwu9b
Il problema è con il driver Atikmdag.sys, prova a tornare ai vecchi driver
Il problema è con il driver Atikmdag.sys, prova a tornare ai vecchi driver
Magari provo prima a passare ai 12.12a visto che sono usciti.. grazie mille per il consulto!
cambiamento
23-12-2010, 10:47
Prova ad aggiornare i driver video
provo e testo il pc
riprovo anche test su ram
provo e testo il pc
riprovo anche test su ram
Per il test ram puoi scollegare un banco alla volta, così il risultato è più attendibile
Salve ragazzi sono nuovo (dopo corro a presentarmi :)):
ho un problema, mi sono appena fatto il pc nuovo
1 x ATI HD6870 ASUS 1GB GDDR5 2DI2S/1GD5 2xDVI/2xDP/HDMI
1 x LC-POWER Green Power LC6560GP3 V2.3 560W
1 x ASROCK AM3 880G Extreme3
1 x DDR3 1600Mhz PC12800 4GB Exceleram Black PCB CL6-9-8-24 (2x2GB)
1 x AMD Phenom II X4 965 3.4Ghz 4x512KB Black Edition
1 x SAMSUNG 320GB HD322GJ 7200rpm 16MB Spinpoint F4
Purtroppo sto avendo problemi di BSOD... la cosa strana che avvengono praticamente sempre quando non sono al pc. Anyway al riavvio Win7 Ultimate x64 questo è il risultato:
Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.256.1
ID impostazioni locali: 1040
Ulteriori informazioni sul problema:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880048B3817
BCP3: FFFFF8800714F8B0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\122410-14586-01.dmp
C:\Users\Giuseppe\AppData\Local\Temp\WER-29608-0.sysdata.xml
Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410
Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt
Le ram erano inizialmente settate a 1333mhz e mi dava bsod, ora le ho settate a 1600mhz (tramite la funzione del bios con il voltaggio in "auto") e non cambia la situazione. Provo a settare manualmente a 1.65v le ram?
Grazie in anticipo.
cambiamento
24-12-2010, 11:16
Per il test ram puoi scollegare un banco alla volta, così il risultato è più attendibile
Grazie provo così allora!
Salve ragazzi sono nuovo (dopo corro a presentarmi :)):
ho un problema, mi sono appena fatto il pc nuovo
Purtroppo sto avendo problemi di BSOD... la cosa strana che avvengono praticamente sempre quando non sono al pc. Anyway al riavvio Win7 Ultimate x64 questo è il risultato:
Le ram erano inizialmente settate a 1333mhz e mi dava bsod, ora le ho settate a 1600mhz (tramite la funzione del bios con il voltaggio in "auto") e non cambia la situazione. Provo a settare manualmente a 1.65v le ram?
Grazie in anticipo.
Se hai i 10.12 di driver video prova a mettere i 10.12a o i 10.10e.
A me erano i driver video a causare quel problema ;)
jacoscar
24-12-2010, 18:42
Io ricevo l'avviso che i symbols sono sbagliati.....
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\122410-36348-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: E:\symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e50
Debug session time: Fri Dec 24 00:56:50.056 2010 (UTC + 1:00)
System Uptime: 0 days 13:18:25.945
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff800031e8477}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Ho windows 7 home premium 64 bit e ho provato ad installare entrambi questi
-Windows 7 RTM x64 retail symbols, all languages (File size: 286 MB)
-Windows 7 RTM x64 checked symbols, all languages (File size: 260 MB)
Se hai i 10.12 di driver video prova a mettere i 10.12a o i 10.10e.
A me erano i driver video a causare quel problema ;)
ho scaricato ed installato i 10.12a e ora nel tool catalyst mi ristulta 10.11 -.-
Ho sbagliato qualcosa? comunque sì, avevo i 10.12
Io ricevo l'avviso che i symbols sono sbagliati.....
Usa BlueScreenView e risolvi il problema ;)
jacoscar
25-12-2010, 17:15
Usa BlueScreenView e risolvi il problema ;)
Cioè quel programmino da 2mb fa le stesse cose che non riesco a fare dopo aver scaricato centinaia di MB dalla Microsoft?
Comunque...
http://dl.dropbox.com/u/16550043/bluescreenview.txt
Cioè quel programmino da 2mb fa le stesse cose che non riesco a fare dopo aver scaricato centinaia di MB dalla Microsoft?
Comunque...
http://dl.dropbox.com/u/16550043/bluescreenview.txt
Prova a dare un'occhiata qui
http://support.microsoft.com/search/default.aspx?query=hal.dll&mode=r&catalog=LCID%3D1040
jacoscar
25-12-2010, 22:20
Prova a dare un'occhiata qui
http://support.microsoft.com/search/default.aspx?query=hal.dll&mode=r&catalog=LCID%3D1040
le schermate blu mi appaiono solo con utorrent attivo comunque
le schermate blu mi appaiono solo con utorrent attivo comunque
Allora chiedi sul forum utorrent, penso sia un problema comune, oppure qui
http://img687.imageshack.us/img687/1207/bsodz.th.png (http://img687.imageshack.us/i/bsodz.png/)
Ho un i7@ 2,66 Ghz 920 D0 @ 3,33 Ghz. Testato più volte con prima95 e stabile da mesi. Non credo sia questo il problema.
Molte volte crasha adobe flash e l'ultima volta che ho riscontrato un BSDOD, qui sul forum mi avete detto che i dischi fissi hanno quale problema.
Ho un Seagate spinpoint 1 Tb e un Buffalo 500 Gb potatile esterno USB.
Spero si riesca a capire la causa. In allegato trovate il report da estrarre :)
Tre problemi:
pshed.dll
http://support.microsoft.com/search/default.aspx?query=pshed.dll&mode=r&catalog=LCID%3D1040
hal.dll
http://support.microsoft.com/search/default.aspx?mode=r&query=hal.dll&spid=14019&catalog=LCID%3D1040&1040comm=1&1040mt=1&ast=25&ast=28&ast=30&ast=31&res=10
ntoskrnl.exe
http://support.microsoft.com/search/default.aspx?mode=r&qid=4834&query=ntoskrnl.exe&spid=14019&catalog=LCID%3D1040&1040comm=1&1040mt=1&ast=25&ast=28&ast=30&ast=31&res=10
Per l'ultimo errore dovresti iniziare testando la ram o meglio scolelgnadone un banco alla vota
Tre problemi:
pshed.dll
http://support.microsoft.com/search/default.aspx?query=pshed.dll&mode=r&catalog=LCID%3D1040
hal.dll
http://support.microsoft.com/search/default.aspx?mode=r&query=hal.dll&spid=14019&catalog=LCID%3D1040&1040comm=1&1040mt=1&ast=25&ast=28&ast=30&ast=31&res=10
ntoskrnl.exe
http://support.microsoft.com/search/default.aspx?mode=r&qid=4834&query=ntoskrnl.exe&spid=14019&catalog=LCID%3D1040&1040comm=1&1040mt=1&ast=25&ast=28&ast=30&ast=31&res=10
Per l'ultimo errore dovresti iniziare testando la ram o meglio scolelgnadone un banco alla vota
quindi è dovuto praticamente alla RAM?
Forse ma potrebbe dipendere anche da qualcos'altro, intanto fai il test della ram
Prima di poter testare la RAM è comparso un secondo BSOD:
http://img341.imageshack.us/img341/1959/immaginedg.th.png (http://img341.imageshack.us/i/immaginedg.png/)
Altri 2 BSOD, Non mi erano mai capitati così ripetutamente. Potrebbe essere la temp troppo alta
GPU: 91°
CPU 74°
Core: 81° - 79° - 84° - 80°
http://img830.imageshack.us/img830/3289/immaginefl.th.png (http://img830.imageshack.us/i/immaginefl.png/)
Non so se le bsod siano diretta conseguenza delle temperature, ma queste sono decisamente troppo alte, apri il pc e dai una bella ripulita per iniziare.
http://support.microsoft.com/search/default.aspx?mode=r&query=pshed.dll+bsod&spid=14019&catalog=LCID%3D1040&1040comm=1&1040mt=1&ast=25&ast=28&ast=30&ast=31&res=10
Ho dato una ripulita ieri e oggi. Mi sono accorto ora che ieri durante la pulizia avevo montato le ventole al contrario.
Ora sono a posto: soffiano aria verso il retro del case.
Come temp con prime95 in full arrivo a 70°, ma non credo siano causati dalle temp.
PS: all'avvio il BIOS segnalava un overclock fallito, come mai visto che dai test di prime95 risulta tutto ok.
bluddino
27-12-2010, 19:32
La mia cartella minidump contiene il bel paio di files:
Mini122310-01.dmp
Mini122410-01.dmp
Mini122410-02.dmp
Mini122410-03.dmp
Mini122410-04.dmp
Mini122510-01.dmp
Mini122610-01.dmp
Mini122610-02.dmp
Mini122610-03.dmp
Mini122610-04.dmp
Mini122610-05.dmp
Mini122610-06.dmp
Mini122610-07.dmp
Mini122610-08.dmp
Mini122610-09.dmp
Mini122710-01.dmp
Mini122710-02.dmp
Mini122710-03.dmp
Mini122710-04.dmp
Mini122710-05.dmp
Mini122710-06.dmp
Mini122710-07.dmp
Dovrei postarle tutte una ad una? Ho notato che gli errori sono sempre acpi.sys oppure upzwws.sys ,
questa è l'ultima bsod che mi è arrivata:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini122710-07.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18488.x86fre.vistasp1_gdr.100608-0458
Machine Name:
Kernel base = 0x81e03000 PsLoadedModuleList = 0x81f1ac70
Debug session time: Mon Dec 27 20:18:32.603 2010 (UTC + 1:00)
System Uptime: 0 days 2:14:40.460
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {af9ca000, 2, 0, 82a10ccb}
Unable to load image \SystemRoot\System32\Drivers\upzwws.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for upzwws.sys
*** ERROR: Module load completed but symbols could not be loaded for upzwws.sys
Probably caused by : upzwws.sys ( upzwws+4ccb )
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: af9ca000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 82a10ccb, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 81f3a868
Unable to read MiSystemVaType memory at 81f1a420
af9ca000
CURRENT_IRQL: 2
FAULTING_IP:
upzwws+4ccb
82a10ccb ?? ???
CUSTOMER_CRASH_COUNT: 7
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: svchost.exe
TRAP_FRAME: a172845c -- (.trap 0xffffffffa172845c)
ErrCode = 00000000
eax=af9ca000 ebx=000000e7 ecx=af9c9fff edx=af9c9fff esi=af9c9fff edi=af9c9800
eip=82a10ccb esp=a17284d0 ebp=a17284e0 iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
upzwws+0x4ccb:
82a10ccb ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 82a10ccb to 81e5ddc4
STACK_TEXT:
a172845c 82a10ccb badb0d00 af9c9fff 00000800 nt!KiTrap0E+0x2ac
WARNING: Stack unwind information not available. Following frames may be wrong.
a17284cc 00000000 af9c9800 a1728604 00000800 upzwws+0x4ccb
STACK_COMMAND: kb
FOLLOWUP_IP:
upzwws+4ccb
82a10ccb ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: upzwws+4ccb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: upzwws
IMAGE_NAME: upzwws.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ca32ea6
FAILURE_BUCKET_ID: 0xD1_upzwws+4ccb
BUCKET_ID: 0xD1_upzwws+4ccb
Followup: MachineOwner
---------
upzwws.sys questo mi sembra parte di un malware, per l'altro acpi.sys
http://support.microsoft.com/kb/983543/it
però a questo punto approfondirei la ricerca e rimozione del malware
bluddino
28-12-2010, 12:49
Io ho vista sp1 e nel link che mi hai postato parla di Seven e del server 2008... comunque potrebbe essere la scheda video? Windows dice che ha un'entrata pcie e dunque ho scaricato quei drivers... ora ho qualche dubbio, anche se mi pare ci fossero solo quelli disponibili. Ancora un volta perdona la mia scarsità in materia :D ..
Per quanto riguarda il malware cerchero' di rimediare eseguendo una scansione con Malwarebytes', che mi è stato di grande aiuto tempo fa quando prisi un grosso malware.
Un'ultima domanda... l'errore allegato al file acpi.sys potrebbe essere lo stesso causa del malware che provoca l'arresto a upzwws.sys ?
Da due giorni mi compaiono schermate blu con il nuovo sistema...l'ultima schermata blu mi segnava memory managment...ho già fatto un memtest ed è passato senza errori...per curiosità o provato il programma diagnostica memoria di windows e mi rivela subito degli errori.
Di chi mi devo fidare di memtest o del programma di windows ?
Ps: ho testato anche l'hd con hdtube e non ha trovato nessun settore danneggiato
bluddino
28-12-2010, 15:02
Ho fatto una scansione completa del disco "C:\ "con Malwarebytes' e mi ha trovato solamente un file infetto, ma era un 'residuo' del trojan di qualche tempo fa... insomma, non penso sia quello la causa del problema.
EDIT: qualcosa non quadra; proprio ora volevo analizzare le altre bsod col debugger tool, ma misteriosamente non è più installato! non ci sono nemmeno i file di setup che ho scaricato con tanta fatica ieri, niente, nemmeno i symbols :(
com'è possibile ?!
Da due giorni mi compaiono schermate blu con il nuovo sistema...l'ultima schermata blu mi segnava memory managment...ho già fatto un memtest ed è passato senza errori...per curiosità o provato il programma diagnostica memoria di windows e mi rivela subito degli errori.
Di chi mi devo fidare di memtest o del programma di windows ?
Ps: ho testato anche l'hd con hdtube e non ha trovato nessun settore danneggiato
Basta che scolleghi un banco di ram alla volta e hai la controprova ;)
bluddino
28-12-2010, 17:44
Ho appena aggiornato windows vista al service pack 2 e mentre si stava riavviando per terminare l'installazione è apparsa una bsod 0x000000D1 al file acpi.sys , poi si è riavviato di nuovo, ha completato l'installazione dell'sp2 e mi appare un messaggio di installazione correttamente completata.
Allora per testare i risultati ho aperto un video su youtube e subito è crashato, come sempre, 0x000000D1 al file upzwws.sys .
Ripeto anche di aver eseguito una scansione completa con Malwarebytes' senza risultati...
Ho appena aggiornato windows vista al service pack 2 e mentre si stava riavviando per terminare l'installazione è apparsa una bsod 0x000000D1 al file acpi.sys , poi si è riavviato di nuovo, ha completato l'installazione dell'sp2 e mi appare un messaggio di installazione correttamente completata.
Allora per testare i risultati ho aperto un video su youtube e subito è crashato, come sempre, 0x000000D1 al file upzwws.sys .
Ripeto anche di aver eseguito una scansione completa con Malwarebytes' senza risultati...
Continuo a pensare che il tuo sia un problema di malware...
bluddino
29-12-2010, 09:51
Continuo a pensare che il tuo sia un problema di malware...
Allora sapresti dirmi come sbarazzarmene? In effetti cercando upzwws.sys su google non trova nientre, a parte mie stesse discussioni.
ps: stamattina ho acceso il pc e subito e partita una bsod prima che windows si avviasse, 0x0000007E a acpi.sys
Basta che scolleghi un banco di ram alla volta e hai la controprova ;)
ho già fatto cosi per fare il memtest e non mi ha dato errori
ho già fatto cosi per fare il memtest e non mi ha dato errori
Ok, ma dovresti anche provare ad utilizzare per un po' il pc con un banco alla volta scollegato
Un'altro BSOD, temp sono un po' scese. 90 GPU e 76 per i core in full.
Cmq non sono sicuro che dipenda dalle temp.
Puoi dargli un'occhiata? ;)
http://img811.imageshack.us/img811/2987/immagineaiz.th.png (http://img811.imageshack.us/i/immagineaiz.png/)
Ora faccio il test della RAM, ma ho dei dubbi:
1) gli faccio fare il test con tutti banchi installati: 3x 2Gb
2) quanto tempo occorre affinchè il test sia terminato?
Ok, ma dovresti anche provare ad utilizzare per un po' il pc con un banco alla volta scollegato
la cosa strana e che ieri ho giocato e non ho riscontrato nessun problema...oggi ho aperto street view e mi è uscita una schermata blu...riavvio apro youtube e seconda schermata blu sempre con scritto memory managment e con questo errore:
0x0000001A
Pippinu88
29-12-2010, 19:32
quale symbol devo scarcare tra tutti con window 7 64bit?
Non devi scaricare nessun simbolo, ma devi indicare al programma WinDebug il percorso esatto al serve MS come indicato nella prima pagina di questa discussione, altrimenti ti scarichi BlueScreenView e tagli al testa al toro ;)
Pippinu88
29-12-2010, 19:52
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Administrator\Desktop\122610-14898-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Simbol
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c94e50
Debug session time: Sun Dec 26 16:40:56.847 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:08.611
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004a128f8, 0, 0}
***** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** WARNING: Unable to verify timestamp for hal.dll
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : hardware
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004a128f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set
symbol path and load symbols.
FAULTING_MODULE: fffff80002a57000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031bd6f0 fffffa80`04a128f8 : 00000000`00000001 00000000`00000000
fffff880`02fd3180 fffffa80`04a128f8 : nt+0x4a63cc
fffff880`031bd6f8 00000000`00000001 : 00000000`00000000 fffff880`02fd3180
fffffa80`04a128f8 00000000`00000000 : 0xfffffa80`04a128f8
fffff880`031bd700 00000000`00000000 : fffff880`02fd3180 fffffa80`04a128f8
00000000`00000000 00000000`00000000 : 0x1
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
--------- Cosa puo essere ragazzi? perfavore datemi una mano i symbol sono coretti?
bluddino
29-12-2010, 20:35
Allora sapresti dirmi come sbarazzarmene? In effetti cercando upzwws.sys su google non trova nientre, a parte mie stesse discussioni.
ps: stamattina ho acceso il pc e subito e partita una bsod prima che windows si avviasse, 0x0000007E a acpi.sys
up
Cosa puo essere ragazzi? perfavore datemi una mano i symbol sono coretti?
No, i simboli non sono corretti, allega qui il file dmp zippato
up
Hai provato a seguire la guida alla rimozione malware?
http://www.hwupgrade.it/forum/showthread.php?t=1599737
Proprio il fatto che non si trovi nulla in giro sul tuo errore significa che molto probabilmente si tratta di problema malware
Pippinu88
30-12-2010, 09:50
Ecco qui ragà
Ecco qui ragà
Inizia controllando la ram, puoi fare memtest oppure ancora meglio scollega un banco alla volta e vedi come va il pc
Pippinu88
30-12-2010, 10:44
ma quanto dura memtest perche già lo fatto ma siccome non finiva mai e sembrava che girava sembre intorno, e poi dv stare li davanti a guardare a lui?
Alberto-87
30-12-2010, 15:45
Salve a tutto, vi chiedo un aiuto perchè dopo solo 72 ore che ho il pc nuovo mi sono già comparse due schermate blu ... vi posto delle img con i relativi errori del sistema sperando che possiate darmi una mano a risolvere...
le immagini sono state fatte dal software bluscreen view
http://img23.imageshack.us/img23/7199/errore2g.th.jpg (http://img23.imageshack.us/i/errore2g.jpg/)
Uploaded with ImageShack.us (http://imageshack.us)
http://img23.imageshack.us/img23/7199/errore2g.th.jpg (http://img23.imageshack.us/i/errore2g.jpg/)
Uploaded with ImageShack.us (http://imageshack.us)
cambiamento
31-12-2010, 15:28
Prova ad aggiornare i driver video
Il 22 ho aggiornato i driver della scheda video.
Da quel giorno ad oggi non si sono più presentate BS.
Ti ringrazio del supporto mi sei stato davvero utile :)
Il 22 ho aggiornato i driver della scheda video.
Da quel giorno ad oggi non si sono più presentate BS.
Ti ringrazio del supporto mi sei stato davvero utile :)
;)
bluddino
01-01-2011, 17:56
Hai provato a seguire la guida alla rimozione malware?
http://www.hwupgrade.it/forum/showthread.php?t=1599737
Proprio il fatto che non si trovi nulla in giro sul tuo errore significa che molto probabilmente si tratta di problema malware
Sto provando, solamente che appena eseguo gmer mi si blocca tutto e sono costretto a spegnere tutto :/
Non saprei, chiedi li agli specialisti di rimozione e di programmi del genere
Pippinu88
02-01-2011, 14:42
allora qualcuno ha idea di cosa fare per il mio errore? ho fatto il test delle memorie con memetest, nessun errore. Ho controllato l HD con hdd regenerator 2011, anche qui nessun problema, cosa mi rimane da fare? l errore si presenta una volta ogni 2 giorni in media, la schermata blu non mi compare però al riavvio mi compare la finestra ch e ha salvato il file dmp. perfavore aiuto tante grazie
Il memtest può durare anche ore ed ore, infatti ti converrebbe lasciarlo la sera per la mattina :D oppure come ti avevo consigliato, per sveltire e affinare i risultati, potresti scollegare un banco di ram alla volta e vedere come va l'utilizzo del pc.
Il tuo problema ntoskrnl.exe come vedi è molto diffuso e la causa di difficile individuazione
http://support.microsoft.com/search/default.aspx?query=ntoskrnl.exe&mode=r&catalog=LCID%3D1040
Bisogna andare per tentativi
Tech Info....
0x0000c1f5 (0xc01a000a, 0x8d500000, 0x00000000, 0x00000000)
su un portatile...il problema lo da in avvia , anche in mod. provvisoria e anche facendo partire l'installazione da cd di vista...
facendo partire ubuntu in livecd però è andato tutto a buon fine...non sembrava ci fosse alcun problema...
che fò ?
Se riesci ad estrarre qualche informazione in più dalla schermata o magari meglio ancora il file dmp col cd live
Se riesci ad estrarre qualche informazione in più dalla schermata o magari meglio ancora il file dmp col cd live
adesso ho formattato e il problema non me lo da più...:D
:banned:
adesso ho formattato e il problema non me lo da più...:D
:banned:
Se davvero non si ripresenterà più allora era un virus, se la causa fosse hw/driver allora potrebbe rifarci :D
Pippinu88
02-01-2011, 20:13
adesso mi si e spento un altra volta ma l errore e cambiato cm mai? ade l errore e atikmdag.sys fffffffffffffff
Qui puoi trovare un'ampia casistica sul tuo ultimo problema
http://support.microsoft.com/search/default.aspx?query=Atikmdag.sys&mode=r&catalog=LCID%3D1040
vedi anche qui
http://www.hwupgrade.it/forum/showthread.php?t=1782864
Ragazzi sto impazzendo con le schermate blu che sto avendo!!
questo è il report:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: oodag.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ce49fd to 82c8bf6b
STACK_TEXT:
88e920d4 82ce49fd badb0d00 887f5801 00000001 nt!KiSystemFatalException+0xf
88e92144 856cbec0 00000000 00000000 00004540 nt!MiRemoveNode+0x158
WARNING: Frame IP not in any known module. Following frames may be wrong.
88e92148 00000000 00000000 00004540 0000454f 0x856cbec0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82c8bf6b c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemFatalException+f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: oodag.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ce49fd to 82c8bf6b
STACK_TEXT:
88e920d4 82ce49fd badb0d00 887f5801 00000001 nt!KiSystemFatalException+0xf
88e92144 856cbec0 00000000 00000000 00004540 nt!MiRemoveNode+0x158
WARNING: Frame IP not in any known module. Following frames may be wrong.
88e92148 00000000 00000000 00004540 0000454f 0x856cbec0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82c8bf6b c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemFatalException+f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: oodag.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ce49fd to 82c8bf6b
STACK_TEXT:
88e920d4 82ce49fd badb0d00 887f5801 00000001 nt!KiSystemFatalException+0xf
88e92144 856cbec0 00000000 00000000 00004540 nt!MiRemoveNode+0x158
WARNING: Frame IP not in any known module. Following frames may be wrong.
88e92148 00000000 00000000 00004540 0000454f 0x856cbec0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82c8bf6b c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemFatalException+f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: oodag.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ce49fd to 82c8bf6b
STACK_TEXT:
88e920d4 82ce49fd badb0d00 887f5801 00000001 nt!KiSystemFatalException+0xf
88e92144 856cbec0 00000000 00000000 00004540 nt!MiRemoveNode+0x158
WARNING: Frame IP not in any known module. Following frames may be wrong.
88e92148 00000000 00000000 00004540 0000454f 0x856cbec0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82c8bf6b c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemFatalException+f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: oodag.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ce49fd to 82c8bf6b
STACK_TEXT:
88e920d4 82ce49fd badb0d00 887f5801 00000001 nt!KiSystemFatalException+0xf
88e92144 856cbec0 00000000 00000000 00004540 nt!MiRemoveNode+0x158
WARNING: Frame IP not in any known module. Following frames may be wrong.
88e92148 00000000 00000000 00004540 0000454f 0x856cbec0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82c8bf6b c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemFatalException+f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: oodag.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ce49fd to 82c8bf6b
STACK_TEXT:
88e920d4 82ce49fd badb0d00 887f5801 00000001 nt!KiSystemFatalException+0xf
88e92144 856cbec0 00000000 00000000 00004540 nt!MiRemoveNode+0x158
WARNING: Frame IP not in any known module. Following frames may be wrong.
88e92148 00000000 00000000 00004540 0000454f 0x856cbec0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82c8bf6b c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemFatalException+f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
0: kd>
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: oodag.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ce49fd to 82c8bf6b
STACK_TEXT:
88e920d4 82ce49fd badb0d00 887f5801 00000001 nt!KiSystemFatalException+0xf
88e92144 856cbec0 00000000 00000000 00004540 nt!MiRemoveNode+0x158
WARNING: Frame IP not in any known module. Following frames may be wrong.
88e92148 00000000 00000000 00004540 0000454f 0x856cbec0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
82c8bf6b c3 ret
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiSystemFatalException+f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID: 0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
Sembrerebbe che sia questo oodag.exe ,ma non capisco se si riferisce al programma di deframmentazione O&O defrag oppure è qualcos altro :S
Elimina per bene O&O dal tuo pc, poi testa le ram scollegadone un banco alla volta e provando il pc come va. Per la deframmentazione dell'hd lascia perdere i programmi esterni e usa l'ottimo deframmentatore integrato nel sistema
Ho disinstallato O&O defrag e ho provato le ram(tutto ok).Vediamo un po' come va adesso ;)
Niente da fare,dopo diverse ore di pace,mi è apparsa un'altra blue screen,ecco il report:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {12037414, 2, 0, 90c292dd}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iBegin+2 )
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
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: 12037414, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 90c292dd, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82d72718
Unable to read MiSystemVaType memory at 82d52160
12037414
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 82d30bc0 -- (.trap 0xffffffff82d30bc0)
ErrCode = 00000000
eax=86ad20e0 ebx=86ad2028 ecx=86b21100 edx=86ad20f0 esi=00000000 edi=82c4a354
eip=90c292dd esp=82d30c34 ebp=82d30c54 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
USBPORT!USBPORT_Xdpc_iBegin+0x2:
90c292dd 55 push ebp
Resetting default scope
LAST_CONTROL_TRANSFER: from 90c292dd to 82c5082b
STACK_TEXT:
82d30bc0 90c292dd badb0d00 86ad20f0 82d30be0 nt!KiTrap0E+0x2cf
82d30c30 90c298c7 86ad2028 86ad2720 82c4a354 USBPORT!USBPORT_Xdpc_iBegin+0x2
82d30c54 90c29d18 86ad20f0 86ad2720 86ad2002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x54
82d30c78 82c723b5 86ad272c 86ad2002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82d30cd4 82c72218 82d33d20 82d3d280 00000000 nt!KiExecuteAllDpcs+0xf9
82d30d20 82c72038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82d30d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Xdpc_iBegin+2
90c292dd 55 push ebp
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Xdpc_iBegin+2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
BUCKET_ID: 0xD1_USBPORT!USBPORT_Xdpc_iBegin+2
Followup: MachineOwner
---------
0: kd>
E dopo 10 minuti un'altra :(
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {3ec59172, 2, 1, 9092c167}
Probably caused by : hardware ( usbuhci!UhciPollAsyncEndpoint+88 )
Followup: MachineOwner
---------
1: 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: 3ec59172, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 9092c167, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dbd718
Unable to read MiSystemVaType memory at 82d9d160
3ec59172
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 807e1b08 -- (.trap 0xffffffff807e1b08)
ErrCode = 00000002
eax=881c7171 ebx=cd3c7100 ecx=86bb5a30 edx=88193600 esi=00000100 edi=86baf0e0
eip=9092c167 esp=807e1b7c ebp=807e1b8c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb:
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl ds:0023:3ec59172=??
Resetting default scope
MISALIGNED_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
LAST_CONTROL_TRANSFER: from 9092c167 to 82c9b82b
STACK_TEXT:
807e1b08 9092c167 badb0d00 88193600 807e1b4c nt!KiTrap0E+0x2cf
807e1b8c 90922652 cd3c7100 86baf028 87b60578 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb
807e1bb8 9091fb6e 86baffe0 87b60578 00000000 usbuhci!UhciPollAsyncEndpoint+0x88
807e1bcc 9092c28a 86baffe0 87b60578 82c95354 usbuhci!UhciPollEndpoint+0x20
807e1be8 9092a6c2 86baf0e0 87b60302 82c95354 USBPORT!MPf_PollEndpoint+0x96
807e1c0c 9092a5ca 00000004 87b60464 0000000e USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xef
807e1c2c 9092b9cb 86baf028 87b603d8 0000000e USBPORT!USBPORT_iSetGlobalEndpointState+0x18
807e1c54 9092bd18 87b603d8 86baf720 86baf002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x158
807e1c78 82cbd3b5 86baf72c 86baf002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e1cd4 82cbd218 807c5120 807ca800 00000000 nt!KiExecuteAllDpcs+0xf9
807e1d20 82cbd038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807e1d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+88
90922652 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+88
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
1: 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: 3ec59172, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 9092c167, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dbd718
Unable to read MiSystemVaType memory at 82d9d160
3ec59172
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 807e1b08 -- (.trap 0xffffffff807e1b08)
ErrCode = 00000002
eax=881c7171 ebx=cd3c7100 ecx=86bb5a30 edx=88193600 esi=00000100 edi=86baf0e0
eip=9092c167 esp=807e1b7c ebp=807e1b8c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb:
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl ds:0023:3ec59172=??
Resetting default scope
MISALIGNED_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
LAST_CONTROL_TRANSFER: from 9092c167 to 82c9b82b
STACK_TEXT:
807e1b08 9092c167 badb0d00 88193600 807e1b4c nt!KiTrap0E+0x2cf
807e1b8c 90922652 cd3c7100 86baf028 87b60578 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb
807e1bb8 9091fb6e 86baffe0 87b60578 00000000 usbuhci!UhciPollAsyncEndpoint+0x88
807e1bcc 9092c28a 86baffe0 87b60578 82c95354 usbuhci!UhciPollEndpoint+0x20
807e1be8 9092a6c2 86baf0e0 87b60302 82c95354 USBPORT!MPf_PollEndpoint+0x96
807e1c0c 9092a5ca 00000004 87b60464 0000000e USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xef
807e1c2c 9092b9cb 86baf028 87b603d8 0000000e USBPORT!USBPORT_iSetGlobalEndpointState+0x18
807e1c54 9092bd18 87b603d8 86baf720 86baf002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x158
807e1c78 82cbd3b5 86baf72c 86baf002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e1cd4 82cbd218 807c5120 807ca800 00000000 nt!KiExecuteAllDpcs+0xf9
807e1d20 82cbd038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807e1d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+88
90922652 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+88
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
1: 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: 3ec59172, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 9092c167, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dbd718
Unable to read MiSystemVaType memory at 82d9d160
3ec59172
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 807e1b08 -- (.trap 0xffffffff807e1b08)
ErrCode = 00000002
eax=881c7171 ebx=cd3c7100 ecx=86bb5a30 edx=88193600 esi=00000100 edi=86baf0e0
eip=9092c167 esp=807e1b7c ebp=807e1b8c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb:
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl ds:0023:3ec59172=??
Resetting default scope
MISALIGNED_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
LAST_CONTROL_TRANSFER: from 9092c167 to 82c9b82b
STACK_TEXT:
807e1b08 9092c167 badb0d00 88193600 807e1b4c nt!KiTrap0E+0x2cf
807e1b8c 90922652 cd3c7100 86baf028 87b60578 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb
807e1bb8 9091fb6e 86baffe0 87b60578 00000000 usbuhci!UhciPollAsyncEndpoint+0x88
807e1bcc 9092c28a 86baffe0 87b60578 82c95354 usbuhci!UhciPollEndpoint+0x20
807e1be8 9092a6c2 86baf0e0 87b60302 82c95354 USBPORT!MPf_PollEndpoint+0x96
807e1c0c 9092a5ca 00000004 87b60464 0000000e USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xef
807e1c2c 9092b9cb 86baf028 87b603d8 0000000e USBPORT!USBPORT_iSetGlobalEndpointState+0x18
807e1c54 9092bd18 87b603d8 86baf720 86baf002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x158
807e1c78 82cbd3b5 86baf72c 86baf002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e1cd4 82cbd218 807c5120 807ca800 00000000 nt!KiExecuteAllDpcs+0xf9
807e1d20 82cbd038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807e1d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+88
90922652 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+88
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
1: 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: 3ec59172, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 9092c167, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dbd718
Unable to read MiSystemVaType memory at 82d9d160
3ec59172
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 807e1b08 -- (.trap 0xffffffff807e1b08)
ErrCode = 00000002
eax=881c7171 ebx=cd3c7100 ecx=86bb5a30 edx=88193600 esi=00000100 edi=86baf0e0
eip=9092c167 esp=807e1b7c ebp=807e1b8c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb:
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl ds:0023:3ec59172=??
Resetting default scope
MISALIGNED_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
LAST_CONTROL_TRANSFER: from 9092c167 to 82c9b82b
STACK_TEXT:
807e1b08 9092c167 badb0d00 88193600 807e1b4c nt!KiTrap0E+0x2cf
807e1b8c 90922652 cd3c7100 86baf028 87b60578 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb
807e1bb8 9091fb6e 86baffe0 87b60578 00000000 usbuhci!UhciPollAsyncEndpoint+0x88
807e1bcc 9092c28a 86baffe0 87b60578 82c95354 usbuhci!UhciPollEndpoint+0x20
807e1be8 9092a6c2 86baf0e0 87b60302 82c95354 USBPORT!MPf_PollEndpoint+0x96
807e1c0c 9092a5ca 00000004 87b60464 0000000e USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xef
807e1c2c 9092b9cb 86baf028 87b603d8 0000000e USBPORT!USBPORT_iSetGlobalEndpointState+0x18
807e1c54 9092bd18 87b603d8 86baf720 86baf002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x158
807e1c78 82cbd3b5 86baf72c 86baf002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e1cd4 82cbd218 807c5120 807ca800 00000000 nt!KiExecuteAllDpcs+0xf9
807e1d20 82cbd038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807e1d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+88
90922652 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+88
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
1: 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: 3ec59172, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 9092c167, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dbd718
Unable to read MiSystemVaType memory at 82d9d160
3ec59172
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: SYSTEM
TRAP_FRAME: 807e1b08 -- (.trap 0xffffffff807e1b08)
ErrCode = 00000002
eax=881c7171 ebx=cd3c7100 ecx=86bb5a30 edx=88193600 esi=00000100 edi=86baf0e0
eip=9092c167 esp=807e1b7c ebp=807e1b8c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb:
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl ds:0023:3ec59172=??
Resetting default scope
MISALIGNED_IP:
USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+cb
9092c167 088b72208971 or byte ptr [ebx+71892072h],cl
LAST_CONTROL_TRANSFER: from 9092c167 to 82c9b82b
STACK_TEXT:
807e1b08 9092c167 badb0d00 88193600 807e1b4c nt!KiTrap0E+0x2cf
807e1b8c 90922652 cd3c7100 86baf028 87b60578 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0xcb
807e1bb8 9091fb6e 86baffe0 87b60578 00000000 usbuhci!UhciPollAsyncEndpoint+0x88
807e1bcc 9092c28a 86baffe0 87b60578 82c95354 usbuhci!UhciPollEndpoint+0x20
807e1be8 9092a6c2 86baf0e0 87b60302 82c95354 USBPORT!MPf_PollEndpoint+0x96
807e1c0c 9092a5ca 00000004 87b60464 0000000e USBPORT!USBPORT_iSetGlobalEndpointStateTx+0xef
807e1c2c 9092b9cb 86baf028 87b603d8 0000000e USBPORT!USBPORT_iSetGlobalEndpointState+0x18
807e1c54 9092bd18 87b603d8 86baf720 86baf002 USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x158
807e1c78 82cbd3b5 86baf72c 86baf002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e1cd4 82cbd218 807c5120 807ca800 00000000 nt!KiExecuteAllDpcs+0xf9
807e1d20 82cbd038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
807e1d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciPollAsyncEndpoint+88
90922652 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbuhci!UhciPollAsyncEndpoint+88
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
I problemi sono parecchi, a cominciare da quello con le porte usb, poi dovresti provare ad aggiornare i driver del chipset e magari anche quelli della scheda video, la ram l'hai testata scollegando un banco alla volta?
Ma possibile che i driver asus scaricati dal sito loro non vadano bene?
Oppure dopo il formattone è meglio che lascio installare tutto a windows?
Ho reinstallato e aggiornato sia chipset che driver di ram e scheda video ieri sera.Vediamo un poco...
edit:niente da fare,si blocca ancora :(
Leggendo tra i vari dmp c'è anche una causa hw non meglio specificata, potrebbe essere qualche componente difettoso o in conflitto con qualcun'altro, magari la mobo :rolleyes: il pc era preassemblato o l'hai assemblato tu?
Il computer me lo ha assemblato mio zio perchè all'epoca ancora non ero capacissimo,ma i pezzi li ho comprati io.Mi ricordo che pero' un'altra scheda madre come il mio modello la cambiammo perchè difettata,pero' questa è sempre andata bene per due anni...:(
Comunque da quando ha iniziato a darti problemi, per caso prima avevi un SO diverso nel pc?
Mi ha fatto un po' di problemini ad inizio dicembre,ho approfittato e ho messo win 7 a 64 bit,poi nessun problema.
Un paio di giorni fa invece di nuovo le BSOD,senza aver cambiato niente a livello hardware.
Io sono strasicuro che sia un problema di driver,perchè in passato gia mi uscirono alcune BSOD ma subito riuscii a porre rimedio disinstallando i driver delle usb e della scheda video.Questa volta pero' sembra diverso....
p.s. ho riformattato e messo su win 7 64 bit.Speriamo sia la volta buona....ovviamente O&O defrag non lo metto,e per ora non installo nessun driver della asus,faccio fare tutto a lui,vediamo un po' come va...:)
hacker39
07-01-2011, 21:05
recentemente ho avuto una serie impressionante di bsod che avvengono quando lascio il computer in idle per molto tempo.Addirittura l'ultimo è avvenuto mentre facevo una scansione con MAM, avevo lo schermo spento e quando l'ho riacceso mi dava segnale assente e anche schiacciando qualsiasi pulsante non succede nulla. Al riavvio del computer windows mi dice che il sistema operativo è stato ripristinato etc etc senza darmi nessuna informazione.Fortunatamente mi ha salvato il minidump.
Ecco cosa ne risulta con Bluescreenview link (http://img59.imageshack.us/img59/7282/catturavo.png)
Sembra che sia imputato in qualche modo il driver ati della scheda video, ma è possibile che mi blocchi il pc anche quando è in idle?
Qualche anima pia mi può aiutare?
Sembra che sia imputato in qualche modo il driver ati della scheda video, ma è possibile che mi blocchi il pc anche quando è in idle?Qualche anima pia mi può aiutare?
Non so se ho l'anima pia :D comunque prova a disattivare/disabilitare tutti i servizi e processi dell'ati in avvio automatico, da msconfig e nei servizi
hacker39
07-01-2011, 22:09
@ eress
ho provato a disinstallare i driver (con annessa pulizia con driver sweeper) reinstallati e ho provato a rifare una scansione con MAM e puntualmente si è presentato l'errore con bsod. I file imputati sono 2 :atimdag.sys e ntoskrnl.exe
Adesso provo a fermare il servizio ati e a togliere i due processi ati dall'avvio
edit:il fatto che le bsod avvengano a schermo spento c'entra qualcosa?
Sto sconvolto :(
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002a84905, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff80002a84905, 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!ExpInterlockedPopEntrySListFault16+0
fffff800`02a84905 498b08 mov rcx,qword ptr [r8]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb90e0
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: svchost.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff8800a9b52b8 -- (.exr 0xfffff8800a9b52b8)
ExceptionAddress: fffff80002a84905 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff8800a9b5360 -- (.trap 0xfffff8800a9b5360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000023720006 rbx=0000000000000000 rcx=fffffa80039019d0
rdx=ffff0380034aa571 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a84905 rsp=fffff8800a9b54f0 rbp=fffff8800a9b5540
r8=ffff0380034aa570 r9=fffff80002c0dd48 r10=fffffa80039019d0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a84905 498b08 mov rcx,qword ptr [r8] ds:0001:ffff0380`034aa570=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002abba39 to fffff80002a81740
STACK_TEXT:
fffff880`0a9b4ae8 fffff800`02abba39 : 00000000`0000001e ffffffff`c0000005 fffff800`02a84905 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a9b4af0 fffff800`02a80d82 : fffff880`0a9b52b8 fa8004d5`1d280460 fffff880`0a9b5360 00000000`000001d0 : nt!KiDispatchException+0x1b9
fffff880`0a9b5180 fffff800`02a7f68a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0a9b5360 fffff800`02a84905 : fa8004d5`1d280460 fffff800`02a4537f 00000000`00003400 00000000`00003400 : nt!KiGeneralProtectionFault+0x10a
fffff880`0a9b54f0 fffff800`02a4537f : 00000000`00003400 00000000`00003400 fffff880`0a9b5540 fffff800`02d21c95 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0a9b5500 fffff800`02ce1ada : fffffa80`04cf8de0 fffffa80`00000000 00000000`00000000 00000000`00000005 : nt!MiPfPutPagesInTransition+0x396
fffff880`0a9b5670 fffff800`02edf0ad : 00000000`000000a8 00000000`000001a0 fffffa80`058de930 fffff880`0a9b5738 : nt!MmPrefetchPages+0xda
fffff880`0a9b56d0 fffff800`02ee70ce : fffff8a0`00000000 fffff8a0`000000c0 fffff8a0`000003eb 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x21d
fffff880`0a9b57d0 fffff800`02ee7c67 : 00000000`00000000 fffff880`0a9b5c60 fffff880`0a9b59c8 fffff8a0`01af1060 : nt!PfpPrefetchRequestPerform+0x30e
fffff880`0a9b5920 fffff800`02ef423e : fffff880`0a9b59c8 00000000`00000001 fffffa80`070c66a0 00000000`00000000 : nt!PfpPrefetchRequest+0x176
fffff880`0a9b5990 fffff800`02ef896e : 00000000`00000000 00000000`0249fa50 00000000`0000004f fffffa80`062eeb01 : nt!PfSetSuperfetchInformation+0x1ad
fffff880`0a9b5a70 fffff800`02a80993 : fffffa80`0469c060 00000000`00000000 00000000`00000001 00000000`00000001 : nt!NtSetSystemInformation+0xb91
fffff880`0a9b5be0 00000000`77c0144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0249fa28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c0144a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02a84905 498b08 mov rcx,qword ptr [r8]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0
BUCKET_ID: X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0
Followup: MachineOwner
---------
Stamattina appena acceso il pc si è bloccato sulla schermata del desktop,completamente morto.
Ora invece sto facendo tanti stress test,burnin test e OCCT,ma va tutto liscio come l'olio....ho fatto anche la prova con memtest sui blocchi di ram separatamente,e anche li' tutto bene...
Cosa cavolo devo fare? :(
Ho appena terminato il test di OCCT per le tensioni,sembrano tutte ok:
http://img521.imageshack.us/img521/5969/2011010812h33cpu1.png
http://img151.imageshack.us/img151/6467/2011010812h33cpu2.png
http://img443.imageshack.us/img443/7589/2011010812h33gpu1.png
http://img222.imageshack.us/img222/8044/2011010812h33vcore.png
http://img573.imageshack.us/img573/9198/2011010812h33volt3.png
http://img26.imageshack.us/img26/2875/2011010812h33volt12.png
Non so a cosa altro pensare :eek:
hacker39
08-01-2011, 13:50
sembra che disattivando il servizio ati e i due processi che si avviavano automaticamente tutto si sia risolto.Visto che cercando su internet sembra che il servizio amd external events utility non sia necessario e perciò lo lascio disattivato. Posso invece riattivare l'autorun del catalyst control manager o potrebbe creare problemi?
sembra che disattivando il servizio ati e i due processi che si avviavano automaticamente tutto si sia risolto.Visto che cercando su internet sembra che il servizio amd external events utility non sia necessario e perciò lo lascio disattivato. Posso invece riattivare l'autorun del catalyst control manager o potrebbe creare problemi?
Se per ora sembra che vada bene lascerei stare tutto così ;)
Poi comuqnue puoi anche attivare un solo processo/servizio, se tornano i problemi almeno sai qual'è la causa
hacker39
08-01-2011, 16:52
ok grazie proverò ad attivare una cosa per volta per vedere cosa da problemi
Ragazzi una piccola domanda: dopo natale ho comprato un monitor nuovo,affiancandolo a quello vecchio.Io ho un UPS al quale ho collegato il pc e il monitor nuovo.Il vecchio è collegato direttamente alla ciabatta a terra.
Puo' essere che i blocchi siano dovuti all'ups che non ce la fa ?Lo chiedo perchè non so veramente che pesci pigliare.....
alethebest90
09-01-2011, 14:41
buon giorno e buona domenica
oggi mi si è riavviato il pc dopo una schermata blue che purtroppo non sono riuscito a vedere perchè non ero in camera
ho letto la guida in prima pagina ma non riesco a far leggere il file .dmp perchè mi richiede le autorizzazioni anche se sono io l'amministratore...come devo fare ?
ho win 7 x64 con UAC al max
quando cerchi windbg da start,selezionalo con tasto destro ed esegui come amministratore :)
alethebest90
09-01-2011, 15:10
quando cerchi windbg da start,selezionalo con tasto destro ed esegui come amministratore :)
grazie ci sono riuscito però da una prima analisi si riesce a vedere qualcosa, cioè che il file incriminato è
BugCheck 3B, {c0000005, fffff88004ca1817, fffff880083798c0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
però il resto non lo riesco a vedere perchè mi dice che i symbol non sono corretti...ma quali devo scaricare ? io ho scaricato quelli per windows 7 RTM retail x64
mo sto provando a scaricare quelli per windows 7 x64 checked
http://support.microsoft.com/search/default.aspx?query=ATIKMDAG.SYS&mode=r&catalog=LCID%3D1040
alethebest90
09-01-2011, 16:06
http://support.microsoft.com/search/default.aspx?query=ATIKMDAG.SYS&mode=r&catalog=LCID%3D1040
si a quanto pare sono i driver della scheda video (probabilmente è il nuovo catalyst) vabbe fortuna che non capita sempre...diciamo che è la seconda volta da quando li ho installati e sopratutto sembra che lo fa solo lasciando il sistema in idle
a questo punto aspetto i nuovi driver sperando che venga risolto ;)
Altri BSOD, sempre gli stessi, nel registro eventi vedo sia causato dai core della CPU. Potrebbero essere i voltaggi mal settati?
i7 2,66 Ghz @ 3.33 Ghz
Core a 1.19 poi 1.20 ora 1.22
QPI 1.20 ora a 1.22
DRAMv 1.62
config pc in firma ;)
jacoscar
09-01-2011, 16:29
Con Bluescreenview....
010911-57548-01.dmp 09/01/2011 17:18:53 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000030 00000000`00000002 00000000`00000000 fffff880`05a34394 NETw5s64.sys NETw5s64.sys+1b4394 x64 C:\Windows\Minidump\010911-57548-01.dmp 2 15 7600
con quell'errore dovresti aggiornare i driver della scheda di rete wireless
jacoscar
09-01-2011, 18:12
con quell'errore dovresti aggiornare i driver della scheda di rete wireless
grazie, ma non capisco... sono già aggiornati! :confused:
poi dopo un'ora mi ha dato quest'altro errore :muro:
010911-38906-01.dmp 09/01/2011 18:11:54 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`031f8477 hal.dll hal.dll+2477 x64 C:\Windows\Minidump\010911-38906-01.dmp 2 15 7600
Per hal.dll vedi qui
http://support.microsoft.com/search/default.aspx?mode=r&query=hal.dll&spid=14019&catalog=LCID%3D1040&1040comm=1&1040mt=1&ast=25&ast=28&ast=30&ast=31&res=10
controlla anche la ram
Altri BSOD, sempre gli stessi, nel registro eventi vedo sia causato dai core della CPU. Potrebbero essere i voltaggi mal settati?
i7 2,66 Ghz @ 3.33 Ghz
Core a 1.19 poi 1.20 ora 1.22
QPI 1.20 ora a 1.22
DRAMv 1.62
config pc in firma ;)
up
PS: il BSOD compare solo dopo ore di BOINC in full
è successo gia 4 volte
potete aiutarmi per piacere (acer 6930G) ho fatto la pulizia con cc cleaner e il file minudump è stato rimosso
Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7600.2.0.0.256.1
ID impostazioni locali: 1040
Ulteriori informazioni sul problema:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002C867F0
BCP3: FFFFF88009859BA0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\011311-18720-01.dmp
C:\Users\Salvatore\AppData\Local\Temp\WER-37783-0.sysdata.xml
Leggere l'informativa sulla privacy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0410
Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt
grazie a tutti
è successo gia 4 volte
potete aiutarmi per piacere (acer 6930G) ho fatto la pulizia con cc cleaner e il file minudump è stato rimosso
Vedi qui
http://www.hwupgrade.it/forum/showthread.php?t=1955371
Vedi qui
http://www.hwupgrade.it/forum/showthread.php?t=1955371
ho visto il primo post...
ma non ho capito molto. il file minidump per postarlo completo non c'è. inoltre qualè il codice errore da mettere sul sito microsoft??
non si può sapere come risolvere?
Se imposti correttamente i valori nelle opzioni avanzante>avvio e ripristino come spiegato nella guida, alla fine dopo l'eventuale schermata blu dovresti trovare il file dmp in C/Windows/Minidump lo zippi e lo posti come allegato
ragazzi non so se bastano come info però per ora sono risucito a racimolare queste con bluescreenview ==================================================
Dump File : MEMORY.DMP
Crash Time : 15/01/2011 21:56:48
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000019
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`009b2180
Parameter 4 : 00000000`00000004
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\MEMORY.DMP
Processors Count : 8
Major Version : 15
Minor Version : 7600
Dump File Size : 482.271.160
==================================================
qualche soluzione? il bsod è relativo al pc in firma e sorge sporadicamente...
Sono informazioni incomplete ed inutilizabili
Sono informazioni incomplete ed inutilizabili
è riapparso il bsod e dice questo
"a clock interrupt was not recieved on a secondary processor within the allocated interval", il bug check code e i parametri sono quelli che ho postato precedentemente...
Dovresti dare una controllata all'HW, hai fatto overclock, qualche intervento/modifica hw ultimamente?
vedi anche qui
http://www.evga.com/forumsarchive/tm.asp?m=100494809&mpage=1&key
Ciao a tutti...avrei bisogno di un vostro aiuto in merito a questo problema. Il pc è un Dell 1564 con windows 7 64bit.
*******************************************************************************
* *
* 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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88004e1d8f2, The address that the exception occurred at
Arg3: fffff88002f4eda8, Exception Record Address
Arg4: fffff88002f4e610, Context Record Address
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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff80002e11000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49cc26b1
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {ERRORE DI EXCEPTION} Divisione intera per zero.
FAULTING_IP:
bcmwl664+58f2
fffff880`04e1d8f2 41f7f9 idiv eax,r9d
EXCEPTION_RECORD: fffff88002f4eda8 -- (.exr 0xfffff88002f4eda8)
ExceptionAddress: fffff88004e1d8f2 (bcmwl664+0x00000000000058f2)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff88002f4e610 -- (.cxr 0xfffff88002f4e610)
rax=000000000000000c rbx=fffffa80038ef000 rcx=0000000000001770
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80038ef000
rip=fffff88004e1d8f2 rsp=fffff88002f4efe8 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=00000000000007d0
r11=0000000000000064 r12=0000000000000001 r13=0000000000000002
r14=fffffa80038efe88 r15=0000000000000056
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
bcmwl664+0x58f2:
fffff880`04e1d8f2 41f7f9 idiv eax,r9d
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88004e261aa to fffff88004e1d8f2
STACK_TEXT:
FOLLOWUP_IP:
bcmwl664+58f2
fffff880`04e1d8f2 41f7f9 idiv eax,r9d
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: bcmwl664+58f2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bcmwl664
IMAGE_NAME: bcmwl664.sys
STACK_COMMAND: .cxr 0xfffff88002f4e610 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Ê la scheda di rete wireless Broadcom 802.11 Network Adapter wireless driver
Sì è vero, è il driver della periferica wireless ma come posso fare per sistemarlo??
Ho notato che il problema si presenta quando stacco l'alimentazione ed il portatile lavora con la sua batteria. O quando lo avvio senza alimentazione.
Cerca se ci sono driver aggiornati e dai anche una controllata nel risparmio energia>opzioni avanzate>wireless
Cerca se ci sono driver aggiornati e dai anche una controllata nel risparmio energia>opzioni avanzate>wireless
Ok grazie al tuo consiglio forse ho risolto. Ora il pc era stabile. Ho settato la scheda wireless con lo stesso profilo di risparmio energetico, ovvero tutto al max delle prestazioni.
Così per curiosità, come ti è venuto di consigliami di guardare questo particolare?? :D
Così per curiosità, come ti è venuto di consigliami di guardare questo particolare?? :D
Perché essendo coinvolta la scheda di rete, ci poteva anche stare un problema nelle impostazioni del risparmio energia e poi mi avevi dato l'indizio della batteria...;)
mi spiegate che significa??ho provato ad eseguire la procedura descritta in prima pagina ma non ci capisco molto,qualcuno mi dà una mano???
http://img715.imageshack.us/img715/497/fotoxq.th.jpg (http://img715.imageshack.us/i/fotoxq.jpg/)
Uploaded with ImageShack.us (http://imageshack.us)
Inizia a etstare la ram, magari scollegando un banco alla volta. Seguendo la guida dovresti riuscire ad estrarre il file dmp, alla fine serve quello per risalire alla causa
Inizia a etstare la ram, magari scollegando un banco alla volta. Seguendo la guida dovresti riuscire ad estrarre il file dmp, alla fine serve quello per risalire alla causa
dicevi a me??
mi puoi spiegare un po meglio,come faccio a testare la ram??è dovuto alla ram il problema???:muro: :muro: :muro:
non ci capisco nulla!!
|| Luca ||
19-01-2011, 13:07
Ragazzi, la versione dei symbols da scaricare è la retail o la checked?
No non devi scaricare nulla, ma solo indicare al programma il percorso ai symbols sul server MS, nella guida c'è scritto mi pare
una schermata blu recitante tipo:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
If this is the first time you’ve seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to be sure you have adequate disk space. If a driver is identified in the Stop message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters.
Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
che appare la prima volta che si accende un notebook nuovo, ancor prima di installare e configurare tutto, che cosa può significare? :muro:
Salve a tutti, provo anche io a chiedervi aiuto perchè non so più dove sbattere la testa :(
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\011911-22453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02810000 PsLoadedModuleList = 0xfffff800`02a4de50
Debug session time: Wed Jan 19 09:20:30.256 2011 (UTC + 1:00)
System Uptime: 0 days 0:04:45.913
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc000001d, fffff88006eb7ec0, 0, 0}
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+70740 )
Followup: MachineOwner
---------
avete qualche idea? Da quando ho installato Win7 ho continuamente bluscreen, con esattamente lo stesso hardware che avevo usando xp che non mi ha mai dato problemi...
una schermata blu recitante tipo:
che appare la prima volta che si accende un notebook nuovo, ancor prima di installare e configurare tutto, che cosa può significare? :muro:
Che ti hanno appena venduto un pc difettoso :rolleyes:
Salve a tutti, provo anche io a chiedervi aiuto perchè non so più dove sbattere la testa :(
C'è un errore nei symbols e da quel log non si ricava nulla. Riprova seguendo bene la guida per il bugcheck puntando per i simboli al server di MS oppure posta qui il file dmp zippato
Ho messo come percorso dei symbol il server, ma ora mi appare molto più corto:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\011911-22453-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02810000 PsLoadedModuleList = 0xfffff800`02a4de50
Debug session time: Wed Jan 19 09:20:30.256 2011 (UTC + 1:00)
System Uptime: 0 days 0:04:45.913
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc000001d, fffff88006eb7ec0, 0, 0}
Probably caused by : hardware ( partmgr!PmWmiCounterIoStart+16 )
Followup: MachineOwner
---------
è sbagliato di nuovo? Se sì provvedo ad allegarlo al topic :mc:
|| Luca ||
19-01-2011, 18:12
No non devi scaricare nulla, ma solo indicare al programma il percorso ai symbols sul server MS, nella guida c'è scritto mi pare
Come no?
4) Windows Debugging Tools necessita dei "symbols" che trovate nella stessa pagina del debugger, è il link subito sopra e vi porterà QUI
Dovrete scegliere i symbols package adeguati alla versione del vostro Windows (la scelta va da Win2000 a Windows7), la dimensione dei pacchetti è di circa 200MB.
Ho messo come percorso dei symbol il server, ma ora mi appare molto più corto
E più chiaro anche :D
Sembra una causa HW non meglio specificata
Allora inizia a contrtollare ram e hd
Come no?
Nota bene: Se il controllo del file dump mostra a video "Your debugger is not using the correct symbols", inserite come percorso dei symbols (passaggio n.6 di quesa guida) il link che segue dopo aver eliminato quelli precedentemente installati (al posto di c:\Windows\symbols potete usare una qualsiasi cartella di vostra preferenza):
SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
;)
E più chiaro anche :D
Sembra una causa HW non meglio specificata
Allora inizia a contrtollare ram e hd
Per quanto riguarda la ram c'è memtest e/o goldmemory, per l'hd mi sai consigliare un tool simile che lo "stressi"?
Puoi trovare l'utilità specifica per l'hd sul sito del costruttore, per la ram se ti dovessero restare dei dubbi scollega un banco alla volta e vedi come va il pc
MatteoBirel
20-01-2011, 16:19
cavolo col pc nuovo in firma è già la 4-5° volta in 4 giorni che mi da BLUE SCREEN errore driver_not_or_less_equal ho W7 ultimate e pc in firma, HD cvontrollato con HDtune ma nessun problema...che può essere!!?:muro:
PS la scheda video è la stessa del mio vecchio PC con windows XP la nVIDIA 9800gt
Per iniziare prova a controllare se il problema sia HW o SW, vai in msconfig scheda avvio e deselezioni tutti i processi non necessari, proverei a disattivare anche AVG. Poi nella scheda servizi seleziona la casella nascondi tutti i servizi MS e disabiliti tutti gli altri, riavvia il pc e vedi se continuano le bsod.
Per l'HW inizierei testando la ram
mi spiegate che significa??ho provato ad eseguire la procedura descritta in prima pagina ma non ci capisco molto,qualcuno mi dà una mano???
http://img715.imageshack.us/img715/497/fotoxq.th.jpg (http://img715.imageshack.us/i/fotoxq.jpg/)
Uploaded with ImageShack.us (http://imageshack.us)
mi compare almeno 3/4 volte al giorno questa schermata,che devo fare??
formatto tutto?
mi consigliate il 7 al posto di vista????
mi compare almeno 3/4 volte al giorno questa schermata,che devo fare??
formatto tutto?
mi consigliate il 7 al posto di vista????
Prima di formattare controlla l'HW ad iniziare dalla ram
Prima di formattare controlla l'HW ad iniziare dalla ram
devo fare dei test???con cosa??sono totalmente ignorante su queste cose!!
è da un po che sto facendo il test alla ram ma non mi segnala nessun errore,che devo fare ora???
il test della ram deve durare parecchio almeno alcune ore e comunque potresti anche provare a scollegare direttamente un banco ala volta per maggior sicurezza del test
MatteoBirel
21-01-2011, 15:49
test RAM fatto e mi da qualche errorino...le ram sono nuove però o.0
Potrebbe essere proprio quello però :asd:
MatteoBirel
21-01-2011, 18:46
AZZ...E NON UN PROBLEMA Scheda video con la madre o i driver invidia.???molto male!vabbè sono in warranty XD
MatteoBirel
24-01-2011, 06:58
:muro:
Dopo 48 ore il PC si è riavviato con un BSOD.
Il registro eventi riporta l'errore al file ntoskrnl.exe
In allegato il file dmp: http://www.megaupload.com/?d=5NBDKFZ
inoltre allego il report di bluescrenview:
Dopo 48 ore il PC si è riavviato con un BSOD.
Il registro eventi riporta l'errore al file ntoskrnl.exe
In allegato il file dmp: http://www.megaupload.com/?d=5NBDKFZ
inoltre allego il report di bluescrenview:
C'è anche il problema con PSHED.dll, potrebbe indicare un problema coi driver, video in particolare.
Prova ad eliminare tutti i timer nelle opzioni risparmio energia, prestazioni elevate, disattivazione schermo, HD ecc tutto su mai, insomma avrai capito
C'è anche il problema con PSHED.dll, potrebbe indicare un problema coi driver, video in particolare.
Prova ad eliminare tutti i timer nelle opzioni risparmio energia, prestazioni elevate, disattivazione schermo, HD ecc tutto su mai, insomma avrai capito
A volte invece del BSOD, trovo il pc acceso, il disco in funzione, ma schermata nera: nessun segnale in ingresso nel monitor.
Potrebbe essere la scheda video, in particolare le temp, visto che con BOINC in full, arriva a 91°
Su risparmio energia PCIe (GTX-470 avevo già settato su "disattivato" proprio per il problema relativo a nessun segnale ;)
Quella temperatura è assolutamente abnorme
Quella temperatura è assolutamente abnorme
Dici?
nel thread apposito mi hanno confemrato che a 90° è ancora buona, se supera i 95° comincia a fare le bizze.
Può darsi che abbiano ragione, non conosco i dati tecnici precisi della tua scheda, ma a me sembra altina :asd:
Walter83666
27-01-2011, 18:54
Per rimanere in tema non è che qualcuno ha qualcosa da consigliarmi per il mio caso specifico che trovate qui? (http://www.hwupgrade.it/forum/showthread.php?p=34300863#post34300863)
Grazie;)
Serve il file dmp, per quello ti avevo indicato la guida alla prima pagine del thread
Walter83666
28-01-2011, 16:18
OK ti ringrazio, era per raccogliere pareri in attesa di poter mettere le mani sul pc in questione (che non ho a casa mia) e seguire la procedura. Un mio amico per esempio giusto ieri mi ha consigliato di cancellare i files temporanei di internet e i cookies visto che il problema sembra manifestarsi con applicativi internet... visto mai trattasi di un malware o similare.:) Dite che è inutile? Comunque appena ho il dmp posto!
ragazzi ho il problema BSOD, sulla schermata blù ho letto in fondo ndis.sys, e stavo giocando online.:confused: ho fatto una prova con prime95 e subito BSOD, ho abbassato l'oc di 100mhz del cpu niente crash, sarà colpa dell'oc a questo punto?
Quel problema è collegato sempre con la scheda di rete, aggiorna i driver
Quel problema è collegato sempre con la scheda di rete, aggiorna i driver
ho la chiavetta, e non cè driver di aggiornamento per questa E1800. quelli della scheda realtek di rete sono aggiornati.:mbe: ma anche la cpu deve reggere prime95 per essere stabile no'?
frankie1963
29-01-2011, 18:03
Ciao amici,ho letto i vari post,siccome anch'io ho avuto per ben 3 volte schermo blu e pc impallato ma ho dercato dentro la cartella C:\Windows\Minidump\ ma nel suointerno non cè nulla come mai ? (l'opzione cartella è messa su visualizza anche file nascosti) per adesso ho fatto un poco di pulizia sull' HD e sembra andare bene,anche se quando meno te lo aspetti eccolo li che ri-succede
grazie
Ciao amici,ho letto i vari post,siccome anch'io ho avuto per ben 3 volte schermo blu e pc impallato ma ho dercato dentro la cartella C:\Windows\Minidump\ ma nel suo interno non cè nulla come mai ? (l'opzione cartella è messa su visualizza anche file nascosti)
Non è un file nascosto, devi impostare il sistema per salvare il file nelle proprietà del PC>impostazioni avanzate>avvio e ripristino.
http://www.hwupgrade.it/forum/showthread.php?t=1955371
frankie1963
30-01-2011, 10:43
Non è un file nascosto, devi impostare il sistema per salvare il file nelle proprietà del PC>impostazioni avanzate>avvio e ripristino.
http://www.hwupgrade.it/forum/showthread.php?t=1955371
Ok, Grazie per aver risposto,il mio è cosi' ,come dovrei settarlo?
PS: ho windows seven professional 64 bit
http://img248.imageshack.us/img248/9296/impostazioniripristino.jpg
jacoscar
30-01-2011, 12:46
grazie, ma non capisco... sono già aggiornati! :confused:
poi dopo un'ora mi ha dato quest'altro errore :muro:
010911-38906-01.dmp 09/01/2011 18:11:54 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`031f8477 hal.dll hal.dll+2477 x64 C:\Windows\Minidump\010911-38906-01.dmp 2 15 7600
Ricordo che il problema più frequente è questo
012911-74490-01.dmp 29/01/2011 21:02:55 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000030 00000000`00000002 00000000`00000000 fffff880`059d4394 NETw5s64.sys NETw5s64.sys+1b4394 x64 C:\Windows\Minidump\012911-74490-01.dmp 2 15 7600
Come mi avete detto ho controllato i driver della scheda wireless ma ho già i più aggiornati disponibili sul sito acer
Ok, Grazie per aver risposto,il mio è cosi' ,come dovrei settarlo?
PS: ho windows seven professional 64 bit
Per iniziare devi deselezionare la casella riavvia automaticamente
Walter83666
30-01-2011, 20:13
Scusate ma dal link in prima pag per prendere Windows Debugging Tools sono riuscito a scaricare solo un file che si chiama winsdk_web.exe ma pesa meno di mezzo mega... mi sa che sbaglio qualcosa.
Ok invece per i symbols (WindowsVista.6002.090410-1830.amd64chk.Symbols.exe) che mi dovrebbe aver installato regolarmente.
Ovviamente se provo ad eseguire la voce "windbg" mi da errore... :muro:
Quel problema è collegato sempre con la scheda di rete, aggiorna i driver
per ora niente bsod, dal 28/1, spero sia statol'oc in particolare, grazie comuncque.
frankie1963
31-01-2011, 10:57
Per iniziare devi deselezionare la casella riavvia automaticamente
ok tutto qui e basta? adesso devo aspettare che il fenomeno si ripeta cosi trovo la cartella menzionata prima?
grazie
ok tutto qui e basta? adesso devo aspettare che il fenomeno si ripeta cosi trovo la cartella menzionata prima?
grazie
Esatto. Ma hai letto la guida?
frankie1963
31-01-2011, 15:45
Esatto. Ma hai letto la guida?
scusa a quale guida ti riferisci? alla prima pagina? si si ho letto ma avendo impostato la spunta su riavvio automatico non ho nessun file salvato quindi aspetto la prossima schermata blu,spero mai e dopo scarico i vari programmi,ma forse è uno solo
grazie
quindi aspetto la prossima schermata blu
:eekk: :eekk: :D :p
vBulletin® v3.6.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.