Quantcast
Viewing all articles
Browse latest Browse all 8389

Bluescreen ! PC crash


I upgraded my PC in "ditech" with a new graphics card a new mainboard(motherboard) and a new harddrive

they said my old hard drive have a dead sector so I changed it

before I change it they said that :if you dont change your old harddrive you will maby see a bluescreen or your pc crashes.

So I backuped my files from my old harddrive and went to the ditech store and buy a new compatible harddrive and they changed my old harddrive to my new harddrive

so I installed the new Windiws 7 iso and updatet my drives **** and stuff and.. I
play a videogame with a friend and I see a Bluescreen again :banghead:

after this I banged my head of and write this Therad

So a.. here is the needed info for you community







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

computer name: DANIEL-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: Gigabyte Technology Co., Ltd., Z77M-D3H
CPU: GenuineIntel Intel(R) Core(TM) i5-3450 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17135898624 total
VM: 2147352576, free: 1961893888





REPORT:
Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7600.2.0.0.768.3
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88009E4B0CB
BCP3: FFFFF88009DDE0D8
BCP4: FFFFF88009DDD940
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\111613-15615-01.dmp
C:\Users\Daniel\AppData\Local\Temp\WER-38922-0.sysdata.xml

Lesen Sie unsere Datenschutzbestimmungen online:
Datenschutzbestimmungen für Windows*7 - Microsoft Windows

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
C:\Windows\system32\de-DE\erofflps.txt

DUMB_FILES:



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 16.11.2013 22:22:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111613-15615-01.dmp
This was probably caused by the following module: bcmwlhigh664.sys (bcmwlhigh664+0x430CB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88009E4B0CB, 0xFFFFF88009DDE0D8, 0xFFFFF88009DDD940)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\bcmwlhigh664.sys
product: Broadcom 802.11 Network Adapter wireless driver
company: Broadcom Corporation
description: Broadcom 802.11 Network Adapter wireless driver
Bug check description: This indicates that a system thread 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.
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: bcmwlhigh664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sat 16.11.2013 22:22:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: bcmwlhigh664.sys (bcmwlhigh664+0x430CB)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88009E4B0CB, 0xFFFFF88009DDE0D8, 0xFFFFF88009DDD940)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\bcmwlhigh664.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 a system thread generated an exception that the error handler did not catch.
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: bcmwlhigh664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
Google query: Broadcom Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Sat 16.11.2013 21:47:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111613-20529-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4710A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CC70A0, 0xFFFFF88003D6C7B8, 0xFFFFF88003D6C020)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

3 crash dumps have been found and 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:

bcmwlhigh664.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.




Im 15year old
know a lot about Computers
happy about any answere
and language:German ,English

Thanks for the comming support

Viewing all articles
Browse latest Browse all 8389

Trending Articles