OS Win7 ultimate 64bit
Computer Specs
Cpu intel core i7 870 2.93ghz
cpu fan cooler master V8
M.Board Asus p7h57d-v evo
Ram 8giga(4x2) Corsair ddr3 dominator TR3X6G1600C8D
Sapphire ATI radeon hd 5850 1gb ddr5
HDD WD caviar sata 3 1TB 7200rp
Keyboard Logitech G110
Mouse logitech mx518
PSU Cooler Master real power M520 (maybe low to handle the system?)
With this setup i get some random Bsod while gaming.
attached minidump files with Driver Verifier enabled
Thanks
This one caused by your video driver and not driver verifier enabled. At cmd type verifier /query to find its state.
Re-install using below
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\013011-21528-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\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`02c54000 PsLoadedModuleList = 0xfffff800`02e91e50 Debug session time: Sun Jan 30 14:44:14.603 2011 (GMT-5) System Uptime: 0 days 0:25:35.618 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 119, {7000000, fffffa800676f410, fffffa8008719160, fffffa80086c4010} Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c ) Followup: MachineOwner --------- 4: 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: fffffa800676f410 Arg3: fffffa8008719160 Arg4: fffffa80086c4010 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 fffff8800187a22f to fffff80002cc5f00 STACK_TEXT: fffff880`0280eae8 fffff880`0187a22f : 00000000`00000119 00000000`07000000 fffffa80`0676f410 fffffa80`08719160 : nt!KeBugCheckEx fffff880`0280eaf0 fffff880`0420e318 : fffffa80`086ba450 00000000`00000000 00000000`00000000 fffffa80`087191c0 : watchdog!WdLogEvent5+0x11b fffff880`0280eb40 fffff880`0420e37a : fffffa80`0000378e fffffa80`087191c0 00000000`00000000 fffffa80`0676f410 : dxgmms1!VidSchiCheckConditionDeviceCommand+0x8c fffff880`0280eb70 fffff880`0420a360 : fffffa80`086c5010 fffffa80`08719160 fffffa80`0943c000 fffffa80`0943c000 : dxgmms1!VidSchiCheckPendingDeviceCommand+0x3e fffff880`0280ebb0 fffff880`0420a3af : fffff880`04237dc0 fffffa80`086c5010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x438 fffff880`0280ec70 fffff880`04239186 : fffffa80`0676f410 fffffa80`0676f410 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidSchiProcessCompletedQueuePacket+0xf fffff880`0280eca0 fffff880`042383f8 : fffff800`04054080 fffffa80`086ba450 00000000`00000000 fffffa80`0676f410 : dxgmms1!VidSchiSubmitDeviceCommand+0x52 fffff880`0280ecd0 fffff880`04237e96 : 00000000`00000000 fffffa80`086ba450 00000000`00000080 fffffa80`0676f410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0 fffff880`0280ed00 fffff800`02f69166 : 00000000`00000010 fffffa80`09055b60 fffffa80`06721b30 00000000`00010286 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`0280ed40 fffff800`02ca4486 : fffff800`02e3ee80 fffffa80`09055b60 fffff800`02e4cc40 39393939`39393939 : nt!PspSystemThreadStartup+0x5a fffff880`0280ed80 00000000`00000000 : fffff880`0280f000 fffff880`02809000 fffff880`0280e690 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidSchiCheckConditionDeviceCommand+8c fffff880`0420e318 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 ---------
Thanks, i'll try that and repost with results.
Quote