Random Freezes met Asus p5n-t Deluxe

[airwolf1]

Beste Tweakers,

Ik heb altijd al vanaf het begin problemen gehad met mijn pc, maar de laatste tijd is het steeds erger geworden. Hij is al meerdere keren terug naar alternate geweest voor reparatie maar de problemen waren nooit echt verholpen. De problemen komen nu in de vorm van freezes. De pc freezed voornamelijk bij games, maar ook komt het wel eens voor gelijk na het log-in scherm van windows. Soms kan ik dus 3 uur doorspelen zonder een freeze en soms gebeurt het al na 10 minuten
Ik heb heel veel geprobeerd maar ik kom er zelf niet uit.

Wat heb ik al gedaan:
-Registry schoonmaken (dmv ccleaner of tuneup utilities)
-Clean windows install (nu heb ik vista 32 bit)
-Nieuwte drivers geinstalleerd
-Drivers getest via cmd>verifier>aangepaste instellingen>geavanceerde i/o controle*
-nieuwe fan erin gezet vanwege tamelijk hoge temps (75 graden in games)
-9 uur memtest (0 errors)

-andere anti virus erop gezet
-bios updaten
-enorm veel posts gelezen op het internet opzoek naar vergelijkbare problemen

Mijn systeem
-Psu: RealPower M 700W
-Mobo: Asus P5n-T Deluxe
Gpu: XFX 9800GTX+
CPU: intel quad core 9400
Mem: Ocz pc8500 2 GB DDR2-1066 Kit (x2 dus 4gb)
HDD: Samsung 7200 500gb
Case: Apollo

De temps van me pc lijken nu in orde (komen niet boven de 60), nieuwste drivers, schone os, geen problemen in apparaatbeheer, nooit overgeclocked, bios op defaults. Waar kan het aan liggen ?

Bij voorbaat dank !

* toen ik dit deed, kwam er een bsod die wees op ASACPI.sys. Ik heb toen van asus de file gedownload en mijne vervangen en nu kan ik dit proces herhalen zonder bsod. Ik weet niet of dit relevante informatie is maar ik het zet het er maar even bij.

Nieuw: Er is inderdaad wat mis met ASACPI.sys bestand, ik weet alleen niet wat ik eraan kan doen. Zie hieronder voor de uitslag van de debug.

*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
Probably caused by : ASACPI.sys ( ASACPI+37c )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000023b, The caller has changed the status field of an IRP it does not understand.
Arg2: 8c96037c, The address in the driver's code where the error was detected.
Arg3: 8cb14eb8, IRP address.
Arg4: 00000000

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


ERROR_CODE: (NTSTATUS) 0xc9 - Het besturingssysteem kan %1 niet uitvoeren.

EXCEPTION_CODE: (Win32) 0xc9 (201) - Het besturingssysteem kan %1 niet uitvoeren.

EXCEPTION_PARAMETER1: 0000023b

EXCEPTION_PARAMETER2: 8c96037c

EXCEPTION_PARAMETER3: 8cb14eb8

EXCEPTION_PARAMETER4: 0

BUGCHECK_STR: 0xc9_23b

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 23b

FAULTING_IP:
ASACPI+37c
8c96037c 8bf8 mov edi,eax

FOLLOWUP_IP:
ASACPI+37c
8c96037c 8bf8 mov edi,eax

IRP_ADDRESS: 8cb14eb8

DEVICE_OBJECT: 8c675698

DRIVER_OBJECT: 8c674bd8

IMAGE_NAME: ASACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 411c2d04

MODULE_NAME: ASACPI

FAULTING_MODULE: 8c960000 ASACPI

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LOCK_ADDRESS: 81b72600 -- (!locks 81b72600)

Resource @ nt!PiEngineLock (0x81b72600) Exclusively owned
Threads: 843e3ad0-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0x81b72600
Thread Count : 1
Thread address: 0x843e3ad0
Thread wait : 0x3a6

LAST_CONTROL_TRANSFER: from 81d2814b to 81b0bb8d

STACK_TEXT:
85bdb354 81d2814b 0000004c 000000c9 85bdb374 nt!KeBugCheckEx+0x1e
85bdb4dc 81d27ce3 8d10f920 01000000 00000001 nt!ViBugcheckHalt+0xb0
85bdb780 81d27bf4 0000023b 85bdb790 85bdb878 nt!VfBugcheckThrowException+0xd9
85bdb860 81d2fac5 0000023b 00000009 8c96037c nt!VfBugcheckThrowIoException+0x11b
85bdb89c 81d2b1e9 8cb14fb8 8cb14f94 8d10f718 nt!ViGenericVerifyIrpStackDownward+0x149
85bdb8b8 81d28c31 899bf380 8a79f6a8 8cb14fb8 nt!VfMajorVerifyIrpStackDownward+0x5a
85bdb920 81d2787b 8a6504d8 8a6504d8 8a79f6a8 nt!IovpCallDriver1+0x42e
85bdb938 81d2066d 8a79f6a8 8c675750 8a79f6a8 nt!VfBeforeCallDriver+0xd7
85bdb958 81a8297d 8cb14fb8 8cb14eb8 8a79f6a8 nt!IovCallDriver+0x1ef
85bdb96c 8c96037c 8439a498 8cb14eb8 81d206be nt!IofCallDriver+0x1b
85bdb978 81d206be 8c675698 8cb14eb8 8cb14fd4 ASACPI+0x37c
85bdb99c 81a8297d 8cb14fb8 8cb14ff8 8c675698 nt!IovCallDriver+0x23f
85bdb9b0 81d30290 87d64168 8cb14eb8 8c675548 nt!IofCallDriver+0x1b
85bdb9c8 81d206be 8c675600 8cb14eb8 8cb15000 nt!ViFilterDispatchGeneric+0x5e
85bdb9ec 81a8297d 8cb14fdc 85bdba7c 8c675548 nt!IovCallDriver+0x23f
85bdba00 81d27727 00000000 87ce2588 00000004 nt!IofCallDriver+0x1b
85bdba2c 81d2f82e 87ce2588 85bdba58 00000001 nt!VfIrpSendSynchronousIrp+0xb8
85bdba80 81d2b4be 00000000 85bdbaf4 81ba47b2 nt!VfWmiTestStartedPdoStack+0x4e
85bdba8c 81ba47b2 87ce2588 87d30d48 00000000 nt!VfMajorTestStartedPdoStack+0x3f
85bdbaf4 81b9fb9c 00000001 81b70550 00000000 nt!PipProcessStartPhase3+0x347
85bdbcec 81a4a764 8439ab20 8a6524d0 85bdbd38 nt!PipProcessDevNodeTree+0x2d1
85bdbd44 81ae3e22 00000000 00000000 843e3ad0 nt!PnpDeviceActionWorker+0x229
85bdbd7c 81c13c42 00000000 a468bdb0 00000000 nt!ExpWorkerThread+0xfd
85bdbdc0 81a7cf4e 81ae3d25 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: ASACPI+37c

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xc9_23b_VRF_ASACPI+37c

BUCKET_ID: 0xc9_23b_VRF_ASACPI+37c

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

2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> !drvobj ffffffff8c674bd8 f
Driver object (8c674bd8) is for:
\Driver\MTsensor
Driver Extension List: (id , addr)

Device Object list:
8c675698

DriverEntry: 8c960d20 ASACPI
DriverStartIo: 00000000
DriverUnload: 8c960c20 ASACPI
AddDevice: 8c960932 ASACPI

Dispatch routines:
[00] IRP_MJ_CREATE 8c960c3a ASACPI+0xc3a
[01] IRP_MJ_CREATE_NAMED_PIPE 81a66a22 nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE 8c960c3a ASACPI+0xc3a
[03] IRP_MJ_READ 8c9602e0 ASACPI+0x2e0
[04] IRP_MJ_WRITE 8c9602e0 ASACPI+0x2e0
[05] IRP_MJ_QUERY_INFORMATION 81a66a22 nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION 81a66a22 nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA 81a66a22 nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA 81a66a22 nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS 81a66a22 nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION 81a66a22 nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION 81a66a22 nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL 81a66a22 nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL 81a66a22 nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL 8c960344 ASACPI+0x344
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL 81a66a22 nt!IopInvalidDeviceRequest
[10] IRP_MJ_SHUTDOWN 81a66a22 nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL 81a66a22 nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP 81a66a22 nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT 81a66a22 nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY 81a66a22 nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY 81a66a22 nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER 8c960300 ASACPI+0x300
[17] IRP_MJ_SYSTEM_CONTROL 8c960344 ASACPI+0x344
[18] IRP_MJ_DEVICE_CHANGE 81a66a22 nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA 81a66a22 nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA 81a66a22 nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP 8c960a64 ASACPI+0xa64

2: kd> !drvobj ffffffff8c674bd8 f
Driver object (8c674bd8) is for:
\Driver\MTsensor
Driver Extension List: (id , addr)

Device Object list:
8c675698

DriverEntry: 8c960d20 ASACPI
DriverStartIo: 00000000
DriverUnload: 8c960c20 ASACPI
AddDevice: 8c960932 ASACPI

Dispatch routines:
[00] IRP_MJ_CREATE 8c960c3a ASACPI+0xc3a
[01] IRP_MJ_CREATE_NAMED_PIPE 81a66a22 nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE 8c960c3a ASACPI+0xc3a
[03] IRP_MJ_READ 8c9602e0 ASACPI+0x2e0
[04] IRP_MJ_WRITE 8c9602e0 ASACPI+0x2e0
[05] IRP_MJ_QUERY_INFORMATION 81a66a22 nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION 81a66a22 nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA 81a66a22 nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA 81a66a22 nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS 81a66a22 nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION 81a66a22 nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION 81a66a22 nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL 81a66a22 nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL 81a66a22 nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL 8c960344 ASACPI+0x344
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL 81a66a22 nt!IopInvalidDeviceRequest
[10] IRP_MJ_SHUTDOWN 81a66a22 nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL 81a66a22 nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP 81a66a22 nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT 81a66a22 nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY 81a66a22 nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY 81a66a22 nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER 8c960300 ASACPI+0x300
[17] IRP_MJ_SYSTEM_CONTROL 8c960344 ASACPI+0x344
[18] IRP_MJ_DEVICE_CHANGE 81a66a22 nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA 81a66a22 nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA 81a66a22 nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP 8c960a64 ASACPI+0xa64

2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm ASACPI
start end module name
8c960000 8c961420 ASACPI (no symbols)
Loaded symbol image file: ASACPI.sys
Mapped memory image file: C:\Windows\System32\drivers\ASACPI.sys
Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
Image name: ASACPI.sys
Timestamp: Fri Aug 13 04:52:52 2004 (411C2D04)
CheckSum: 00004AA7
ImageSize: 00001420
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> !locks
**** DUMP OF ALL RESOURCE OBJECTS ****
KD: Scanning for held locks..

Resource @ nt!IopDeviceTreeLock (0x81b72680) Shared 1 owning threads
Threads: 843e3ad0-01<*>
KD: Scanning for held locks.

Resource @ nt!PiEngineLock (0x81b72600) Exclusively owned
Threads: 843e3ad0-01<*>
KD: Scanning for held locks.........
312 total locks, 2 locks currently held

[ Voor 255% gewijzigd door airwolf1 op 31-03-2010 20:26 ]

[stijnos1991]

Hoe is het met andere operating systems?

[airwolf1]

Met windows 7 was het precies hetzelfde. Ik heb echter maar 1 andere os (xp) maar die zit op mijn andere pc

[iichel]

Warmte probleem? CPU en of GPU en of NB te warm?
En anders even een memtest doen om te kijken of je geheugen stuk is. Ik denk aan een hardwareprobleem omdat je met beide OS'en problemen hebt.

[Verwijderd]

Ik zou even het voltage van je memory nalopen,die hoog geclockte ocz modules willen wel eens 2.0v nodig hebben inplaats van de stock 1.8v.
Dat kan al een hoop verhelpen.

Edit:Ik lees dat bijvoorbeeld de ocz reapers modulles werken onder:2.1 - 2.3** Volts

[ Voor 24% gewijzigd door Verwijderd op 29-03-2010 22:10 ]

[Lucky0wn]

Ik heb vrijwel dezelfde configuratie als de TS, op de processor (Q94509) en 2x 9800GTX+ na.
Ook ik heb last van precies hetzelfde probleem en ook dezelfde BSOD's.
Ik heb al alles geprobeerd, en het ligt volgens mij aan een ontwerpfout van de chipset.
Dit denk ik omdat ik 2 andere mensen ken die hetzelfde probleem hebben en in de winkel kan er ook niets gevonden worden.
Ikzelf heb me eroverheen gezet en werkt er gewoon mee vervelend maar 't is zo.

[airwolf1]

Ik zou even het voltage van je memory nalopen,die hoog geclockte ocz modules willen wel eens 2.0v nodig hebben inplaats van de stock 1.8v.
Dat kan al een hoop verhelpen.

Edit:Ik lees dat bijvoorbeeld de ocz reapers modulles werken onder:2.1 - 2.3** Volts

al geprobeerd, zelfde

Warmte probleem? CPU en of GPU en of NB te warm?
En anders even een memtest doen om te kijken of je geheugen stuk is. Ik denk aan een hardwareprobleem omdat je met beide OS'en problemen hebt.

cpu idle rond de 40 graden
gpu idle rond de 60 graden (is dit te hoog?)

ik ga vanavond de hele nacht memtest proberen als ie teminste niet vastloopt...

Ik heb vrijwel dezelfde configuratie als de TS, op de processor (Q94509) en 2x 9800GTX+ na.
Ook ik heb last van precies hetzelfde probleem en ook dezelfde BSOD's.
Ik heb al alles geprobeerd, en het ligt volgens mij aan een ontwerpfout van de chipset.
Dit denk ik omdat ik 2 andere mensen ken die hetzelfde probleem hebben en in de winkel kan er ook niets gevonden worden.
Ikzelf heb me eroverheen gezet en werkt er gewoon mee vervelend maar 't is zo.

Dan geeft alternate me maar een nieuwe pc als het niet mijn schuld is toch ? Ik heb nog garantie maar het is vrij ver weg en volgens mij is het probleem niet al te ingewikkeld.

[Lucky0wn]

sja ik heb na het 4x terugsturen van m'n moederbord in 1.5 jaar tijd geen zin meer in gezeur heb al 2 keer een ander moederbord gehad met precies dezelfde problemen, en de winkel wil ij geen nieuw moederbord meer geven of vergelijkbaarniet leverbaar volgens hun)

[airwolf1]

En anders even een memtest doen om te kijken of je geheugen stuk is. Ik denk aan een hardwareprobleem

9 uur memtest leverde niets op. Ik denk dat het aan het moederbord ligt maar zoals je ziet in de dmp file heeft het blijkbaar met drivers te maken

[airwolf1]

nieuwe bsod weer os opnieuw geinstallereerd, misschien kunnen jullie hier wat meer mee.

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18160.x86fre.vistasp2_gdr.091208-0542
Machine Name:
Kernel base = 0x81a0b000 PsLoadedModuleList = 0x81b22c70
Debug session time: Wed Mar 31 13:51:07.589 2010 (UTC + 2:00)
System Uptime: 0 days 1:26:23.321
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, 8ab14120, 2}

Page 99b16 not present in the dump file. Type ".hh dbgerr004" for details
windbg> .hh dbgerr004
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8ab14120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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

Page 99b16 not present in the dump file. Type ".hh dbgerr004" for details

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1c

STACK_TEXT:
8c3388dc 81ab68c5 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8c338910 81ab86bd 850aa51b 000000d1 8c3389a8 nt!KeUpdateRunTime+0xd5
8c338910 81a2ef1e 850aa51b 000000d1 8c3389a8 nt!KeUpdateSystemTime+0xed
8c3389a8 81c421f1 00000001 1141aa30 00000053 nt!KeFlushProcessWriteBuffers+0x7f
8c338d4c 81a55c7a 00000053 002b2f00 00000004 nt!NtQuerySystemInformation+0x2251
8c338d4c 76f55e74 00000053 002b2f00 00000004 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
006bf828 00000000 00000000 00000000 00000000 0x76f55e74


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8ab14120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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

Page 99b16 not present in the dump file. Type ".hh dbgerr004" for details

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1c

STACK_TEXT:
8c3388dc 81ab68c5 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8c338910 81ab86bd 850aa51b 000000d1 8c3389a8 nt!KeUpdateRunTime+0xd5
8c338910 81a2ef1e 850aa51b 000000d1 8c3389a8 nt!KeUpdateSystemTime+0xed
8c3389a8 81c421f1 00000001 1141aa30 00000053 nt!KeFlushProcessWriteBuffers+0x7f
8c338d4c 81a55c7a 00000053 002b2f00 00000004 nt!NtQuerySystemInformation+0x2251
8c338d4c 76f55e74 00000053 002b2f00 00000004 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
006bf828 00000000 00000000 00000000 00000000 0x76f55e74


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8ab14120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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

Page 99b16 not present in the dump file. Type ".hh dbgerr004" for details
windbg> .hh dbgerr004

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1c

STACK_TEXT:
8c3388dc 81ab68c5 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8c338910 81ab86bd 850aa51b 000000d1 8c3389a8 nt!KeUpdateRunTime+0xd5
8c338910 81a2ef1e 850aa51b 000000d1 8c3389a8 nt!KeUpdateSystemTime+0xed
8c3389a8 81c421f1 00000001 1141aa30 00000053 nt!KeFlushProcessWriteBuffers+0x7f
8c338d4c 81a55c7a 00000053 002b2f00 00000004 nt!NtQuerySystemInformation+0x2251
8c338d4c 76f55e74 00000053 002b2f00 00000004 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
006bf828 00000000 00000000 00000000 00000000 0x76f55e74


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8ab14120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1c

STACK_TEXT:
8c3388dc 81ab68c5 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8c338910 81ab86bd 850aa51b 000000d1 8c3389a8 nt!KeUpdateRunTime+0xd5
8c338910 81a2ef1e 850aa51b 000000d1 8c3389a8 nt!KeUpdateSystemTime+0xed
8c3389a8 81c421f1 00000001 1141aa30 00000053 nt!KeFlushProcessWriteBuffers+0x7f
8c338d4c 81a55c7a 00000053 002b2f00 00000004 nt!NtQuerySystemInformation+0x2251
8c338d4c 76f55e74 00000053 002b2f00 00000004 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
006bf828 00000000 00000000 00000000 00000000 0x76f55e74


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

0: kd> lmvm Unknown_Module
start end module name
0: kd> hh dbgerr004
^ Syntax error in 'hh dbgerr004'
windbg> .hh dbgerr004
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8ab14120, The PRCB address of the hung processor.
Arg4: 00000002, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1c

STACK_TEXT:
8c3388dc 81ab68c5 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8c338910 81ab86bd 850aa51b 000000d1 8c3389a8 nt!KeUpdateRunTime+0xd5
8c338910 81a2ef1e 850aa51b 000000d1 8c3389a8 nt!KeUpdateSystemTime+0xed
8c3389a8 81c421f1 00000001 1141aa30 00000053 nt!KeFlushProcessWriteBuffers+0x7f
8c338d4c 81a55c7a 00000053 002b2f00 00000004 nt!NtQuerySystemInformation+0x2251
8c338d4c 76f55e74 00000053 002b2f00 00000004 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
006bf828 00000000 00000000 00000000 00000000 0x76f55e74


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

[Erwin1967]

Heb je de bios instelling wel eens op de standaard waarden gezet? Ik las dat je een biosupdate had gedaan maar weet niet of dat ook de instellingen terugzet. Ik heb onlangs zelf voor andere problemen zitten experimenteren met instellingen die uiteindelijk tot freezes leidden. Deze verdwenen weer na terugzetten. Het betroffen instellingen met ACPI.

[airwolf1]

Heb je de bios instelling wel eens op de standaard waarden gezet?

yep net nog. Werkt niet (super hardnekkig probleem lol)

ik heb net met driververifier de acpi driver getest en nu krijg ik weer een prachtige bluescreen.

Ik zal me beginpost vervangen met een betere Debug van me dumpfile.

[Erwin1967]

Misschien is de oplossing het deinstalleren van de Asus utilities:

http://vip.asus.com/forum...xe&page=1&SLanguage=en-us