|
|||||||
|
|
|
 |
|
|
Strumenti |
06-05-2010, 11:35
|
#1 |
|
Senior Member
Iscritto dal: Feb 2005
Città: Enna Sicilia
Messaggi: 456
|
Se non risolvo niente patatina :( Schermata blu
Ciao ragà, mi trovo in una gran brutta situazione, o risolvo il problema o la mia ragazza non mi da più la patatina.
E' da un pò di tempo che ha diverse schermate blu Codice:
CLASSPNP.SYS PAGE_FAULT_IN_NONPAGED_AREA STOP: 0x00000050 (0xFFFFFFE0, 0x00000001, 0xF7660F8A, 0x00000000) IRQL_NOT_LESS_OR_EQUAL STOP: 0x0000000A (0x00000004, 0x00000002, 0x00000001, 0x804FDB10) IRQL_NOT_LESS_OR_EQUAL STOP: 0x0000000A (0x00000000, 0x00000002, 0x00000001, 0x8051EE76) STOP: 0x0000007E (0xC0000005, 0x80622B1F, 0xF430BAC4, 0xF430B7C0) STOP: 0x0000007E (0xC0000005,0x8062A789, 0xF7A2B468, 0xF7A2B164) win32k.sys PAGE_FAULT_IN_NONPAGED_AREA STOP: 0x00000050 (0xF0008014, 0x00000000, 0xBF8495F8, 0x00000000) DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP: 0x000000D1 (0x00000000, 0x00000002, 0x00000000, 0xF3B91613) LF30XP.sys Ho testato le memorie con memtest e i test sono andati "pass" Ho formattato il PC, installato ultimo BIOS, ultimi driver. A volte questo PC si blocca proprio nella fase di POST. Non sembra esserci un comportamento tale che gli errori si ripetano ad un determinato evento, a come gli gira và. Quando inizia a dare la prima schermata blu, poi dopo un pò continua a darle, ma se spengo il PC per un pò di tempo, funziona per un pò. E poi di nuovo schermate blu. Ho installato il Debugging Tools e i Symbol, ma sinceramente non ci capisco nulla dei risultati che mi da: 1 FILE Dump Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\FILì\Desktop\Errore Martina\Dump\Mini050510-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Wed May 5 01:47:48.687 2010 (UTC + 2:00)
System Uptime: 0 days 0:02:11.265
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
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {0, 2, 1, 8051ee76}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+1ba5d )
Followup: MachineOwner
---------
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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8051ee76, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmProbeAndLockPages+433
8051ee76 ff08 dec dword ptr [eax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: iexplore.exe
LAST_CONTROL_TRANSFER: from 80511b21 to 8051ee76
STACK_TEXT:
f776f92c 80511b21 c0709530 00000000 00000000 nt!MmProbeAndLockPages+0x433
f776f944 8051341e e12a6008 c0709530 00000000 nt!MmCopyToCachedPage+0x578
f776f9bc 8051cb1c 00000000 e12a6008 c0709530 nt!FsRtlFastUnlockSingleExclusive+0x63
f776fa20 8054051c 00000001 e12a6008 00000000 nt!PpRemoveDeviceActionRequests+0xc6
f776fa38 8062c9ca badb0d00 000000d4 de3c1000 nt!RtlIpv6AddressToStringExW+0x2b
f776fa5c e2c58a58 00000001 00000000 00000023 nt!PopAllocateDevState+0x71
WARNING: Frame IP not in any known module. Following frames may be wrong.
f776fadc 805ba740 e29b4238 867bf800 e12a6000 0xe2c58a58
f776fc00 f42bea5d e29b4238 e12a6000 00002000 nt!`string'+0x14
f776fc54 f42beb5b 805447e6 e2cbb468 00000000 klif+0x1ba5d
f776fc80 f42bece3 f776fcb0 e29b4238 00000000 klif+0x1bb5b
f776fcf8 f42c26d6 00000009 f776fd2c 00000000 klif+0x1bce3
f776fd50 8053d638 0017b294 00020019 022ef328 klif+0x1f6d6
f776fd64 7c91e4f4 badb0d00 022ef310 00000000 nt!PopPresentNotify+0x66
f776fd74 00000000 00000000 00000000 00000000 0x7c91e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
klif+1ba5d
f42bea5d ?? ???
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: klif+1ba5d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: klif
IMAGE_NAME: klif.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4afabcc5
FAILURE_BUCKET_ID: 0xA_klif+1ba5d
BUCKET_ID: 0xA_klif+1ba5d
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\FILì\Desktop\Errore Martina\Dump\Mini050510-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Wed May 5 01:51:45.609 2010 (UTC + 2:00)
System Uptime: 0 days 0:01:26.203
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
............
Unable to load image LF30XP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for LF30XP.sys
*** ERROR: Module load completed but symbols could not be loaded for LF30XP.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {0, 2, 0, f3b91613}
*** WARNING: Unable to verify timestamp for fltMgr.sys
Unable to load image klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : LF30XP.sys ( LF30XP+9613 )
Followup: MachineOwner
---------
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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f3b91613, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
LF30XP+9613
f3b91613 668b10 mov dx,word ptr [eax]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: avp.exe
LOCK_ADDRESS: 805591e0 -- (!locks 805591e0)
Resource @ nt!PiEngineLock (0x805591e0) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0x805591e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from f3b91828 to f3b91613
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b8703714 f3b91828 85bd31e0 85bd7252 b8703744 LF30XP+0x9613
b8703724 f3b9412b 85bd3284 b8703798 00000001 LF30XP+0x9828
b8703744 f3b8f11f b8703798 f3b91802 00000001 LF30XP+0xc12b
b870375c f3b9457e b8703798 b87037a4 00000001 LF30XP+0x711f
b8703784 f3b913a4 b8703798 b87037a4 00000001 LF30XP+0xc57e
b870379c f3b91af7 00000000 85bd30f0 f3b9772c LF30XP+0x93a4
b87037b8 f3b8dd51 85bd7252 85bd725e 85bd30f0 LF30XP+0x9af7
b87037d0 f3b8d9c4 85bd7252 b8703880 00000000 LF30XP+0x5d51
b87037ec f3b8daa0 0000005c 85bd7252 b8703808 LF30XP+0x59c4
b8703800 f3b8b27d 85bd7250 b870382c b8703828 LF30XP+0x5aa0
b870383c f3b8e2ce 85bd7250 00000970 b8703870 LF30XP+0x327d
b870388c f3b8e807 85bd7250 8551ae00 00120089 LF30XP+0x62ce
b87038bc f3b8eac7 859cdda0 8551afb4 85bd3598 LF30XP+0x6807
b87038e0 f3b911a3 00000000 86771020 8551ae00 LF30XP+0x6ac7
b8703914 f3b94289 86771020 85bd3628 85bd3c08 LF30XP+0x91a3
b8703930 804ee119 86771020 8551ae00 86761380 LF30XP+0xc289
b870398c 804ee119 86770bf0 8551ae00 8551ae00 nt!CcAcquireByteRangeForWrite+0x56c
b87039c0 f7463754 b87039e0 8654e020 00000000 nt!CcAcquireByteRangeForWrite+0x56c
b87039fc 804ee119 8654e020 8551ae00 8551ae00 fltMgr!FltpCreate+0x26a
b8703aec 805b4cbc 8677b900 00000000 855ffd68 nt!CcAcquireByteRangeForWrite+0x56c
b8703b74 805b1065 00000000 b8703bb4 00000040 nt!PipMakeGloballyUniqueId+0x38d
b8703bc8 8056b223 00000000 00000000 5627db01 nt!NtQueryVirtualMemory+0x3a8
b8703c44 8056bb9a 02bcf3dc 80100080 02bcf37c nt!CcPreparePinWrite+0x26
b8703ca0 8056e2ac 02bcf3dc 80100080 02bcf37c nt!NtQueryInformationThread+0x20d
b8703ce0 f42c42ae 02bcf3dc 80100080 02bcf37c nt!NtQueryVirtualMemory+0x181
b8703d30 8053d638 02bcf3dc 80100080 02bcf37c klif+0x212ae
b8703d64 7c91e4f4 badb0d00 02bcf344 00000000 nt!PopPresentNotify+0x66
b8703d74 00000000 00000000 00000000 00000000 0x7c91e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
LF30XP+9613
f3b91613 668b10 mov dx,word ptr [eax]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: LF30XP+9613
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: LF30XP
IMAGE_NAME: LF30XP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a76b0ee
FAILURE_BUCKET_ID: 0xD1_LF30XP+9613
BUCKET_ID: 0xD1_LF30XP+9613
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\FILì\Desktop\Errore Martina\Dump\Mini050510-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Wed May 5 13:40:51.937 2010 (UTC + 2:00)
System Uptime: 0 days 2:12:30.533
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
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, a030001, f7a3fcb0, f7a3f9ac}
Probably caused by : ntoskrnl.exe ( nt!KeOptimizeProcessorControlState+9 )
Followup: MachineOwner
---------
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: 0a030001, The address that the exception occurred at
Arg3: f7a3fcb0, Exception Record Address
Arg4: f7a3f9ac, Context Record Address
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:
+80
0a030001 ?? ???
EXCEPTION_RECORD: f7a3fcb0 -- (.exr 0xfffffffff7a3fcb0)
ExceptionAddress: 0a030001
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 0a030001
Attempt to execute non-executable address 0a030001
CONTEXT: f7a3f9ac -- (.cxr 0xfffffffff7a3f9ac)
eax=0a030001 ebx=867c5b30 ecx=71576343 edx=80010031 esi=8055b0c0 edi=867fc020
eip=0a030001 esp=f7a3fd78 ebp=f7a3fdac iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
0a030001 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".
EXCEPTION_PARAMETER1: 00000008
EXCEPTION_PARAMETER2: 0a030001
WRITE_ADDRESS: 0a030001
FOLLOWUP_IP:
nt!KeOptimizeProcessorControlState+9
80534c02 ?? ???
FAILED_INSTRUCTION_ADDRESS:
+2502faf00fadfc0
0a030001 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 80534c02 to 0a030001
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a3fd74 80534c02 71576343 00000000 867c5b30 0xa030001
f7a3fdac 805c615f 71576343 00000000 00000000 nt!KeOptimizeProcessorControlState+0x9
f7a3fddc 80541dd2 80534b02 00000000 00000000 nt!ArbSortArbitrationList+0x6
f7a3fdf0 00000000 00000000 00000000 00000000 nt!RtlpTraceDatabaseInternalAdd+0x80
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeOptimizeProcessorControlState+9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
STACK_COMMAND: .cxr 0xfffffffff7a3f9ac ; kb
FAILURE_BUCKET_ID: 0x7E_BAD_IP_nt!KeOptimizeProcessorControlState+9
BUCKET_ID: 0x7E_BAD_IP_nt!KeOptimizeProcessorControlState+9
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\FILì\Desktop\Errore Martina\Dump\Mini050510-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
Debug session time: Wed May 5 13:42:20.687 2010 (UTC + 2:00)
System Uptime: 0 days 0:00:55.281
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 1000000A, {4, 2, 1, 804fdb10}
Probably caused by : memory_corruption ( nt!MmDeleteProcessAddressSpace+e3 )
Followup: MachineOwner
---------
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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 804fdb10, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000004
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmDeleteProcessAddressSpace+e3
804fdb10 894104 mov dword ptr [ecx+4],eax
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: avp.exe
LAST_CONTROL_TRANSFER: from 806d3c35 to 804fdb10
STACK_TEXT:
b816dc10 806d3c35 00000000 00000000 b816dc28 nt!MmDeleteProcessAddressSpace+0xe3
b816dc28 806d38eb badb0d00 e32ed928 80575c2e hal!IoFreeAdapterChannel+0xcf
b816dcb4 8056e191 00000c94 00000002 00000000 hal!HalpCopyBufferMap+0xc7
b816dd48 8053d638 00000c94 056cfee8 056cfec8 nt!NtOpenProcessTokenEx+0xbb
b816dd64 7c91e4f4 badb0d00 056cfe8c 0070fd84 nt!PopPresentNotify+0x66
WARNING: Frame IP not in any known module. Following frames may be wrong.
b816dd74 00000000 00000000 00000000 00000000 0x7c91e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmDeleteProcessAddressSpace+e3
804fdb10 894104 mov dword ptr [ecx+4],eax
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MmDeleteProcessAddressSpace+e3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MmDeleteProcessAddressSpace+e3
BUCKET_ID: 0xA_nt!MmDeleteProcessAddressSpace+e3
Followup: MachineOwner
---------
Codice:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\FILì\Desktop\Errore Martina\Dump\Mini050510-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Wed May 5 14:26:23.656 2010 (UTC + 2:00)
System Uptime: 0 days 0:22:53.162
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
...................................
Loading User Symbols
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {f0008014, 0, bf8495f8, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!vSpOrderInY+72 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f0008014, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf8495f8, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: f0008014
FAULTING_IP:
win32k!vSpOrderInY+72
bf8495f8 39712c cmp dword ptr [ecx+2Ch],esi
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
LAST_CONTROL_TRANSFER: from bf827c44 to bf8495f8
STACK_TEXT:
f7ad2860 bf827c44 e22316a0 00000000 e22316a0 win32k!vSpOrderInY+0x72
f7ad2928 bf938b78 e173c048 0000001f 0000001b win32k!bSpUpdatePosition+0x3af
f7ad2958 bf938d2c e1738768 00000197 00000186 win32k!EngMovePointer+0x140
f7ad298c bf84ac9b e1738768 00000000 e1d8f010 win32k!EngSetPointerShape+0x172
f7ad2a24 bf84a72f e173c008 e181be80 00000000 win32k!vSetPointer+0x3e3
f7ad2a50 bf800e12 85fd1328 e15827c8 00000010 win32k!GreSetPointer+0x66
f7ad2a7c bf8244d6 0014f3e4 e22b55f0 00000000 win32k!zzzUpdateCursorImage+0x1a1
f7ad2a8c bf885a67 804dcbe4 00000001 00000000 win32k!zzzSetFMouseMoved+0xd5
f7ad2ad4 bf89fd38 00000022 0070fff4 bf8010e7 win32k!ProcessQueuedMouseEvents+0x1c8
f7ad2d30 bf884705 f7ac2490 00000002 f7ad2d54 win32k!RawInputThread+0x5b9
f7ad2d40 bf80110a f7ac2490 f7ad2d64 0070fff4 win32k!xxxCreateSystemThreads+0x60
f7ad2d54 804de7ec 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f7ad2d54 7c91e4f4 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c91e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!vSpOrderInY+72
bf8495f8 39712c cmp dword ptr [ecx+2Ch],esi
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!vSpOrderInY+72
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
FAILURE_BUCKET_ID: 0x50_win32k!vSpOrderInY+72
BUCKET_ID: 0x50_win32k!vSpOrderInY+72
Followup: MachineOwner
---------
La RAM sembra apposto Avevo provato ad utilizzare un programma della Maxtor per testare il mio HD Maxtor, e sembrava anche li apposto. Bu Scheda madre? o boh non so vero cosa pensare, anche se sinceramente mi e sembrato di capire che l'hard disk forse gira male, cioè quandi si riavvia sente ripetutamente un "tic tic" che dovrebbe essere l hd. HELP RAGA, O NON POSSO PIU' TRAMANDARE IL MIO COGNOME Grazie mille 
__________________
Mercatino: Utenti OK: Kaiser76, Bobosassa, veltosaar;  problemi con lellosplendor, si è aggiudicato un PC, ma non lo ha pagato Compaq miniPC
|
|
|
|
06-05-2010, 12:54
|
#2 |
|
Senior Member
Iscritto dal: Feb 2002
Messaggi: 808
|
scusa ma se ti aiutiamo noi del forum poi va a finire che la tua ragazza la patatina la deve.....
 temperatura di cpu è apposto no ? Ultima modifica di Cristian81 : 06-05-2010 alle 12:58. |
|
|
|
|
06-05-2010, 22:09
|
#3 |
|
Senior Member
Iscritto dal: Feb 2009
Messaggi: 50674
|
Prova ad andare in Gestione periferiche e guarda se hai qualche punto esclamativo in giallo.
Prova anche ad aggiornare il Bios. Errore 0x00000050 o PAGE_FAULT_IN_NONPAGED_AREA Un driver o un servizio di sistema ha richiesto dati non presenti in memoria causando un errore di eccezione. Può essere causato da un software incompatibile, in particolare driver, antivirus o programmi di controllo remoto, l'errore può anche essere prodotto dalla memoria RAM difettosa Prova al limite anche a dare il comando sfc /scannow da start/esegui che prevede l'inserimanto del cd originale E digli alla tua lei, che si applichi di più
|
|
|
|
|
07-05-2010, 13:40
|
#4 | ||
|
Senior Member
Iscritto dal: Feb 2005
Città: Enna Sicilia
Messaggi: 456
|
Quote:
 La metti in bocca e inizi a rosolare a 100° in un bel pentolone mentre tengo il coperchio per cuocere meglio. Le temperature sono le seguenti e mi sembrano OK Scheda Madre: 45 °C (Asus A8V-E) Processore: 52 °C (AMD A64 3200) HD: 50° Poi le temperature dei diodi che non so cosa sono, ditemi voi: Diodo Processore: 62° Diodo GPU: 70° La GPU è una Nvidia 6600 o 6200 mi pare. Quote:
RAM difettosa non saprei, perchè ho fatto alcuni test con memtest e mi dava ok. Utilizzando il debugging tool che esamina i file dump, non è possibile capire se c'è qualche programma o servizio che rompre le palle? Grazie ciao
__________________
Mercatino: Utenti OK: Kaiser76, Bobosassa, veltosaar; problemi con lellosplendor, si è aggiudicato un PC, ma non lo ha pagato Compaq miniPC
|
||
|
|
|
|
07-05-2010, 13:51
|
#5 | ||
|
Senior Member
Iscritto dal: Feb 2002
Messaggi: 808
|
Quote:
Quote:
senti la tua scheda video è agp, pci express cosa ? |
||
|
|
|
|
07-05-2010, 18:17
|
#6 | |
|
Senior Member
Iscritto dal: Feb 2005
Città: Enna Sicilia
Messaggi: 456
|
Quote:
Ma dall analisi dei dump niente si può capire?
__________________
Mercatino: Utenti OK: Kaiser76, Bobosassa, veltosaar; problemi con lellosplendor, si è aggiudicato un PC, ma non lo ha pagato Compaq miniPC
|
|
|
|
|
|
07-05-2010, 19:57
|
#7 |
|
Senior Member
Iscritto dal: Feb 2002
Messaggi: 808
|
ah non ti saprei dire, scheda video sempre quella ? hai fatto qlc cambiamento poco prima che ti desse problemi ?
|
|
|
|
|
07-05-2010, 20:14
|
#8 |
|
Senior Member
Iscritto dal: Aug 2003
Messaggi: 9650
|
io opererei così:
 Ritesterei la ram con Windiag (test completo) http://oca.microsoft.com/en/windiag.asp Test dell'hard disk con le utility che il produttore mette a disposizione Controllo visivo della scheda madre se ci sono condensatori gonfi o aperti provare con un alimentatore diverso certi della sua affidabilità controllo temperature |
|
|
|
|
07-05-2010, 20:38
|
#9 |
|
Senior Member
Iscritto dal: Feb 2002
Messaggi: 808
|
mi sà che ci puoi dire ciao alla patatina
 molto presto conoscerai federica
|
|
|
|
|
07-05-2010, 22:23
|
#10 | |||
|
Senior Member
Iscritto dal: Feb 2005
Città: Enna Sicilia
Messaggi: 456
|
Quote:
Quote:
Con memtest le memorie erano ok proverò con questo microsoft Visivamente dovrò guardarla la MB Pensi che un alimentatore possa dare questi problemi? Magari provo con un tester e vedere se è tutto ok, anche se cmq penso che dovrei testarlo a carico non a vuoto, e come fò? Le temperature mi sembrano nella norma 45 Mb e 52 il processore. Invece cosa sono sti diodi, di cui ho la temperatura? Le odio troppo ste schermate blu, il problema è che a volte si verificano ad ogni accensione del PC, a volte sta per un bel pò di tempo senza problemi mah.. Non so se è una coincidenza: Quando capitavano le schermate blu e dovevo spegnere da power, queste schermate continuavano a comparire, se invece spengo il PC normalmente da "Start Chiudi sessione" ste schermate non si fanno vedere. Mah Esiste un programma per testare il Processore? Non si può trattare di errori di memoria cache? Ma che poi dico io a che serve sto Debugging tool? Quote:
Comunque grazie tante raga secondo me non ne verro mai a capo. Se avete altri suggerimeti ditemi. Vi invito al battesimo di mio figlio
__________________
Mercatino: Utenti OK: Kaiser76, Bobosassa, veltosaar; problemi con lellosplendor, si è aggiudicato un PC, ma non lo ha pagato Compaq miniPC
|
|||
|
|
|
|
07-05-2010, 23:27
|
#11 |
|
Senior Member
Iscritto dal: Feb 2002
Messaggi: 808
|
avevo fatto una ricercuzza, niente di imputabile, ma erano utenti che avevano cambiato la scheda video.
|
|
|
|
|
08-05-2010, 14:51
|
#12 | |
|
Senior Member
Iscritto dal: Feb 2005
Città: Enna Sicilia
Messaggi: 456
|
Quote:
__________________
Mercatino: Utenti OK: Kaiser76, Bobosassa, veltosaar; problemi con lellosplendor, si è aggiudicato un PC, ma non lo ha pagato Compaq miniPC
|
|
|
|
|
|
08-05-2010, 19:17
|
#13 | |
|
Senior Member
Iscritto dal: Feb 2009
Messaggi: 50674
|
Quote:
Magari risolvi anche se hai detto che il problema non sembra imputabile al software. O uno scandisk andando in prompt di dos e digitando chkdsk C: /f /r Ahhh queste patatine come ti fanno sudare freddo ehh  La sapevate: dicono che tiri più un pelo di ........che 100 tori Vero eh
|
|
|
|
|
|
08-05-2010, 19:18
|
#14 |
|
Senior Member
Iscritto dal: Dec 2008
Messaggi: 361
|
ma non aveva appena formattato e reinstallato
|
|
|
|
|
08-05-2010, 19:27
|
#15 | |
|
Senior Member
Iscritto dal: Feb 2009
Messaggi: 50674
|
Quote:
Ha testato l' HD e gli dice che è tutto ok....... Magari andare nel Visualizzatore Eventi digitando eventvwr per vedere se gli dice di più. Alle voci Applicazione e Sistema, dovrebbe guardare negli errori, e per sapere qualcosa di più sull'errore stesso cliccare due volte col mouse . Importanti sono L'ID evento e l'origine. Io andrei a vedere anche in Gestione periferiche se mi dice qualcosa, tipo punti esclamativi gialli. |
|
|
|
|
|
10-05-2010, 13:23
|
#16 | |
|
Senior Member
Iscritto dal: Feb 2005
Città: Enna Sicilia
Messaggi: 456
|
Quote:
siamo schiavi
__________________
Mercatino: Utenti OK: Kaiser76, Bobosassa, veltosaar; problemi con lellosplendor, si è aggiudicato un PC, ma non lo ha pagato Compaq miniPC
|
|
|
|
|
|
10-05-2010, 14:08
|
#17 |
|
Senior Member
Iscritto dal: Dec 2008
Messaggi: 361
|
ci sono quelli a cui fà puzza
|
|
|
|
|
10-05-2010, 14:16
|
#18 | |
|
Senior Member
Iscritto dal: Feb 2005
Città: Enna Sicilia
Messaggi: 456
|
Quote:
__________________
Mercatino: Utenti OK: Kaiser76, Bobosassa, veltosaar; problemi con lellosplendor, si è aggiudicato un PC, ma non lo ha pagato Compaq miniPC
|
|
|
|
|
|
10-05-2010, 14:23
|
#19 |
|
Senior Member
Iscritto dal: Dec 2008
Messaggi: 361
|
e se li tolgono quando stanno con il rago
|
|
|
|
|
11-05-2010, 14:38
|
#20 |
|
Senior Member
Iscritto dal: Feb 2009
Messaggi: 50674
|
Raga vediamo di tenere un certo contegno
 non andiamo fuori dal discorso ........Non avessi fatto la battuta .......che è realtà, comunque Mr. Filter invece di fare lo spiritaus, se non altro già dal titolo della discussione stessa , hai combinato qualcosa, andiamo alle calende greche, come siamo ?Perchè qui mi sa altro che no pata, no party , peggio......
Ultima modifica di tallines : 11-05-2010 alle 14:40. |
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 04:05.
