System po 15 minutach pracy zacina się
|
Gabrielek
Wdrażany
Liczba postów: 30
|
System po 15 minutach pracy zacina się
Witam.
Mój problem wygląda następująco. Dziś odpaliłem komputer i jak zawsze powchodziłem na strony typu Facebook itp. Nagle komputer się zawiesił, a ja myśląc że to nic strasznego zresetowałem go. Potem powtórzyło się to 2 razy i teraz piszę ten post. Dodam że wcześniej pokazywał się BS, lecz sądziłem że to także nic poważnego. Co poradzicie?
|
 Podziękowania od: |
|
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: System po 15 minutach pracy zacina się
Jak pojawił się bsod to podrzuć pliki do analizy z katalogu c:\windows\minidump
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
| Podziękowania od: |
|
|
|
Gabrielek
Wdrażany
Liczba postów: 30
|
RE: System po 15 minutach pracy zacina się
Nie wiem jak wrzucić pliki z minidump, lecz mam dla ciebie w .rar właśnie te pliki z ostatnich BSOD http://www.sendspace.com/file/fmh436
|
| Podziękowania od: |
|
|
|
peciaq
VIP
Liczba postów: 5.100
|
RE: System po 15 minutach pracy zacina się
Przede wszystkim go odkurz.
|
| Podziękowania od: |
|
|
|
Gabrielek
Wdrażany
Liczba postów: 30
|
RE: System po 15 minutach pracy zacina się
Wyczyscic? tj. przeinstalowac i/lub odkurzyc"
|
| Podziękowania od: |
|
|
|
peciaq
VIP
Liczba postów: 5.100
|
RE: System po 15 minutach pracy zacina się
Nie, chodzi mi o fizyczne zakurzenie podzespołów, szczególnie wiatraka procesora i karty graficznej.
|
| Podziękowania od: |
|
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: System po 15 minutach pracy zacina się
Wszystkie 3 błędy sprowadzają się do wadliwego działania sterowników tzn do odwoływania się do pamięci.
Nie wiem co to masz za sprzęt ale radziłbym poszukać najnowszych sterowników od wszystkich urządzeń (chipset/audio/lan/wlan/grafika/...) i je zainstalować.
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\bsody\dmp16\052112-20625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`0305f650
Debug session time: Mon May 21 20: 53: 05.954 2012 (UTC + 2: 00)
System Uptime: 0 days 5: 59: 13.079
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, a490c, 2, b10b}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000a490c, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000000b10b, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002f2010c to fffff80002e97c80
STACK_TEXT:
fffff880`0abc6418 fffff800`02f2010c : 00000000`0000004e 00000000`00000099 00000000`000a490c 00000000`00000002 : nt!KeBugCheckEx
fffff880`0abc6420 fffff800`02efaeea : ffffffff`ffffffff 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!MiBadShareCount+0x4c
fffff880`0abc6460 fffff800`02f98cba : fffffa80`029503f8 fffff880`0abc6670 00000000`00000000 fffffa80`0000000c : nt! ? : FNODOBFM: `string'+0x20ac3
fffff880`0abc6650 fffff800`030da56d : fffffa80`04e65060 00000000`00000001 ffffffff`ffffffff fffff880`0abc6ca0 : nt!MiEmptyWorkingSet+0x24a
fffff880`0abc6700 fffff800`032e819d : 00000000`00000001 fffff8a0`0d9e9220 00000000`00000000 00000000`00000000 : nt!MmAdjustWorkingSetSizeEx+0xad
fffff880`0abc6780 fffff800`031ecfab : 00000000`00000008 00000000`00000000 00000000`00000001 00000000`025ce700 : nt!PspSetQuotaLimits+0x32d
fffff880`0abc68d0 fffff800`02e96f13 : fffffa80`04e65060 fffff880`0abc6ca0 00000000`7efd8000 00000000`7efd8000 : nt! ? : NNGAKEGL: `string'+0x4a490
fffff880`0abc6c20 00000000`76e314da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`025ce6c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e314da
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`02f2010c cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
Followup: MachineOwner
---------
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\bsody\dmp16\051712-21203-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304a650
Debug session time: Thu May 17 08: 48: 26.595 2012 (UTC + 2: 00)
System Uptime: 0 days 0: 40: 43.642
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff6800039d988, d1d0000008395847, fffff68000047cc8}
Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+3266c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff6800039d988
Arg3: d1d0000008395847
Arg4: fffff68000047cc8
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_403
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: iw5mp.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002e2ac56 to fffff80002e82c80
STACK_TEXT:
fffff880`092837a8 fffff800`02e2ac56 : 00000000`0000001a 00000000`00000403 fffff680`0039d988 d1d00000`08395847 : nt!KeBugCheckEx
fffff880`092837b0 fffff800`02eb4017 : fffff700`01080000 fffff680`0039dbd0 fffffa80`040358e0 fffff680`002aaae8 : nt! ? : FNODOBFM: `string'+0x3266c
fffff880`09283960 fffff800`02e6f4bf : fffffa80`00000000 00000000`73b7afff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`09283b20 fffff800`02e81f13 : ffffffff`ffffffff 00000000`0008e320 00000000`0008e318 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`09283c20 00000000`779614fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779614fa
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ? : FNODOBFM: `string'+3266c
fffff800`02e2ac56 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ? : FNODOBFM: `string'+3266c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55
FAILURE_BUCKET_ID: X64_0x1a_403_nt!_??_: FNODOBFM: _string_+3266c
BUCKET_ID: X64_0x1a_403_nt!_??_: FNODOBFM: _string_+3266c
Followup: MachineOwner
---------
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\bsody\dmp16\051512-19609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e55000 PsLoadedModuleList = 0xfffff800`03099650
Debug session time: Tue May 15 21: 33: 56.446 2012 (UTC + 2: 00)
System Uptime: 0 days 6: 52: 54.493
Loading Kernel Symbols
................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffffffffffff9, 2, 0, fffff80002edce8c}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1cc )
Followup: MachineOwner
---------
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: fffffffffffffff9, 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: fffff80002edce8c, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003103100
fffffffffffffff9
CURRENT_IRQL: 0
FAULTING_IP:
nt!KiInsertTimerTable+1cc
fffff800`02edce8c 4c3b78f8 cmp r15,qword ptr [rax-8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from fffff80002eda809 to fffff880069719c2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02eda809 : 00000000`0023d1ce fffffa80`03e757b8 4fcad23f`e1e2f5e7 a5f5034e`1a07aea0 : 0xfffff880`069719c2
fffff800`00b9cca0 fffff800`02ec995c : fffff800`03046e80 fffff800`00000000 00000000`00000000 fffff880`0678552c : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt!KiInsertTimerTable+1cc
fffff800`02edce8c 4c3b78f8 cmp r15,qword ptr [rax-8]
SYMBOL_NAME: nt!KiInsertTimerTable+1cc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55
FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+1cc
BUCKET_ID: X64_0xA_nt!KiInsertTimerTable+1cc
Followup: MachineOwner
---------
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
| Podziękowania od: |
|
|
|
Gabrielek
Wdrażany
Liczba postów: 30
|
RE: System po 15 minutach pracy zacina się
Mieliście rację - wyczyściłem i żadnego BS nie miałem. A co do sterów to mam problemy z wyszukaniem do chipsetu, a tak to mam aktualne.
|
| Podziękowania od: |
|
|
|
peciaq
VIP
Liczba postów: 5.100
|
RE: System po 15 minutach pracy zacina się
Na stronie producenta szukałeś?
|
| Podziękowania od: |
|
|
|
Gabrielek
Wdrażany
Liczba postów: 30
|
RE: System po 15 minutach pracy zacina się
Tak, nic nie mogłem znaleźć. :/
|
| Podziękowania od: |
|
|
|
zygus26
Wdrażany
Liczba postów: 43
|
RE: System po 15 minutach pracy zacina się
Podaj czego ci trzeba na pewno coś znajdziemy.
|
| Podziękowania od: |
|
|
|
Gabrielek
Wdrażany
Liczba postów: 30
|
RE: System po 15 minutach pracy zacina się
Chipset - INTEL P35/G33/G31
Southbridge - INTEL 82801IR (ICH9R)
|
| Podziękowania od: |
|
|
|
Post: #1
![[Obrazek: havensygn.jpg]](http://img33.imageshack.us/img33/2410/havensygn.jpg)
