New
#1
New Build Random Blue Screens
Last edited by street1030; 18 Feb 2010 at 22:00.
these were caiused by three different things. first was video driver, then watchdog, then ntosknl.
Sice they are from three different sources we have to think hardware, specifically memory.
first
un-install the current video driver and reinstall a clean copy
second
memory
download memtestx86 and run for 5 passes
run a sytem file check
type cmdin search>right click and run as admin>sfc /scannow
If you are overclocking stop
let us know if you need help
Ken
DMP filesCode:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\New folder\022010-20280-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02857000 PsLoadedModuleList = 0xfffff800`02a94e50 Debug session time: Sat Feb 20 14:59:52.761 2010 (GMT-5) System Uptime: 0 days 2:17:49.950 Loading Kernel Symbols ............................................................... ................................................................ ............. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 119, {7000000, fffffa8005541410, fffffa80059a2af0, fffffa8006055da0} Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_SCHEDULER_INTERNAL_ERROR (119) The video scheduler has detected that fatal violation has occurred. This resulted in a condition that video scheduler can no longer progress. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 0000000007000000, The subtype of the bugcheck: Arg2: fffffa8005541410 Arg3: fffffa80059a2af0 Arg4: fffffa8006055da0 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x119 PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff8800180122f to fffff800028c8f00 STACK_TEXT: fffff880`05da0ae8 fffff880`0180122f : 00000000`00000119 00000000`07000000 fffffa80`05541410 fffffa80`059a2af0 : nt!KeBugCheckEx fffff880`05da0af0 fffff880`04fb3318 : fffffa80`05f07170 00000000`00000000 00000000`00000000 fffffa80`059a2b50 : watchdog!WdLogEvent5+0x11b fffff880`05da0b40 fffff880`04fb337a : fffffa80`0000378e fffffa80`059a2b50 00000000`00000000 fffffa80`05541410 : dxgmms1!VidSchiCheckConditionDeviceCommand+0x8c fffff880`05da0b70 fffff880`04faf360 : fffffa80`05e84680 fffffa80`059a2af0 fffffa80`07978000 fffffa80`07978000 : dxgmms1!VidSchiCheckPendingDeviceCommand+0x3e fffff880`05da0bb0 fffff880`04faf3af : fffff880`04fdcdc0 fffffa80`05e84680 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x438 fffff880`05da0c70 fffff880`04fde186 : fffffa80`05541410 fffffa80`05541410 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidSchiProcessCompletedQueuePacket+0xf fffff880`05da0ca0 fffff880`04fdd3f8 : fffff880`0308d040 fffffa80`05f07170 00000000`00000000 fffffa80`05541410 : dxgmms1!VidSchiSubmitDeviceCommand+0x52 fffff880`05da0cd0 fffff880`04fdce96 : 00000000`00000000 fffffa80`05f07170 00000000`00000080 fffffa80`05541410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`05da0d00 fffff800`02b6c166 : 00000000`01e7a672 fffffa80`07911b60 fffffa80`054ec040 fffffa80`07911b60 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`05da0d40 fffff800`028a7486 : fffff880`03088180 fffffa80`07911b60 fffff880`030930c0 fffff880`0124ea90 : nt!PspSystemThreadStartup+0x5a fffff880`05da0d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidSchiCheckConditionDeviceCommand+8c fffff880`04fb3318 c744243071c8ffff mov dword ptr [rsp+30h],0FFFFC871h SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgmms1!VidSchiCheckConditionDeviceCommand+8c FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c BUCKET_ID: X64_0x119_dxgmms1!VidSchiCheckConditionDeviceCommand+8c Followup: MachineOwner ---------
Code:021910-21715-01.dmp 2/19/2010 4:11:40 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`04f6753a fffff880`05e7a7c8 fffff880`05e7a020 dxgmms1.sys dxgmms1.sys+31d27 x64 022010-31200-01.dmp 2/20/2010 7:40:02 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff880`098c7240 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 x64 022010-20280-01.dmp 2/20/2010 2:01:42 PM 0x00000119 00000000`07000000 fffffa80`05541410 fffffa80`059a2af0 fffffa80`06055da0 watchdog.sys watchdog.sys+122f x64
Thanks for the reply. I'll do this then post back.
O btw I'm not sure if this would be considered overclocking but i set the ram timings and voltage myself to the factor recommended settings not what the bios had it set at default.
I just burned memtest86 to a disc. Which is the best way to test? should I test with only 1 memory module at a time and do 5 passes of each for a total of 15 passes? or just do all of them at once.
Last edited by street1030; 18 Feb 2010 at 23:03.