Bluescreen Windows 7

Pagina: 1
Acties:

Acties:
  • 0 Henk 'm!

  • Dabo007
  • Registratie: Januari 2014
  • Laatst online: 19-09-2022
Hallo allemaal,

de laatste weken krijg ik vaak een Bluescreen.
Het gebeurt de ene keer als ik een filmpje zit te kijken,
maar het gebeurt ook als ik gewoon zit te internetten of een document zit te tikken.

Kan iemand mij helpen om dit probleem te verhelpen?

Hier is het logbestand:

Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7601.2.1.0.256.1
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 116
BCP1: FFFFFA80088EC4E0
BCP2: FFFFF88002E08EFC
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\032314-17828-01.dmp
C:\Users\Dabo\AppData\Local\Temp\WER-89203-0.sysdata.xml

Lees de onlineprivacyverklaring:
http://go.microsoft.com/f...inkid=104288&clcid=0x0413

Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
C:\Windows\system32\nl-NL\erofflps.txt

Acties:
  • 0 Henk 'm!

  • xFeverr
  • Registratie: Juni 2011
  • Laatst online: 21:52
Kan je wat meer vertellen over je pc? De specificaties, soort computer (desktop, laptop, tablet,etc), hoe oud, maakt niet uit als het maar meer informatie is.

Acties:
  • 0 Henk 'm!

  • F_J_K
  • Registratie: Juni 2001
  • Niet online

F_J_K

Moderator CSA/PB

Front verplichte underscores

Dabo007 schreef op dinsdag 25 maart 2014 @ 10:27:
Kan iemand mij helpen om dit probleem te verhelpen?
Ik mis eerlijk gezegd dat je jezelf en ons helpt, door relevante info en de resultaten van je eigen pogingen te geven. (Zie ook Het algemeen beleid #topicplaatsen voor tips over wat er in een topicstart nodig is).
Je hebt vast al [google=BCCode 116] gedaan, wat een mogelijke veroorzaker (videokaart/-drivers) en oplossingsrichting geeft. Welke heb je al geprobeerd (zoals updates doorvoeren), waar loop je dan vast? Ook zegt je quote dat er meer info is te vinden in de minidump. Wat staat daar in (aan relevante info?)

'Multiple exclamation marks,' he went on, shaking his head, 'are a sure sign of a diseased mind' (Terry Pratchett, Eric)


Acties:
  • 0 Henk 'm!

  • Dabo007
  • Registratie: Januari 2014
  • Laatst online: 19-09-2022
Hier de specs van mijn pc:

Desktop-PC
Intell Core i5 2,8Ghz
8,0 GB Ram
Ati Radeon HD4550
Windows 7 64-bit

Ik heb alle drivers een update gegeven.
Ik heb al onderzoek gedaan naar de foutcode 116, maar helaas geen resultaat.
Alle instellingen in Catalyst Control Center op default gezet, maar nog steeds Bluescreens.

Acties:
  • 0 Henk 'm!

  • Rushleader
  • Registratie: November 2011
  • Laatst online: 19-07 11:06
Hey Dabo007,

Na een beetje zoeken kwam ik hier op uit. Deze post geeft een goeie verklaring van het fenomeen.
First off, TDR is an acronym for Timeout Detection and Recovery. Timeout Detection and Recovery was introduced in Vista and carried over to Windows 7. Rather than putting exactly what Timeout Detection and Recovery does exactly, I'll just directly quote the MSDN article!
Quote:
Timeout detection:

The GPU scheduler, which is part of the DirectX graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU is taking more than the permitted amount of time to execute a particular task. The GPU scheduler then tries to preempt this particular task. The preempt operation has a "wait" timeout, which is the actual TDR timeout. This step is thus the timeout detection phase of the process. The default timeout period in Windows Vista and later operating systems is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout period, the operating system diagnoses that the GPU is frozen.
To prevent timeout detection from occurring, hardware vendors should ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and game play.

Preparation for recovery:

The operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to inform the driver that the operating system detected a timeout. The driver must then reinitialize itself and reset the GPU. In addition, the driver must stop accessing memory and should not access hardware. The operating system and the driver collect hardware and other state information that could be useful for post-mortem diagnosis.

Desktop recovery:

The operating system resets the appropriate state of the graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications. Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly. An application must release and then recreate its Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK.

Article here.


With this being said, if Timeout Detection and Recovery fails to recover the display driver, it will then shoot the 0x116 bugcheck. There are many different things that can cause a 0x116, which I will explain below:

The following hardware issues can cause a TDR event:
Quote:
1. Unstable overclock (CPU, GPU, etc). Revert all and any overclocks to stock settings.
2. Bad sector in memory resulting in corrupt data being communicated between the GPU and the system (video memory otherwise known as VRAM or physical memory otherwise known as RAM).
GPU testing: Furmark
RAM testing: Memtest86+

3. Corrupt hard drive or Windows install / OS install resulting in corruption to the registry or page file.
HDD diagnostics: http://www.carrona.org/hddiag.html
To reset your page file, follow the instructions below:

a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.

b ) In this window, note down the current settings for your pagefile (so you can restore them later on).

-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.

c ) Reboot (this will remove the pagefile from your system)

d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step

b ). Follow the steps all the way through (and including) the reboot.

e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:

SFC.EXE /SCANNOW

Go to Start and type in "cmd.exe" (without the quotes)

At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"

In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.

Let the program run and post back what it says when it's done.

- Overheating of the CPU or GPU and or other components can cause 0x116 bugchecks. Monitor your temperatures and ensure the system is cooled adequately.
- GPU failure. Whether it's heat, power issue (PSU issue), failing VRAM, etc.

The following software issues can cause a TDR event:

Quote:
-Incompatible drivers of any sort (either GPU, sound, etc)

-Messy / corrupt registry

-Bad direct x files (uninstall, then reinstall DirectX)

-bad system files (System File Checker - was run above)

-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version).
Bron

Daar geven ze als beste optie een clean install van Windows omdat het een Registry fout kan zijn.

Acties:
  • 0 Henk 'm!

  • Dabo007
  • Registratie: Januari 2014
  • Laatst online: 19-09-2022
Dank voor de informatie.
Ik zit er inderdaad aan te denken om een clean install te doen.

Tnx
Pagina: 1