Stránka 1 z 2
Modrá smrt při hraní Battlefield 3
Napsal: 31 led 2012 21:34
od elixdragon
Ahoj kluci, nevím kde se mám ptát - v počítačovce mi bohužel neřekli nic podstatného

modrá smrt mě navštěvuje při hraní multiplayeru Battlefield 3 - a to celkem často. Jinak při běžné práci na PC jako je Internet, práce v excelu apod. ani jednou. Já sám bych to viděl na slabý zdroj, ale raději se chci zeptat profíků z oboru.
Tady je má sestava:
Procesor: E8500 - 3,16 Ghz
Paměť: 4 Gb
Grafika: GeForce N450GTS
Zdroj: Blue Storm II 400W
Systém: Windows Vista 64 Bit Business
Klávesnice: Microsoft 4000 v1.0
Myš: Xgame Laser Oscar X750
Zde je fotografie obrazovky:

Re: Modrá smrt
Napsal: 31 led 2012 22:49
od Martin63
Osobně si myslím, že je to taky slabý zdroj. Za tuto značku zdroje bych ruku do ohně nedal

, pokud si máš zdroj od koho vypůjčit, tak si ho půjči a zkus...
Re: Modrá smrt
Napsal: 31 led 2012 23:01
od elixdragon
No to bohužel nemám - budu muset koupit. Je to špatný zdroj? Nemyslím výkonově, ale značkou?
Re: Modrá smrt
Napsal: 31 led 2012 23:34
od jaro3
Stáhni si a nainstaluj
WhoCrashedotevři ho a klikni na
Analyze.
Program vytvoří
zprávu , zkopíruj celou a vlož prosím sem.
Upni sem obsah složky:
C:\windows\
minidumpKontaktuj uživatele
MiliNess , zda by Ti pomohl.
Re: Modrá smrt při hraní Battlefield 3
Napsal: 02 úno 2012 21:48
od Martin63
No pokud vím, tak v Alze se dá někde koupit zdroj, který můžeš vrátit do 14 dnů bez udání důvodu. Ale nevím kde jen vím, že něco takového bylo. Moc ti to asi nepomůže, ale můžeš se pokusit to někde najít. Ale stejně tento zdroj, který tam máš: Tak značkově stojí za prd... Něco jako Eurocase, který je na stejné úrovni. A za druhé je na tvou pc sestavu docela slabý, já bych začal tím zdrojem...
Re: Modrá smrt při hraní Battlefield 3
Napsal: 02 úno 2012 21:54
od ClearSky
Předpokládám, že zdroj je modrý Forton, který na sestavu dostačuje. Pokud není vadný.
Re: Modrá smrt při hraní Battlefield 3
Napsal: 02 úno 2012 23:04
od -majk-
ja mam stejny problem ale prihrani necoho ako burnoult paradice alebo test drive 2 taky modra smrt ale niekedy sa podary kompu neresetnut a vypise ze ovladac nedokaze pracovat spravne (v krasnom rozliceni kocka na ocke a v 8bitovych farbach) skusal som chladit preinstalovavat a stale to iste. cim by t mohlo este byt ?
Re: Modrá smrt při hraní Battlefield 3
Napsal: 02 úno 2012 23:32
od Mrvi
Když ti to vypsalo že ovladač nedokáže pracovat správně tak že by to bylo ovladači?

Re: Modrá smrt při hraní Battlefield 3
Napsal: 03 úno 2012 19:02
od elixdragon
Tak koupil jsem zdroj 550W a už to od té doby neudělalo ani jednou.
Re: Modrá smrt při hraní Battlefield 3
Napsal: 04 úno 2012 15:42
od -majk-
Mrvi píše:Když ti to vypsalo že ovladač nedokáže pracovat správně tak že by to bylo ovladači?

neni šanze skusal som ich uz minimalne 5 a + vyvojarsky nastroj od nvidie na upravu vikonu vga a nepomohlo
Re: Modrá smrt při hraní Battlefield 3
Napsal: 04 úno 2012 16:02
od Orcus
Potom zkus support danejch her. Určitě poraděj.

Jo a taky si založ příště vlastní téma, jak káže zdejší desatero.

Re: Modrá smrt při hraní Battlefield 3
Napsal: 13 led 2013 15:36
od elixdragon
Tak to začalo znovu:
computer name: PC-PC
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 5367021568 total
VM: 2147352576, free: 1976721408
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 3.1.2013 20:55:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini010313-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFFA6000E032E0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA6000E032E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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 Thu 3.1.2013 20:55:42 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avgfwd6a.sys (avgfwd6a+0x1CC5)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA6000E032E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\avgfwd6a.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Filter Driver
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.
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: avgfwd6a.sys (AVG Filter Driver, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 31.12.2012 13:25:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini123112-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFFA6000E062E0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA6000E062E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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 Thu 27.12.2012 13:43:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122712-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFFA6000E0B2E0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA6000E0B2E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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 Wed 19.12.2012 22:06:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121912-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFFA6000E0E2E0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA6000E0E2E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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 15.12.2012 21:04:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121512-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFFA6000E032E0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA6000E032E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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 Fri 14.12.2012 18:38:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121412-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x57AD0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8005552A30, 0xFFFFFA8006E18050, 0xFFFFFA80065CBC60)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 Sun 9.12.2012 14:12:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120912-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFFA6000E082E0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA6000E082E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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 Thu 6.12.2012 20:46:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x57AD0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0x0)
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 1.12.2012 16:48:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini120112-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFFA6000E072E0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA6000E072E0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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.