Windows dump

[[giBo]]

Originariamente inviato da [giBo]

Di conseguenza alle righe impostate precedentemente,

Intendevo postate!...nel post di qualche giorno fa..

[Dott.Wisem]

Si direbbe che il tuo computer sia andato in crash per via di un componente dell'Outpost Firewall (FILTNT.SYS) che è andato in conflitto con qualcos'altro... Forse con l'antivirus. Disinstalla quel firewall e vedrai che il computer non andrà più in crash.

[[giBo]]

grazie mille....allora per questo computer tutto ok....devi sapere che ho un altro computer (fisso) che mi causa problemi ben piu gravi...( in pratica va in crash 2 volte ogni volta che lo uso, in media!!!!!!!!!! ) ora che ho un po ho capito un po come scoprire il problema vedrò di sistemarlo.... in caso ricorrerò al tuo immenso aiuto...grazie

[Carra86]

Originariamente inviato da [giBo]

ciao a tutti..
chi mi dice come posso aprire dei file .dmp?
Il problema è questo: il computer mi si riavvia inspiegabilmente da solo, il bravo windows mi segnala che c'è stato un errore grave e mi chiede se voglio inviare la segnalazione (il file dmp).
Io vorrei aprirlo per cercare di vedere quali sono i programmi o le periferiche che mi causano i problemi....ho cercato sulla guida online di windows, e ho scaricato un pacchetto con un programma chiamato dumpcheck, con il quale però, non sono riuscito ad aprire i miei file .dmp....mi fa una schermata veloce e poi niente..
c'è un modo più facile per aprire sti benedetti file?

anch'io ho il tuo stesso problema! però dall'output del debugger non capisco quale sia il problema...anche se presumo che ci sia qualche problema di simboli ecc

Probably caused by : torususb.sys ( torususb+5e1a )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* 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: c0000005, The exception code that was not handled
Arg2: a8bb3e1a, The address that the exception occurred at
Arg3: f7936af4, Exception Record Address
Arg4: f79367f0, Context Record Address

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** 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 ***
*** ***
*************************************************************************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3e8ae49a

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferi
mento alla memoria a "0x%08lx". La memoria non poteva essere "%s".

FAULTING_IP:
torususb+5e1a
a8bb3e1a 668b4104 mov ax,word ptr [ecx+4]

EXCEPTION_RECORD: f7936af4 -- (.exr fffffffff7936af4)
ExceptionAddress: a8bb3e1a (torususb+0x00005e1a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000004
Attempt to read from address 00000004

CONTEXT: f79367f0 -- (.cxr fffffffff79367f0)
eax=894f62d0 ebx=00000000 ecx=00000000 edx=00000000 esi=894f62d4 edi=89216b18
eip=a8bb3e1a esp=f7936bbc ebp=f7936bd8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
torususb+0x5e1a:
a8bb3e1a 668b4104 mov ax,word ptr [ecx+4] ds:0023:00000004=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from a8bb577f to a8bb3e1a

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7936bd8 a8bb577f 8956bcc4 891dcaa8 00000001 torususb+0x5e1a
f7936bf8 a8be58a1 8956bcc4 00000001 00000005 torususb+0x777f
f7936c30 a8c01352 891daa4c a8c01370 00000005 torususb+0x378a1
f7936c4c a8c01200 891e112e 00000001 891daa4c torususb+0x53352
f7936c68 a8be9e1d 891e112e 891e1101 00000000 torususb+0x53200
f7936c84 a8be9b36 891e112e 00000001 891e10c8 torususb+0x3be1d
f7936c98 a8c0021f 891e10c8 f7936cbc a8be9d67 torususb+0x3bb36
f7936ca4 a8be9d67 00000000 891e10c8 891e1128 torususb+0x5221f
f7936cbc a8bc63ff f7936ccc 891d935c f7934ff3 torususb+0x3bd67
f7936cd0 a8c03cca 00000000 8965d380 f7936d04 torususb+0x183ff
f7936ce0 a8c0bf16 00000000 00000000 f7936d68 torususb+0x55cca
f7936d04 a8bfe861 00000000 00000000 00000000 torususb+0x5df16
f7936d78 a8bfe5c2 89430488 f7936da8 a8bb4d3d torususb+0x50861
f7936d84 a8bb4d3d 89430488 00000000 00000000 torususb+0x505c2
f7936da8 a8bb6b90 80574128 8931c28c 00000000 torususb+0x6d3d
f7936ddc 804efc81 a8bb6b84 8931c28c 00000000 torususb+0x8b90
00000000 00000000 00000000 00000000 00000000 nt+0x18c81


FOLLOWUP_IP:
torususb+5e1a
a8bb3e1a 668b4104 mov ax,word ptr [ecx+4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: torususb+5e1a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: torususb

IMAGE_NAME: torususb.sys

STACK_COMMAND: .cxr 0xfffffffff79367f0 ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

qualcuno capisce quale potrebbe essere il problema??

ormai ne ho fin sopra ai capelli...grassie a tutti

[Khronos]

dove risiede questo file
torususb.sys? ^^

[Carra86]

Originariamente inviato da Khronos

dove risiede questo file
torususb.sys? ^^

azz...praticamente risiede nella cartella dove ho installato i driver del modem usb e nella cartella

c:\windows\system32\drivers

quindi la causa di tutto sta nel modem!! giusto?

[webmagic]

Richiedo una visione della mia analisi.. grazie...

CURRENT_IRQL:  2

FAULTING_IP: 
+ffffffff865527b5
865527b5 8b4204          mov     eax,dword ptr [edx+4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from 00000000 to 865527b5

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: fffffffff79fbdac

STACK_COMMAND:  dds F79FBDAC-0x20 ; kb

STACK_TEXT:  
f79fbd8c  00000061
f79fbd90  00000061
f79fbd94  855ea0e7
f79fbd98  00000000
f79fbd9c  855ea008
f79fbda0  85021000
f79fbda4  f79fbe34
f79fbda8  f3fa94e9 rt2500usb+0x84e9
f79fbdac  86157150
f79fbdb0  85831000
f79fbdb4  f79fbde4
f79fbdb8  f79fbde4
f79fbdbc  0000000e
f79fbdc0  8580b030
f79fbdc4  00000061
f79fbdc8  00000061
f79fbdcc  00000002
f79fbdd0  00000000
f79fbdd4  00000061
f79fbdd8  8580b028
f79fbddc  8641475c
f79fbde0  8583316c
f79fbde4  80011600
f79fbde8  1800c13d
f79fbdec  2fefdb39
f79fbdf0  86600008
f79fbdf4  85831000
f79fbdf8  85832308
f79fbdfc  00000000
f79fbe00  8580b018
f79fbe04  f6778129 USBPORT+0x8129
f79fbe08  00000000


FOLLOWUP_IP: 
rt2500usb+84e9
f3fa94e9 ??              ???

SYMBOL_NAME:  rt2500usb+84e9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rt2500usb

IMAGE_NAME:  rt2500usb.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------

Dovrebbe essere il file rt2500usb.sys ...
Ogni suggerimento è apprezzato!

[Khronos]

realtek?

[webmagic]

sembrerebbe sia la chiavetta wireless che ho.. ma è una AirStation Wireless-G .. probabilmente monta chipset Ralink Technology, non Realtek...

Consigli?

[net-gamer]

ad un mio amico crasha in continuazione il pc, mi ha passato il file .dmp e con windbg + i simboli l'ho aperto.

Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\WINDOWS\Minidump\minicrash.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: D:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805535a0
Debug session time: Sun Jun 24 16:22:03.344 2007 (GMT-7)
System Uptime: 1 days 12:15:45.125
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............................................
*** WARNING: Unable to verify timestamp for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {4, 805463f0, b2000000, 70f0f}

Probably caused by : ntoskrnl.exe ( nt!CcSetDirtyInMask+7b )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000004
Arg2: 805463f0
Arg3: b2000000
Arg4: 00070f0f

Debugging Details:
------------------

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
--------------------------
_VAL_UC_EN_PCC_BUSCONNERR_30F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_AuthenticAMD

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: eMule_AdnzA.exe

LAST_CONTROL_TRANSFER: from 806d48d7 to 804f8c3f

STACK_TEXT:
805463c8 806d48d7 0000009c 00000004 805463f0 nt!CcSetDirtyInMask+0x7b
805464f4 806cfc2e 80042000 00000000 00000000 hal!HalpGetFeatureBits+0x6d
00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xaa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CcSetDirtyInMask+7b
804f8c3f 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CcSetDirtyInMask+7b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e54849

FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_nt!CcSetDirtyInMask+7b

BUCKET_ID: 0x9C_AuthenticAMD_nt!CcSetDirtyInMask+7b

Followup: MachineOwner
---------

[astimas]

Che abbia colpe questo :

PROCESS_NAME: eMule_AdnzA.exe

?

Prova un'altra versione di Emule...

[angerosale1]

Ciao domani comincio un nuovo lavoro come tecnico informatico. Fino ad ora ho solo montatopc e installato reti. Parlando con l' ingegnere respnsabile mi ha detto che dovro cominciare facendo debug su alcuni computer che dovro' poi mettere in rete. CHE VUOL DIRE FARE DEBUG???????

VI PREGO AIUTATEMI CHE ANCORA DEVO FIRMARE IL CONTRATTO!!!!!!!!

[jstef]

Originariamente inviato da angerosale1

mi ha detto che dovro cominciare facendo debug su alcuni computer che dovro' poi mettere in rete.

? Tranquillo, secondo me non lo sa neanche lui.

[Dott.Wisem]

Originariamente inviato da angerosale1

Ciao domani comincio un nuovo lavoro come tecnico informatico. Fino ad ora ho solo montatopc e installato reti. Parlando con l' ingegnere respnsabile mi ha detto che dovro cominciare facendo debug su alcuni computer che dovro' poi mettere in rete. CHE VUOL DIRE FARE DEBUG???????

VI PREGO AIUTATEMI CHE ANCORA DEVO FIRMARE IL CONTRATTO!!!!!!!!

Significa molto semplicemente che devi testare il buon funzionamento dei computer in rete.

[billy99]

scusate come devo usare windbg??

vorrei aprire un file dump di uan schermata blu...

ma sono proprio un profano e vorrei trovare qualcuno che mi aiuti.. grazie a tutti.

[GT82]

Segnalo quest'ottima guida:

--> http://www.p2pforum.it/forum/showthread.php?t=244944

[ShadyA&B]

Salve ragazzi.

Dovrei aprire anche io il log di un crush dump per capire l'errore di un'applicazione.

Allora ho scaricato sia il programma di debug che i symbol, ho fatto partire il tutto ed ho analizzato il file.

Ecco il log risultato:

*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

***** OS 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
fm!jap_setup_comps+97662a
00e0ea6a 8b11 mov edx,dword ptr [ecx]

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00e0ea6a (fm!jap_setup_comps+0x0097662a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000

PROCESS_NAME: fm.exe

MODULE_NAME: fm

FAULTING_MODULE: 7c910000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP: 491c4c05

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000000

READ_ADDRESS: 00000000

FOLLOWUP_IP:
fm!jap_setup_comps+97662a
00e0ea6a 8b11 mov edx,dword ptr [ecx]

FAULTING_THREAD: 00000da8

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

PRIMARY_PROBLEM_CLASS: INVALID_POINTER_WRITE

BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_WRITE_WRONG_SYMBOLS_NULL_POINTER_WRITE

LAST_CONTROL_TRANSFER: from 01314426 to 00e0ea6a

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0012ecb0 01314426 233aed6c 233aed1c 26ea8e10 fm!jap_setup_comps+0x97662a
00000000 00000000 00000000 00000000 00000000 fm!wc_setup_comps+0x354256


STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: fm!jap_setup_comps+97662a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: fm.exe

BUCKET_ID: WRONG_SYMBOLS

WATSON_IBUCKET: 1013567357

WATSON_IBUCKETTABLE: 1

FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_fm.exe!base_address

Followup: MachineOwner

Potete aiutarmi a capire il problema?

[ShadyA&B]

Ho provato a fare ricerche da non esperto per conto mio, ma non ho trovato nessun hotfix di Windows per risolvere il problema, e non è neanche indicato come modalità nelle FAQ del supporto Microsoft.

Possibile che nessuno abbia idee?

[Prophet84]

Ragazzi da qualche settimana il mio pc da schermate blu, ho estratto il file dal dump, secondo voi che cosa è?
premetto che ho testato le ram con memtest86, fatto un paio di cicli di test, nessun problema è stato riscontrato.

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: bb1ffffc, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8207084c, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82172868
Unable to read MiSystemVaType memory at 82152420
bb1ffffc

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiIdentifyPfn+a29
8207084c 8b7918 mov edi,dword ptr [ecx+18h]

CUSTOMER_CRASH_COUNT: 12

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: svchost.exe

TRAP_FRAME: 95a187e4 -- (.trap 0xffffffff95a187e4)
ErrCode = 00000000
eax=01ffffff ebx=8481b4b0 ecx=bb1fffe4 edx=01ffffff esi=0000002b edi=01ffffff
eip=8207084c esp=95a18858 ebp=95a188b8 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!MiIdentifyPfn+0xa29:
8207084c 8b7918 mov edi,dword ptr [ecx+18h] ds:0023:bb1ffffc=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8207084c to 82095d24

STACK_TEXT:
95a187e4 8207084c badb0d00 01ffffff 00768036 nt!KiTrap0E+0x2ac
95a188b8 820cecbd 95a18864 0381b4b0 8481b000 nt!MiIdentifyPfn+0xa29
95a188ec 8224db79 6762330b 95a18978 00000006 nt!MmQueryPfnList+0x130
95a18930 82268c1a 00000001 6762339b 00000014 nt!PfpPfnPrioRequest+0xdc
95a189a0 82274199 00000000 00000001 95a18d30 nt!PfQuerySuperfetchInformation+0xea
95a18d4c 82092a1a 0000004f 01c5ede8 00000014 nt!NtQuerySystemInformation+0x2201
95a18d4c 772c9a94 0000004f 01c5ede8 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01c5edb4 00000000 00000000 00000000 00000000 0x772c9a94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiIdentifyPfn+a29
8207084c 8b7918 mov edi,dword ptr [ecx+18h]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiIdentifyPfn+a29

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49ac8fb4

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiIdentifyPfn+a29

BUCKET_ID: 0xA_nt!MiIdentifyPfn+a29

Followup: MachineOwner
---------

[wjmat]

http://www.hwupgrade.it/forum/showthread.php?t=1955647