New
#11
Will do...thanks
5min shut down Screen/BSOD on restart but ok on pwr cyc
-
-
New #12
Wow....Not so good with the bios update....I already had the latest (non-beta) version but there was a beta version on gigabyte's website but with that version it BSOD'ed no mater what (well safe mood worked)...so here are some more minidumps
Thanks Bradey
-
New #13
Are you overclocking either CPU, or GPU?
all three dumps have different bug checks, and causes.
first dump hardware with ntkrnl involved
second dump below
I suspect given the randomness of the causes, that the bios upgrade, or memory might need to be examined
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\111209-14929-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`02c58000 PsLoadedModuleList = 0xfffff800`02e95e50
Debug session time: Thu Nov 12 17:58:19.173 2009 (GMT-5)
System Uptime: 0 days 0:00:10.126
Loading Kernel Symbols
...............................................................
...........................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88004c89021, fffff880035d3b90, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+3b6021 )
Followup: MachineOwner
---------
5: 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: fffff88004c89021, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880035d3b90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nvlddmkm+3b6021
fffff880`04c89021 898c9088000000 mov dword ptr [rax+rdx*4+88h],ecx
CONTEXT: fffff880035d3b90 -- (.cxr 0xfffff880035d3b90)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000003
rip=fffff88004c89021 rsp=fffff880035d4570 rbp=fffffa800c9711b0
r8=0000000000000010 r9=0000000000000010 r10=fffff880035d4570
r11=fffffa800cdfe1b0 r12=fffffa800c92a870 r13=fffff88004f21a18
r14=000000000000000f r15=fffff88004f21a40
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0x3b6021:
fffff880`04c89021 898c9088000000 mov dword ptr [rax+rdx*4+88h],ecx ds:002b:00000000`00000088=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88004c89021
STACK_TEXT:
fffff880`035d4570 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x3b6021
FOLLOWUP_IP:
nvlddmkm+3b6021
fffff880`04c89021 898c9088000000 mov dword ptr [rax+rdx*4+88h],ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+3b6021
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56
STACK_COMMAND: .cxr 0xfffff880035d3b90 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+3b6021
BUCKET_ID: X64_0x3B_nvlddmkm+3b6021
Followup: MachineOwner
---------
three obvious things you can do.
update critical drivers. Bios, video, raid, etc
second run a system file check by typung
cmd in search>right click and run as admin> sfc /scannow
let us know the results
third download and run memtestx86 and run overnight.
Hope this helps.
If you get more bsod upload them so we can narrow the focus
Ken J
-
-
New #15
Those dumps were from the beta bios and between dumps i was trying changes in the bios...however i have since gone back to the latest released bios...did you check out the dumps from the earlier post...those were with the working bios
A little bit more info for you all...
We have another machine with almost the same components...only differences are - just the two 295's in SLI (no third vid card), and different brand ssd's....This machine doesn't BSOD on restart with the same vid drivers, bios, updates, etc.
With the two cards in SLI you can only run two monitors so i threw the 7200 in my machine to run a third monitor...this seems to be the only difference (IMO) that could be causing the BSOD on restart.
We recently installed 7 x64 on eight Dell workstations of various components and configurations...none of which have the BSOD on restart issue...however all of which plus the two in house built machines have excessive shut down issue.
a recap on the shut down issue...everything closes out almost immediately and then the "shutting down" screen comes up with the "thinking" revolving circle icon for (in most cases) 5+ minutes.
Both issues have been consistent on my machine from 7 beta - 7rc - 7 release as well as multiple nvidia drivers over that time.
Well maybe my rambling helps...and thanks to all for the info thus far...let me know if i can provide any other info....thanks Bradey
-
-
Quote
Related Discussions