bluescreen... už nevím co s ním prosím o pomoc Vyřešeno

[atp.martin]

ahoj,

už mi zase začal vyskakovat bluescreen:

page fault in nonpaged area
DRIVER_IRQL_NOT_LESS_OR_EQUAL

ve čtvrtek jsem si kvůli předchozím bluescreenum koupil novou desku a nové paměti a stejně pořád vyskakují...
ve W7 i W8 jediné co funguje je linux... :(

zapnul jsem i verifier a nic...

goldmemory a memtest jsou s 0 erors (13hodin kazdý)

v pc nic přetaktovaného nemám
bios mam aktualizovaný na nejnovejší verzi

sestava:
AMD FX 8120
ASUS M5A99X EVO R2.0 NOVÁ
Corsair 2x4GB DDR3 1600MHz NOVÁ
ASUS HD 6870
Corsair CX600
Western Digital Caviar Blue 1000GB 32MB cache

už jsem opravdu zoufalý a nevím co dál... :(
prosím o pomoc...

[Reklama]

[guest]

Předně by ses měl naučit pořádně napsat nadpis chyby a vyhledač by ti možná nabídl řešení, je to vždy dole na stránce Mohlo by vás zajímat. Nevím co s tím fakt není dobře.

Pročti následující - search.php?keywords=DRIVER_IRQL_NOT_LESS_OR_EQUAL&terms=all&author=&sv=0&sc=1&sf=all&sr=posts&sk=t&sd=d&st=0&ch=300&t=0&submit=Hledat

[atp.martin]

číst to nemusím protože je to taky ode mě...

a než jsem napsal na toto forum tak sem nejprve googlil a bez výsledků...

[guest]

Aha to já nevím ,nicméně to neznamená, že tam něco nepřibylo. A jak jste to tedy minule vyřešili anebo nevyřešili? Ty systémy jsou legální?

[atp.martin]

nevyřešily založil jsem nové tema protože jsem koupil nový HW...
ano W8 pro jsem koupil v akci a W7 professional také legální...
jak už jsem psal výše jen linux funguje... :(

EDIT: ani Microsoft mi neporadil

[MiliNess]

Upni mi soubory ze složky Windows\Minidump na www.leteckaposta.cz

[atp.martin]

http://leteckaposta.cz/187638758

[MiliNess]

Bude to nějaká HW závada. Proto ti technická podpora MS nepomůže. To že Linux běží v pohodě na tom nic nemění.
-udělal jsi minule ten thorough test v GoldMemory?
-zvyš časování pamětí a mírně i napájecí napětí pamětí (mírně!!)
-co teploty komponent v zatížení?

[atp.martin]

pomuže ti nějak tohle:

_________________________________________________________
_________________________________________________________

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 17. 11. 2012 14:50:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-14336-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xFC (0xFFFFF8801BB91F8C, 0x800000012598F963, 0xFFFFF802A6C2F780, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 17. 11. 2012 14:50:57 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rt63.sys (Rt630x64+0x1A6BC)
Bugcheck code: 0xFC (0xFFFFF8801BB91F8C, 0x800000012598F963, 0xFFFFF802A6C2F780, 0x0)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rt63.sys .
Google query: rt63.sys ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY



On Sat 17. 11. 2012 14:43:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-16676-01.dmp
This was probably caused by the following module: fwpkclnt.sys (0xFFFFF88001E8370A)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x1, 0xFFFFF88001E8370A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fwpkclnt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FWP/IPsec Kernel-Mode API
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 17. 11. 2012 14:33:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-16879-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xD1 (0xFFFFF80328EB50B0, 0x2, 0x8, 0xFFFFF80328EB50B0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 17. 11. 2012 14:32:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-16208-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xFC (0xFFFFF88001EF8480, 0x8000000001060121, 0xFFFFF8801D8A5F20, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 17. 11. 2012 14:29:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-15163-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x50 (0xFFFFF80191B25790, 0x8, 0xFFFFF80191B25790, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 17. 11. 2012 14:25:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-15522-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40CF8)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF88002FCF358, 0xFFFFF88002FCEB90, 0x3066744E)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 17. 11. 2012 5:49:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-16005-01.dmp
This was probably caused by the following module: fwpkclnt.sys (0xFFFFF88001D42A25)
Bugcheck code: 0x50 (0xFFFFFFFF909106F6, 0x1, 0xFFFFF88001D42A25, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fwpkclnt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FWP/IPsec Kernel-Mode API
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 17. 11. 2012 5:43:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-26473-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x2269B0)
Bugcheck code: 0x50 (0xFFFFF88001CD69B0, 0x8, 0xFFFFF88001CD69B0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\tcpip.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 17. 11. 2012 5:31:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-16910-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xD1 (0xFFFFF80324F7BDE0, 0x7, 0x8, 0xFFFFF80324F7BDE0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 17. 11. 2012 5:29:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-16442-01.dmp
This was probably caused by the following module: hal.dll (hal+0x17325)
Bugcheck code: 0xD1 (0xFFFFF80140B67B90, 0x2, 0x8, 0xFFFFF80140B67B90)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 17. 11. 2012 5:23:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-14726-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xFC (0xFFFFF88001FF0951, 0x8000000001060121, 0xFFFFF8801D5BBF80, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 17. 11. 2012 5:16:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-17971-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1D5001)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF88001CBC001, 0xFFFFFA800A1ADB00, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 17. 11. 2012 5:14:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-16161-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xD1 (0xFFFFF80346967B90, 0x2, 0x8, 0xFFFFF80346967B90)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 17. 11. 2012 5:05:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111712-15646-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0xD1 (0xFFFFF80073B2DE20, 0x2, 0x8, 0xFFFFF80073B2DE20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



_________________________________________________________________________________________________________________________
_________________________________________________________________________________________________________________________


teploty cpu jsou max 47C°

ale grafika tam videt není a přitom mám ovladače z http://www.amd.com nainstalovaný...

ovládací panel grafiky je nějaky ořezaný
a v dolním pravém rohu (v liště) není ani amd CCC vidět... (?)

[MiliNess]

Já jsem ty chyby viděl v debuggeru. Jsou to víceméně náhodné chyby, které spolu nemají mnoho společného.
Co ten GoldMemory?

[Pic]

Uvedená napětí nejsou dobrá! Nebo ten program neuvádí správné hodnoty. Může být chyba na základní desce.

[atp.martin]

ten už jsem dělal minule (9hodin) a 0 erors

ty paměti mám dát na 10 10 10 25 a 1,65 ??

zdroj mám Corsair 600w