Bsod

akoglu · 29 jan 2011

Ik heb een opmaat gaming computer met windows 7 erop
Maar de probleem is, elke keer dat ik hem opstart krijg ik een BSOD. MAar soms heb ik geluk en krijg ik geen bsod, maar de volgende ochtend weer wel. Ik heb hem ook weer geformateerd zonder resultaat

Platzii · 29 jan 2011

Dag akoglu

welke informatie staat er als je een BSOD krijgt?

Simon

akoglu · 29 jan 2011

0x01a

Platzii · 29 jan 2011

Kun je ook de foutmelding (2de lijn, in hoofdletters) en bestuurder (*.sys, ergens in het midden) even doorgeven?

Groet
Simon

dnties · 29 jan 2011

Kijk in de map C:\Windows\Minidump
Daar zouden dump-bestanden moeten staan die qua aanmaaktijd overeenkomen met de tijdstippen dat jij die bsod's kreeg.

Pak in (met Winzip of Winrar) enkel van die dump-bestanden en zet ze hier op het forum als bijlage neer. Misschien kunnen we er wat uit opmaken voor je.

Vermeld ook of je recent nog dingen veranderd hebt (nieuwe software geïnstalleerd, nieuwe hardware geïnstalleerd, nieuwe drivers geïnstalleerd etc.) en wat je toen precies gedaan hebt.

Tijs.

akoglu · 29 jan 2011

Het is een nieuwe, op maat gebouwde P|C Thijs.

dnties · 29 jan 2011

dnties zei:
Kijk in de map C:\Windows\Minidump
Daar zouden dump-bestanden moeten staan die qua aanmaaktijd overeenkomen met de tijdstippen dat jij die bsod's kreeg.

Pak in (met Winzip of Winrar) enkel van die dump-bestanden en zet ze hier op het forum als bijlage neer. Misschien kunnen we er wat uit opmaken voor je.[...]

Als je verder niets had gedaan/geïnstalleerd/veranderd vóór die Bsod's, dan bovenstaande even doen.

Tijs.

akoglu · 31 jan 2011

http://filebeam.com/download.php?file=f36c7ebc0bcbed128d4a65c782d700ea

Password: 0021

dnties · 1 feb 2011

Code:

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\tijs\Bureaublad\Minidumps\012711-31949-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Thu Jan 27 10:43:51.154 2011 (GMT+1)
System Uptime: 0 days 0:01:20.778
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 51, {1, fffff8a0021eb010, 104000, 465}



Probably caused by : discache.sys ( discache!DisCreateObjectAttributeStore+ec )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[B]REGISTRY_ERROR (51)
Something has gone badly wrong with the registry.  If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
[/B]Arguments:
Arg1: 0000000000000001, (reserved)
Arg2: fffff8a0021eb010, (reserved)
Arg3: 0000000000104000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 0000000000000465, depends on where Windows bugchecked, may be return code of
	HvCheckHive if the hive is corrupt.

Debugging Details:
------------------




CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x51

PROCESS_NAME:  System

CURRENT_IRQL:  0

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a2, 0, 0, 0}



Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------




CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  dw20.exe

CURRENT_IRQL:  0

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8001737bd0, ffff, 0}



Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001737bd0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------




BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8001114dd0, ffff, 0}



Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001114dd0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------




BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800169cad0, ffff, 0}



Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa800169cad0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------




BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80017375d0, ffff, 0}



Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339d6 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80017375d0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------




BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  RealTemp.exe

CURRENT_IRQL:  0

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880038a9258, fffff880038a8ac0, fffff80002a6ac56}



Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880038a9258
Arg3: fffff880038a8ac0
Arg4: fffff80002a6ac56

Debugging Details:
------------------




EXCEPTION_RECORD:  fffff880038a9258 -- (.exr 0xfffff880038a9258)
ExceptionAddress: fffff80002a6ac56 (nt!RtlDeleteNoSplay+0x000000000000002a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880038a8ac0 -- (.cxr 0xfffff880038a8ac0)
rax=fffff8a0062f7f68 rbx=ffeffa8005bb7740 rcx=fffff8a006ad1c28
rdx=ffeffa8005bb7740 rsi=ffffffffffffffff rdi=fffff8a0062f7f68
rip=fffff80002a6ac56 rsp=fffff880038a9490 rbp=fffffa8005bb7740
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80002a17000
r11=fffff8a006ad1c28 r12=0000000000000705 r13=0000000000000000
r14=fffffa8005bb76f8 r15=fffff8a0024f5ed8
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!RtlDeleteNoSplay+0x2a:
fffff800`02a6ac56 48832300        and     qword ptr [rbx],0 ds:002b:ffeffa80`05bb7740=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a2, 0, 0, 0}



Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------




CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002bb5000, fffff880038d5f70, 0}



Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+174 )

Followup: Pool_corruption
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002bb5000, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880038d5f70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------




EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt.

FAULTING_IP: 
nt!ExDeferredFreePool+174
fffff800`02bb5000 4c395008        cmp     qword ptr [rax+8],r10

CONTEXT:  fffff880038d5f70 -- (.cxr 0xfffff880038d5f70)
rax=ffeff880025baee0 rbx=0000000000000000 rcx=fffff880025bb7d0
rdx=fffff900c2446aa0 rsi=0000000000000000 rdi=fffff900c21427e0
rip=fffff80002bb5000 rsp=fffff880038d6940 rbp=0000000000000000
 r8=fffff900c1ef3010  r9=fffff900c24469b0 r10=fffff900c24469c0
r11=0000000000000001 r12=fffff880025bacc0 r13=0000000000000000
r14=0000000000000009 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ExDeferredFreePool+0x174:
fffff800`02bb5000 4c395008        cmp     qword ptr [rax+8],r10 ds:002b:ffeff880`025baee8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002bb5000

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800109bbd0, ffff, 0}



Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa800109bbd0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------




BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

Je moet zelf maar even googelen (het zijn (te)veel dumps om allemaal door te nemen), maar zie dat een aantal van die meldingen (zo goed als) hetzelfde zijn. Het zou (bijv.) kunnen zijn dat een of enkele van je geheugenmodules kapot is, de registry in Windows kapot is (of dat je een schijfcontrole met reparatie los moet laten op de harddisk) etc.

Succes,

Tijs.

akoglu · 1 feb 2011

Help =[

dnties · 1 feb 2011

Belangrijkste waar je op googelen kunt is de bugcheck codes.

Daar zul je (hopelijk) wat uit kunnen halen. Verder de tips van mijn vorige posting ter harte nemen, en je geheugen testen met Memtest86 en verder eens een [Windows-toets]r toetscombinatie -> chkdsk c: /f uitvoeren (je zult wel moeten herstarten om die check te laten uitvoeren).

Succes,

Tijs.

joey1999 · 6 feb 2011

VISTA_DRIVER_FAULT = dat er een driver op je PC staat die Vista niet ondersteund.

dnties · 6 feb 2011

joey1999 zei:
VISTA_DRIVER_FAULT = dat er een driver op je PC staat die Vista niet ondersteund.

Jammer, maar dat klopt niet. Dat Vista die driver niet ondersteunt is niet de vertaling van de melding.

Je moet de melding zien als een opgetreden fout in een driver. De oorzaak daarvan kán een fout geprogrammeerde driver zijn, maar het kunnen ook de omstandigheden zijn, zoals (bijv.) teveel warmte-ontwikkeling, slechte computervoeding, slecht moederbord etc.

Tijs.

Bsod

akoglu

Gebruiker

Platzii

Gebruiker

akoglu

Gebruiker

Platzii

Gebruiker

dnties

Tera Honourable Senior Member †

akoglu

Gebruiker

dnties

Tera Honourable Senior Member †

akoglu

Gebruiker

dnties

Tera Honourable Senior Member †

akoglu

Gebruiker

dnties

Tera Honourable Senior Member †

joey1999

Gebruiker

dnties

Tera Honourable Senior Member †

Nieuwste berichten

Wij waarderen jouw privacy