5min shut down Screen/BSOD on restart but ok on pwr cyc

Separate issues I believe...

It seems that once configured for my work domain (doesn't happen at home...but different PC) shut down hangs for approximately 5min at the shutting down screen.

BSOD on restart but no BSOD on shut down and restart (power cycle)...This seems to happen only after installing the latest nvidia driver on all video cards (2 x 295's in SLI and a single 7200 GS).

7 pro x64 (Release)...up to date on updates from Microsoft Update
2 x nvidia gtx 295's in SLI (Driver 8.16.11.9107)
1 x nvidia 7200 GS (Driver 8.16.11.9107)
2 x Intel 160g ssd's (raid 0)
12g Corsair DDR3
Intel i7 3.2g cpu
Gigabyte EX58-Extreme mobo

Thanks Bradey

Try a static ip for the nic.

Sorry for my ignorance...I believe it is a static IP (well my TCP/IPv4 has a static IP)...Can the NIC have an separate/additional IP (maybe in the location of the ss)???

That screenshot show the mac address config box. No changes there are necessary.

You can Google for how to set a static ip address in relation to IPv4 for the NIC (lan adapter).

IP was/is static (TCP/IPv4)...unless I'm not understanding something about another way to have a "static IP for the nic"

Here, I copied and pasted from another thread I posted in:

"Go to Network and Sharing Center. Click local area connection. Click Properties. Double click Internet Protocol Version 4 (TCP/IPv4).

Set it as follows:

Ip address = same as router config page, usually 192.168.0.1 or 192.168.1.1 but change the last part to 150 -

for example, if router is 192.168.0.1 make ip address 192.168.0.150
if router is 192.168.1.1 make ip address 192.168.1.150

Subnet mask = 255.255.255.0

Default gateway = router's config page address same as before (192.168.0.1 or 192.168.1.1)

Preferred dns server = same as router's config page (or 208.67.222.222 if that fails)

Hit ok. Test. Disable then enabled the adapter. Test."

torrentg...

sorry for the confusion and thanks for the info...however the TCP/IPv4 is and has been set up as a static IP...I was just curious if I was missing something or if there was something additional that was needed...so I don't think the static IP is the issue as there are others with and without a static IP in my office and the problem is consistent with both.

Ah alright.

If you'd like, we can take a look at the crash dumps. They're located at C:\Windows\Minidump

Zip or Rar them, then attach to a post using the paperclip. You might have to copy them to another folder first before compressing.

Mini dumps

Code:

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


Loading Dump File [E:\Temp\Rar$DI00.453\103009-16130-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Fri Oct 30 09:05:21.342 2009 (GMT-5)
System Uptime: 0 days 0:00:31.326
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b2180, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`066878e8 fffff800`02a27443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx
fffff880`066878f0 fffff800`02a835f7 : fffffa80`00000000 fffff800`00000004 00000000`00026160 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`06687980 fffff800`02ff0895 : fffff800`03015460 fffff880`06687b30 fffff800`03015460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`06687a80 fffff800`02a773f3 : 00000000`c91f0510 fffff880`05323e18 00000000`00000000 fffff880`03088180 : hal!HalpHpetClockInterrupt+0x8d
fffff880`06687ab0 fffff800`02a3caa3 : fffff880`03088180 fffff800`02a7f071 fffff880`05323d70 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`06687c40 fffff800`02a81a3f : fffff800`02bf3e80 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x23
fffff880`06687c70 fffff880`04a2990a : 00000000`00000000 fffff880`06687d00 00000000`00000008 fffffa80`00000000 : nt!KeAcquireSpinLockAtDpcLevel+0x6f
fffff880`06687cc0 00000000`00000000 : fffff880`06687d00 00000000`00000008 fffffa80`00000000 fffff880`03093000 : nvlddmkm+0x15e90a


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:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

Going by this: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

That really sounds like something a bios update should take care of. So ya, try to visit the motherboard manufacturer's site to see if there's an update for bios and install it according to their specific instructions.

Let us know how it goes.