Witam, tak jak w temacie.Tak co jakiś miesiąc czasu może krócej pojawia się przy starcie BSOD. Pojawiają się klasyczne świetliki, flaga Windows i BSOD. I tak co miesiąc.To jest już denerwujące. Pojawia się BSOD, 5 sekund i restart kompa.
Pozdrawiam Forumowiczów!
Wrzuć pliki z Minidumpa na jakiś serwer i daj nam link, przyjrzymy się im.
Pliki minidump dałem na przeklej.pl pierwszy bsod z lipca i ten z przed dwóch dni
LINK
hasło: minidump
Ja nie widzę tych załączników.
Używasz softu do łączenia z komórką ?
Sony Ericsson Mobile Communications, jeden z jego sterowników wywołuje błąd PAGE_FAULT_IN_NONPAGED_AREA (50) - ten sam w obu bsodach. Uruchom tryb awaryjny i wywal ten soft.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\minidumpy\081311-19125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x83244000 PsLoadedModuleList = 0x8338d4f0
Debug session time: Sat Aug 13 20: 09: 06.730 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 00: 13.057
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
3: 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: 9de59000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 94afd493, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Unable to load image \SystemRoot\system32\DRIVERS\seehcri.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for seehcri.sys
READ_ADDRESS: GetPointerFromAddress: unable to read from 833ad848
Unable to read MiSystemVaType memory at 8338ce40
9de59000
FAULTING_IP:
seehcri+493
94afd493 663906 cmp word ptr [esi],ax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: 8db8f8c4 -- (.trap 0xffffffff8db8f8c4)
ErrCode = 00000000
eax=00000000 ebx=86fa5668 ecx=7fffffff edx=7ffffffe esi=9de59000 edi=8db8f988
eip=94afd493 esp=8db8f938 ebp=8db8f944 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
seehcri+0x493:
94afd493 663906 cmp word ptr [esi],ax ds: 0023: 9de59000=?
Resetting default scope
LOCK_ADDRESS: 833aac00 -- (!locks 833aac00)
Resource @ nt!PiEngineLock (0x833aac00) 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 : 0x833aac00
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from 832853e8 to 832d23db
STACK_TEXT:
8db8f8ac 832853e8 00000000 9de59000 00000000 nt!MmAccessFault+0x106
8db8f8ac 94afd493 00000000 9de59000 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
8db8f944 94b007d5 9de58ffe 7fffffff 8db8f988 seehcri+0x493
8db8f998 8327b58e 870e7e78 00000000 8db8fa18 seehcri+0x37d5
8db8f9b0 8341cfcd c00000bb 8db8fa4c 00000000 nt!IofCallDriver+0x63
8db8f9e0 833f50a3 85a03d70 8db8fa4c 85a03bb8 nt!IopSynchronousCall+0xc2
8db8fa1c 833f5610 00000005 85a03bb8 00000000 nt!PnpIrpQueryID+0x3f
8db8fa9c 83400fa3 00000001 00000000 86f79540 nt!PipProcessStartPhase3+0x2f2
8db8fc94 833cce14 859aace8 86f79540 8db8fcc8 nt!PipProcessDevNodeTree+0x2e6
8db8fcd4 83258cfd 86f79540 833a8b20 859c68e0 nt!PiProcessStartSystemDevices+0x6d
8db8fd00 832c1a6b 00000000 00000000 859c68e0 nt!PnpDeviceActionWorker+0x241
8db8fd50 8344cfda 00000001 a9f25c89 00000000 nt!ExpWorkerThread+0x10d
8db8fd90 832f51d9 832c195e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
seehcri+493
94afd493 663906 cmp word ptr [esi],ax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: seehcri+493
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: seehcri
IMAGE_NAME: seehcri.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 478488c1
FAILURE_BUCKET_ID: 0x50_seehcri+493
BUCKET_ID: 0x50_seehcri+493
Followup: MachineOwner
---------
Tak korzystam z tego programu bo mam Telefon sony.No cóż wiemy co jest problemem, najwyżej zreinstaluje aplikacje i zobaczymy.Thermalfake dostajesz pomógł. Temat rozwiązany. Do zamknięcia