BSOD pokaždé jiná hláška - new

[Bumlak]

Mám podobný problém jako Zabi (http://www.pc-help.cz/viewtopic.php?f=46&t=80345&hilit=BSOD+poka%C5%BEd%C3%A9+jin%C3%A1+hl%C3%A1%C5%A1ka). Pokaždé když zapnu notebook tak někdy už při startu windows někdy až po jejich naběhnutí vyskočí BSOD s příslušnými hláškami. Nakonec se mi po několika restartech a "obnovach systemu" podaří počítač spustit a vše už funguje korektně včetně dalších restartů apod. Občas notebook po prvním BSOD naběhne v horším rozlišení a hlásí, že nemá ovladače pro grafiku. Myslel jsem že to tedy bude ovladači grafiky, ale bohužel se mi mu nepodařilo vnutit jiné něž ty stávající na stránkách HP.
Na různých fórech jsem se dočetl, že by to také mohlo být vadnou pamětí - MemTest86 mi běžel 5 hodin bez chyby.

Naprosto nevím čím to může být způsobeno.
Díky za jakýkoli podnět.


notebook: HP pavilion dv6-6010sw (http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c02780850&jumpid=reg_R1002_USEN)

[Reklama]

[Žbeky]

Stáhni si a nainstaluj WhoCrashed
Otevři ho a klikni na Analyze. Program vytvoří zprávu, celou ji zkopíruj a vlož prosím sem.

[Bumlak]

Welcome to WhoCrashed (HOME EDITION) v 3.04
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: 110-A266-6
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4240293888 total
VM: 2147352576, free: 1936654336



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 11.3.2012 11:32:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031112-16785-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002AAB9B7)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.


On Sun 11.3.2012 11:32:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xAD1E2)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002AAB9B7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.


On Sun 11.3.2012 11:24:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031112-17206-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFF8A002B2B000, 0x2, 0x0, 0xFFFFF8800173C554)
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 which cannot be identified at this time.


On Sun 11.3.2012 11:14:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031112-29140-01.dmp
This was probably caused by the following module: bcmwl664.sys (bcmwl664+0x25AE8)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF88006A60AE8)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\bcmwl664.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: bcmwl664.sys Broadcom Corporation UNEXPECTED_KERNEL_MODE_TRAP




On Sat 10.3.2012 6:09:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031012-24320-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFFFFFEFFFFFFF, 0x2, 0x0, 0xFFFFF88001CC77BB)
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 which cannot be identified at this time.


On Sat 10.3.2012 5:52:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031012-31730-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB299C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF960000E299C, 0x1, 0x80000008)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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 which cannot be identified at this time.


On Sat 3.3.2012 8:24:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030312-27284-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xC5 (0x7000000008, 0x2, 0x0, 0xFFFFF80002BC8A9B)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 2.3.2012 17:11:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030212-31839-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88001D23F9A)
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 which cannot be identified at this time.


On Thu 1.3.2012 16:42:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030112-16442-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFFA8008CDFA63, 0xFFFFF88009D2DEC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\031112-16941-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 10 crash dumps have been found. Only 9 could be analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

bcmwl664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Žbeky]

Všechny soubory z C:\Windows\Minidump\ hoď do raru a na leteckaposta.cz

[El Diablo]

Zkontroluj teploty a RAM memtestem.

[Bumlak]

http://leteckaposta.cz/677149682

[MiliNess]

Ten test paměti je v tomto případě nutný.