blue screen

hugostieglitz (907)|28.5.2012 20:43

zdravím dnes mi zničeho nic naběhla modraá smrt
než jsem to stačil přečíst tak se restlo pc po naběhnutí os se objevil odkaz na minidup který popisuje chybu,ten přikládám,díky za pomoc

052812-14508-01.rar

veny (161)|28.5.2012 21:13

Ahoj tady máš,nebo i ostatní výpis souboru,vypadá to na nějakej síťovej ovladač,ale počkej si raději na vyjádření nějakýho odborníka ;)

[code]
[SIZE="2"]Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Plocha\052812-14508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`02e5f000 PsLoadedModuleList = 0xfffff800`030a3670
Debug session time: Mon May 28 20:34:39.940 2012 (GMT+2)
System Uptime: 0 days 5:20:31.470
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff880064d2cb0, 0, 0}

Probably caused by : NETIO.SYS ( NETIO!KfdClassify+54c )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880064d2cb0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP:
+2e1952f01a5dfdc
fffff880`064d2cb0 d83b fdivr dword ptr [rbx]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d100
0000000000000000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff880064d3bd8 -- (.exr 0xfffff880064d3bd8)
ExceptionAddress: fffff80002ebb1f5 (nt!RtlLookupEntryHashTable+0x0000000000000055)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff880064d3c80 -- (.trap 0xfffff880064d3c80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0043398a8852e0a7 rbx=0000000000000000 rcx=00fffa80061ea380
rdx=fffffa8005bd3110 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ebb1f5 rsp=fffff880064d3e10 rbp=fffff880064d4320
r8=fffffa8003991280 r9=f227c0552615ff27 r10=fffff880064d3f48
r11=fffff88001600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!RtlLookupEntryHashTable+0x55:
fffff800`02ebb1f5 488b4110 mov rax,qword ptr [rcx+10h] ds:0003:00fffa80`061ea390=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002f6687b to fffff80002ede1c0

STACK_TEXT:
fffff880`064d2bf8 fffff800`02f6687b : 00000000`0000001e ffffffff`c0000005 fffff880`064d2cb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`064d2c00 fffff800`02f31224 : fffff880`064d2e50 00000000`00000000 00000000`00000000 ffffffff`00000000 : nt!KipFatalFilter+0x1b
fffff880`064d2c40 fffff800`02f093cc : 00000001`00010101 00000000`00000001 00000000`00000001 fffffa80`061ff778 : nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`064d2c80 fffff800`02f08e4d : fffff800`03021c48 fffff880`064d53a0 00000000`00000000 fffff800`02e5f000 : nt!_C_specific_handler+0x8c
fffff880`064d2cf0 fffff800`02f07c25 : fffff800`03021c48 fffff880`064d2d68 fffff880`064d3bd8 fffff800`02e5f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`064d2d20 fffff800`02f18bb1 : fffff880`064d3bd8 fffff880`064d3430 fffff880`00000000 fffffa80`04d81190 : nt!RtlDispatchException+0x415
fffff880`064d3400 fffff800`02edd842 : fffff880`064d3bd8 f227c055`2615ff27 fffff880`064d3c80 fffff880`064d4220 : nt!KiDispatchException+0x135
fffff880`064d3aa0 fffff800`02edc14a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`064d3c80 fffff800`02ebb1f5 : 00000000`00000000 fffffa80`04d81000 fffff880`064d3ef8 fffffa80`06bed960 : nt!KiGeneralProtectionFault+0x10a
fffff880`064d3e10 fffff880`01606201 : 00000000`00000000 fffff880`064d3ef8 fffff880`064d4320 fffff880`064d4220 : nt!RtlLookupEntryHashTable+0x55
fffff880`064d3e40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!KfdClassify+0x54c

STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!KfdClassify+54c
fffff880`01606201 488bc8 mov rcx,rax

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: NETIO!KfdClassify+54c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381

FAILURE_BUCKET_ID: X64_0x1E_NETIO!KfdClassify+54c

BUCKET_ID: X64_0x1E_NETIO!KfdClassify+54c

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880064d2cb0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP:
+2e1952f01a5dfdc
fffff880`064d2cb0 d83b fdivr dword ptr [rbx]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: 0000000000000000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff880064d3bd8 -- (.exr 0xfffff880064d3bd8)
ExceptionAddress: fffff80002ebb1f5 (nt!RtlLookupEntryHashTable+0x0000000000000055)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff880064d3c80 -- (.trap 0xfffff880064d3c80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0043398a8852e0a7 rbx=0000000000000000 rcx=00fffa80061ea380
rdx=fffffa8005bd3110 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ebb1f5 rsp=fffff880064d3e10 rbp=fffff880064d4320
r8=fffffa8003991280 r9=f227c0552615ff27 r10=fffff880064d3f48
r11=fffff88001600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!RtlLookupEntryHashTable+0x55:
fffff800`02ebb1f5 488b4110 mov rax,qword ptr [rcx+10h] ds:0003:00fffa80`061ea390=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002f6687b to fffff80002ede1c0

STACK_TEXT:
fffff880`064d2bf8 fffff800`02f6687b : 00000000`0000001e ffffffff`c0000005 fffff880`064d2cb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`064d2c00 fffff800`02f31224 : fffff880`064d2e50 00000000`00000000 00000000`00000000 ffffffff`00000000 : nt!KipFatalFilter+0x1b
fffff880`064d2c40 fffff800`02f093cc : 00000001`00010101 00000000`00000001 00000000`00000001 fffffa80`061ff778 : nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`064d2c80 fffff800`02f08e4d : fffff800`03021c48 fffff880`064d53a0 00000000`00000000 fffff800`02e5f000 : nt!_C_specific_handler+0x8c
fffff880`064d2cf0 fffff800`02f07c25 : fffff800`03021c48 fffff880`064d2d68 fffff880`064d3bd8 fffff800`02e5f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`064d2d20 fffff800`02f18bb1 : fffff880`064d3bd8 fffff880`064d3430 fffff880`00000000 fffffa80`04d81190 : nt!RtlDispatchException+0x415
fffff880`064d3400 fffff800`02edd842 : fffff880`064d3bd8 f227c055`2615ff27 fffff880`064d3c80 fffff880`064d4220 : nt!KiDispatchException+0x135
fffff880`064d3aa0 fffff800`02edc14a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`064d3c80 fffff800`02ebb1f5 : 00000000`00000000 fffffa80`04d81000 fffff880`064d3ef8 fffffa80`06bed960 : nt!KiGeneralProtectionFault+0x10a
fffff880`064d3e10 fffff880`01606201 : 00000000`00000000 fffff880`064d3ef8 fffff880`064d4320 fffff880`064d4220 : nt!RtlLookupEntryHashTable+0x55
fffff880`064d3e40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!KfdClassify+0x54c

STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!KfdClassify+54c
fffff880`01606201 488bc8 mov rcx,rax

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: NETIO!KfdClassify+54c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381

FAILURE_BUCKET_ID: X64_0x1E_NETIO!KfdClassify+54c

BUCKET_ID: X64_0x1E_NETIO!KfdClassify+54c

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880064d2cb0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP:
+2e1952f01a5dfdc
fffff880`064d2cb0 d83b fdivr dword ptr [rbx]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: 0000000000000000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff880064d3bd8 -- (.exr 0xfffff880064d3bd8)
ExceptionAddress: fffff80002ebb1f5 (nt!RtlLookupEntryHashTable+0x0000000000000055)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff880064d3c80 -- (.trap 0xfffff880064d3c80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0043398a8852e0a7 rbx=0000000000000000 rcx=00fffa80061ea380
rdx=fffffa8005bd3110 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ebb1f5 rsp=fffff880064d3e10 rbp=fffff880064d4320
r8=fffffa8003991280 r9=f227c0552615ff27 r10=fffff880064d3f48
r11=fffff88001600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po cy
nt!RtlLookupEntryHashTable+0x55:
fffff800`02ebb1f5 488b4110 mov rax,qword ptr [rcx+10h] ds:0003:00fffa80`061ea390=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002f6687b to fffff80002ede1c0

STACK_TEXT:
fffff880`064d2bf8 fffff800`02f6687b : 00000000`0000001e ffffffff`c0000005 fffff880`064d2cb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`064d2c00 fffff800`02f31224 : fffff880`064d2e50 00000000`00000000 00000000`00000000 ffffffff`00000000 : nt!KipFatalFilter+0x1b
fffff880`064d2c40 fffff800`02f093cc : 00000001`00010101 00000000`00000001 00000000`00000001 fffffa80`061ff778 : nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`064d2c80 fffff800`02f08e4d : fffff800`03021c48 fffff880`064d53a0 00000000`00000000 fffff800`02e5f000 : nt!_C_specific_handler+0x8c
fffff880`064d2cf0 fffff800`02f07c25 : fffff800`03021c48 fffff880`064d2d68 fffff880`064d3bd8 fffff800`02e5f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`064d2d20 fffff800`02f18bb1 : fffff880`064d3bd8 fffff880`064d3430 fffff880`00000000 fffffa80`04d81190 : nt!RtlDispatchException+0x415
fffff880`064d3400 fffff800`02edd842 : fffff880`064d3bd8 f227c055`2615ff27 fffff880`064d3c80 fffff880`064d4220 : nt!KiDispatchException+0x135
fffff880`064d3aa0 fffff800`02edc14a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`064d3c80 fffff800`02ebb1f5 : 00000000`00000000 fffffa80`04d81000 fffff880`064d3ef8 fffffa80`06bed960 : nt!KiGeneralProtectionFault+0x10a
fffff880`064d3e10 fffff880`01606201 : 00000000`00000000 fffff880`064d3ef8 fffff880`064d4320 fffff880`064d4220 : nt!RtlLookupEntryHashTable+0x55
fffff880`064d3e40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!KfdClassify+0x54c

STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!KfdClassify+54c
fffff880`01606201 488bc8 mov rcx,rax

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: NETIO!KfdClassify+54c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381

FAILURE_BUCKET_ID: X64_0x1E_NETIO!KfdClassify+54c

BUCKET_ID: X64_0x1E_NETIO!KfdClassify+54c

Followup: MachineOwner[/SIZE]
---------

[/code]

hugostieglitz (907)|28.5.2012 22:11

veny dík
a nebyl by tady poblíž odborník aby mi to "přeložil" vůbec tomu nerozumím
předem díky

veny (161)|28.5.2012 22:57

nz zkusil bych reinstalovat ovladače k síťovce resp.odinstalace a instalace aktuálních ze stránky výrobce

hugostieglitz (907)|29.5.2012 14:55

[quote=veny;504851]nz zkusil bych reinstalovat ovladače k síťovce resp.odinstalace a instalace aktuálních ze stránky výrobce[/quote]

tak jsem odinstaloval a nainstaloval(teda pokud to bylo ono-realtek_pcielan_7_mb)nic jiného na stránkách výrobce desky nebylo a zatím dobrý

hugostieglitz (907)|30.5.2012 20:36

tak se to dnes stalo znovu
přikládám nový minidump
prosím o identifikaci problému díky moc

053012-13306-01.rar

veny (161)|31.5.2012 02:17

zkus udělat zátěžovej test na každej jednotlivej RAM modul

r34ktor (7477)|31.5.2012 04:00

Jak je na tom tvůj systém? Teploty v zátěži? Nastavení (vlož sem screenshoty záložek CPU, Mainboard, Memory a SPD (všechny osazené sloty) z programu CPU-Z)?.

hugostieglitz (907)|31.5.2012 16:11

tady to je údaaje v gpuz jsou max.teploty během zátěže(nyní mám doma cca 27 stupňů-jižní byt)

r34ktor (7477)|31.5.2012 16:15

Máš paměti otestované GoldMemory?

hugostieglitz (907)|31.5.2012 16:56

[quote=r34ktor;505185]Máš paměti otestované GoldMemory?[/quote]

ted jdu na to,

hugostieglitz (907)|10.6.2012 20:52

žádná chyba
(omlouvám se za zpoždění,byl jsem v polsku a na ukrajině)

superdrooper (208)|10.6.2012 21:10

On Sun 10.6.2012 19:05:40 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ECE452, 0xFFFFF880080E9120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: D:\WINDOWS\system32\ntoskrnl.exe
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

hugostieglitz (907)|11.6.2012 16:55

je možné že to byl amd catalyst 12,4?při instalaci hlásil manager že instalace proběhla s výstrahou(žlutý otazník v kolečku)ale v protokolu bylo všude"úspěch"-dal jsem tam 12,6 beta a od té doby je klid.