Zdarec všem. dvakrát po sobě mi spadl komp a uz fakt nevím co stím. prosim a radu.. zde posilam log z Debugging Tools For Windows..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41287
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Studio.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880031165a0 -- (.trap 0xfffff880031165a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028d34e4 rsp=fffff88003116738 rbp=fffffa8000000000
r8=0000000000000000 r9=0000000000000400 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiPageMightBeZero+0x8:
fffff800`028d34e4 f60220 test byte ptr [rdx],20h ds:1000:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002837b7a to fffff8000288b740
STACK_TEXT:
fffff880`03116438 fffff800`02837b7a : 00000000`0000001a 00000000`00041287 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03116440 fffff800`0288982e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42ba5
fffff880`031165a0 fffff800`028d34e4 : fffff800`028d33ba 00000000`00000000 fffff800`0289e06d 00000000`00000246 : nt!KiPageFault+0x16e
fffff880`03116738 fffff800`028d33ba : 00000000`00000000 fffff800`0289e06d 00000000`00000246 fffff800`028999fd : nt!MiPageMightBeZero+0x8
fffff880`03116740 fffff800`0289f4c6 : fffffa80`021a73f8 fffff880`03116990 00000000`00000000 00000000`00000000 : nt!MiFreeWsleList+0x43e
fffff880`03116930 fffff800`0290da5e : fffffa80`021a73f8 fffff880`00000001 00000000`00000001 fffff880`03116bb0 : nt!MiAgeWorkingSet+0x3a6
fffff880`03116ae0 fffff800`0289fee2 : 00000000`000050f4 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x496d6
fffff880`03116b80 fffff800`028a0173 : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03116bd0 fffff800`02b2fc06 : fffffa80`01947040 00000000`00000080 fffffa80`0184fb30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03116d40 fffff800`02869c26 : fffff800`02a05e80 fffffa80`01947040 fffff800`02a13c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03116d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+42ba5
fffff800`02837b7a cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42ba5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
Followup: MachineOwner
A zde je druhý log po druhém pádu WIn..
*******************************************************************************
* *
* 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: fffff680003b0b00, memory referenced
Arg2: 0000000000000000, 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: fffff80002983ef7, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab50e0
fffff680003b0b00
CURRENT_IRQL: 0
FAULTING_IP:
nt!MiCaptureAndResetWorkingSetAccessBits+97
fffff800`02983ef7 488b5d00 mov rbx,qword ptr [rbp]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: lsm.exe
TRAP_FRAME: fffff88003116850 -- (.trap 0xfffff88003116850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000098000000000 rbx=0000000000000000 rcx=00000000003b0b00
rdx=0000000000123000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002983ef7 rsp=fffff880031169e0 rbp=fffff680003b0b00
r8=0000000000000001 r9=0000000000000014 r10=0000000000000014
r11=fffff680007fa000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MiCaptureAndResetWorkingSetAccessBits+0x97:
fffff800`02983ef7 488b5d00 mov rbx,qword ptr [rbp] ss:0018:fffff680`003b0b00=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000287cca9 to fffff8000287d740
STACK_TEXT:
fffff880`03116708 fffff800`0287cca9 : 00000000`0000000a fffff680`003b0b00 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03116710 fffff800`0287b920 : 00000000`00000000 8aa00000`0b856847 00000000`00001000 fffff800`029b1bfe : nt!KiBugCheckDispatch+0x69
fffff880`03116850 fffff800`02983ef7 : 00000003`00000000 8aa00000`0b856867 fffff680`00000918 fffff700`010809d8 : nt!KiPageFault+0x260
fffff880`031169e0 fffff800`028ffa70 : 00000000`00000000 00000000`00000012 fffff880`03116ba0 fffff880`03116bb0 : nt!MiCaptureAndResetWorkingSetAccessBits+0x97
fffff880`03116ae0 fffff800`02891ee2 : 00000000`00000067 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x496e8
fffff880`03116b80 fffff800`028920e8 : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03116bd0 fffff800`02b21c06 : fffffa80`01963040 00000000`00000080 fffffa80`0184fb30 00000000`00000001 : nt!KeBalanceSetManager+0x138
fffff880`03116d40 fffff800`0285bc26 : fffff800`029f7e80 fffffa80`01963040 fffff800`02a05c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03116d80 00000000`00000000 : fffff880`03117000 fffff880`03111000 fffff880`03116710 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCaptureAndResetWorkingSetAccessBits+97
fffff800`02983ef7 488b5d00 mov rbx,qword ptr [rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiCaptureAndResetWorkingSetAccessBits+97
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiCaptureAndResetWorkingSetAccessBits+97
BUCKET_ID: X64_0xA_nt!MiCaptureAndResetWorkingSetAccessBits+97
Followup: MachineOwner
Pad win + bluescreen of death
- LifeRoma
- Level 3
- Příspěvky: 463
- Registrován: listopad 07
- Bydliště: Česká Republika
- Pohlaví:
- Stav:
Offline
- Kontakt:
Pad win + bluescreen of death
JUST METAL RULES THE WORLD!!!
- Pic
- Moderátor
-
Guru Level 13
- Příspěvky: 23292
- Registrován: září 06
- Bydliště: Východní Čechy
- Pohlaví:
- Stav:
Offline
Re: Pad win + bluescreen of death
Zkontroluj paměti programem Memtest a to alespoň 4x celý test. Pokud zjistí chybu, otestuj postupně každou paměť zvlášť. Ostatní paměti vyjmi z PC při vypnutém počítači. Pozor na statický el. náboj.
Přečti si pravidla tohoto fóra! Přečetl jsi si nejprve manuál? Piš tak, abychom Ti rozuměli! Na SZ neodpovídám na požadavky řešení Vašich problémů s PC!
Nic není dokonalé, ani člověk!
Nic není dokonalé, ani člověk!
- LifeRoma
- Level 3
- Příspěvky: 463
- Registrován: listopad 07
- Bydliště: Česká Republika
- Pohlaví:
- Stav:
Offline
- Kontakt:
Re: Pad win + bluescreen of death
Muže byt tenhle? http://www.memtest86.com/memtest86-3.3.iso.zip Jinak to udělam večer, bo jak to znam tak to poběží každý test minimálně hodinku.:( a ted nemam bohužel čas na to to pouštět
JUST METAL RULES THE WORLD!!!
- LifeRoma
- Level 3
- Příspěvky: 463
- Registrován: listopad 07
- Bydliště: Česká Republika
- Pohlaví:
- Stav:
Offline
- Kontakt:
Re: Pad win + bluescreen of death
Tak uděláno, nechal jsem to běžet 9 hodin, a nikde žádná chyba.:(
JUST METAL RULES THE WORLD!!!
Re: Pad win + bluescreen of death
Udělej si tady kontrolu souborů lsm.exe a Studio.exe nejlépe tady a dej pak klidně screen jak to dopadlo.
EDIT: Máš nejspíše Vista / 7, viď ?
EDIT: Máš nejspíše Vista / 7, viď ?
Acer Predator G5-793 ( i7 6700HQ, GTX1060 6GB )
Re: Pad win + bluescreen of death
Podle původního výpisu to nevypadá na chybu paměti, ale na grafiku. Buď nevhodný ovladač (pro jiný operační systém), anebo získat novější.
Potřebujete jinou pomoc při řešení problému ve Windows 10? Stáhněte si soubor Win10-finty.
- LifeRoma
- Level 3
- Příspěvky: 463
- Registrován: listopad 07
- Bydliště: Česká Republika
- Pohlaví:
- Stav:
Offline
- Kontakt:
Re: Pad win + bluescreen of death
File name: lsm.exe
Submission date: 2010-10-08 14:08:10 (UTC)
Current status: finished
Result: 0/ 43 (0.0%)
File name: Studio.exe
Submission date: 2010-10-08 14:30:49 (UTC)
Current status: finished
Result: 0/ 42 (0.0%)
Zkontrolováno a nic.. jj mám win7
JO tak grafika?.. hmm
Submission date: 2010-10-08 14:08:10 (UTC)
Current status: finished
Result: 0/ 43 (0.0%)
File name: Studio.exe
Submission date: 2010-10-08 14:30:49 (UTC)
Current status: finished
Result: 0/ 42 (0.0%)
Zkontrolováno a nic.. jj mám win7
JO tak grafika?.. hmm
JUST METAL RULES THE WORLD!!!
- LifeRoma
- Level 3
- Příspěvky: 463
- Registrován: listopad 07
- Bydliště: Česká Republika
- Pohlaví:
- Stav:
Offline
- Kontakt:
Re: Pad win + bluescreen of death
Tak a dnes zhruba po 10 min po startu pád WIn.. prosím o pomoc..:(
*******************************************************************************
* *
* 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: fffff6fb7dbe5000, memory referenced
Arg2: 0000000000000000, 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: fffff800028e32e2, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b070e0
fffff6fb7dbe5000
CURRENT_IRQL: 0
FAULTING_IP:
nt!MiAgeWorkingSet+1c2
fffff800`028e32e2 488b19 mov rbx,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff88002f167a0 -- (.trap 0xfffff88002f167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6fb7dbe5000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028e32e2 rsp=fffff88002f16930 rbp=007ffffb7dbe5000
r8=0000000000000001 r9=fffffa800447dac8 r10=0000000000000005
r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1c2:
fffff800`028e32e2 488b19 mov rbx,qword ptr [rcx] ds:fffff6fb`7dbe5000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028ceca9 to fffff800028cf740
STACK_TEXT:
fffff880`02f16658 fffff800`028ceca9 : 00000000`0000000a fffff6fb`7dbe5000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f16660 fffff800`028cd920 : 00000000`00000000 00000980`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02f167a0 fffff800`028e32e2 : 00000000`000002be 00000000`00000001 00000000`00000002 00000000`0000025c : nt!KiPageFault+0x260
fffff880`02f16930 fffff800`02951a5e : fffffa80`0447dac8 fffff880`00000001 00000000`00000001 fffff880`02f16bb0 : nt!MiAgeWorkingSet+0x1c2
fffff880`02f16ae0 fffff800`028e3ee2 : 00000000`000001f7 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x496d6
fffff880`02f16b80 fffff800`028e4173 : 00000000`00000008 fffff880`02f16c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`02f16bd0 fffff800`02b73c06 : fffffa80`01947040 00000000`00000080 fffffa80`0184fb30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`02f16d40 fffff800`028adc26 : fffff800`02a49e80 fffffa80`01947040 fffff800`02a57c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f16d80 00000000`00000000 : fffff880`02f17000 fffff880`02f11000 fffff880`02f16610 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAgeWorkingSet+1c2
fffff800`028e32e2 488b19 mov rbx,qword ptr [rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiAgeWorkingSet+1c2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiAgeWorkingSet+1c2
BUCKET_ID: X64_0xA_nt!MiAgeWorkingSet+1c2
Followup: MachineOwner
---------
*******************************************************************************
* *
* 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: fffff6fb7dbe5000, memory referenced
Arg2: 0000000000000000, 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: fffff800028e32e2, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b070e0
fffff6fb7dbe5000
CURRENT_IRQL: 0
FAULTING_IP:
nt!MiAgeWorkingSet+1c2
fffff800`028e32e2 488b19 mov rbx,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff88002f167a0 -- (.trap 0xfffff88002f167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6fb7dbe5000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028e32e2 rsp=fffff88002f16930 rbp=007ffffb7dbe5000
r8=0000000000000001 r9=fffffa800447dac8 r10=0000000000000005
r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1c2:
fffff800`028e32e2 488b19 mov rbx,qword ptr [rcx] ds:fffff6fb`7dbe5000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028ceca9 to fffff800028cf740
STACK_TEXT:
fffff880`02f16658 fffff800`028ceca9 : 00000000`0000000a fffff6fb`7dbe5000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f16660 fffff800`028cd920 : 00000000`00000000 00000980`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02f167a0 fffff800`028e32e2 : 00000000`000002be 00000000`00000001 00000000`00000002 00000000`0000025c : nt!KiPageFault+0x260
fffff880`02f16930 fffff800`02951a5e : fffffa80`0447dac8 fffff880`00000001 00000000`00000001 fffff880`02f16bb0 : nt!MiAgeWorkingSet+0x1c2
fffff880`02f16ae0 fffff800`028e3ee2 : 00000000`000001f7 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x496d6
fffff880`02f16b80 fffff800`028e4173 : 00000000`00000008 fffff880`02f16c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`02f16bd0 fffff800`02b73c06 : fffffa80`01947040 00000000`00000080 fffffa80`0184fb30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`02f16d40 fffff800`028adc26 : fffff800`02a49e80 fffffa80`01947040 fffff800`02a57c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f16d80 00000000`00000000 : fffff880`02f17000 fffff880`02f11000 fffff880`02f16610 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAgeWorkingSet+1c2
fffff800`028e32e2 488b19 mov rbx,qword ptr [rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiAgeWorkingSet+1c2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiAgeWorkingSet+1c2
BUCKET_ID: X64_0xA_nt!MiAgeWorkingSet+1c2
Followup: MachineOwner
---------
JUST METAL RULES THE WORLD!!!
-
- Mohlo by vás zajímat
- Odpovědi
- Zobrazení
- Poslední příspěvek
-
- 3
- 980
-
od Zivan
Zobrazit poslední příspěvek
22 kvě 2023 14:45
Kdo je online
Uživatelé prohlížející si toto fórum: Žádní registrovaní uživatelé a 1 host