Vantage and 3dMark11 crash on fresh Windows 7 Pro N SP1
I have a Dell n5110 laptop with Intel HD Graphics 3000 and nVidia GT 525M with fresh installation of Windows 7 Pro N SP1 x64.
All drivers have newest versions. Haven't even installed antivirus yet, just some basic software like MS Office, CCleaner, VLC, Skype.
Driver versions:
nVidia: 296.10
Intel HD Graphics: file version showed on Intel page v15.26.12.64.2761 (driver version shown Intel Graphics control panel - 8.15.10.1761)
3DMark11 is crashing when I lauch application. Here is what I get in Event Viewer:
Application: 3DMark11.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at System.RuntimeMethodHandle._InvokeMethodFast(Syste m.IRuntimeMethodInfo, System.Object, System.Object[], System.SignatureStruct ByRef, System.Reflection.MethodAttributes, System.RuntimeType)
at System.RuntimeMethodHandle.InvokeMethodFast(System .IRuntimeMethodInfo, System.Object, System.Object[], System.Signature, System.Reflection.MethodAttributes, System.RuntimeType)
at System.Reflection.RuntimeMethodInfo.Invoke(System. Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, Boolean)
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.Invok eImpl()
at System.Threading.ExecutionContext.runTryCode(Syste m.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invok e()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCat chWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.InvokeImpl(Sys tem.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame)
at .()
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Re: Vantage and 3dMark11 crash on fresh Windows 7 Pro N SP1
Ok, updated SystemInfo.
Now I can start Vantage, but when launch the benchmark it scans system for a while and then crashes my computer. No BSOD, just reboots. No messages in Event Viewer.
3DMark11 does the same. When I disabled SystemInfo in Help tab, then benchmarking ran fine.
Re: Vantage and 3dMark11 crash on fresh Windows 7 Pro N SP1
That is very strange. Either some other application is causing a conflict with the SystemInfo scan or there is something odd with the BIOS. One thing that can cause SystemInfo scan to fail is if "HPET" (High Precision Event Timer) is not enabled in BIOS. However, I have no idea what kind of options a Dell BIOS gives. Could see if there are any BIOS updates available for the laptop?
In general no application can cause straight up spontaneous reboot; it always is a bluescreen. You could also try disabling automatic reboot in Control Panel->System to see what the actual bluescreen is and what file it is referring at... now if there is still no bluescreen, there has to be some kind of issue with the hardware and/or BIOS; applications simply cannot cause such an effect.
Is this a normal unmodified Windows? The N version is very rare in the wild...
Re: Vantage and 3dMark11 crash on fresh Windows 7 Pro N SP1
Yes, it's a normal Windows, the ISO was downloaded from an official source. N version doesn't have Media Player (and some other media components) by requirement European Union. Since I don't use it, I decided to install this version. It turned out that I cannot run Windows Experience Index test because of those missing thigs, so I might install them anyway.
There indeed was a BIOS update, so I updated from A07 to A10. And yes, automatic reboot was enabled. After updating the BIOS and disabling reboot I got a BSOD.
Here's what WinDbg analysis says about minidump:
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800ae08b30, Terminating object
Arg3: fffffa800ae08e10, Process image file name
Arg4: fffff80003186510, Explanatory message (ascii)
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'lltdio' and 'RtsUStor.sys' overlap
PROCESS_OBJECT: fffffa800ae08b30
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.
I had tghis problem last year and a topic in this forum, but we didn't manage to solve it. Was too busy and forgot to follow up on that. Would be nice to finally figure this out.
Re: Vantage and 3dMark11 crash on fresh Windows 7 Pro N SP1
"OVERLAPPED_MODULE: Address regions for 'lltdio' and 'RtsUStor.sys' overlap"
RtsUstor.sys is driver for Realtek USB controller and lltdio is related to network controller (link layer topology mapper I/O driver)
Both are windows components and not directly related to 3DMark... so this is very odd. csrss.exe (the actual crashing binary) is also a windows component.
One thing you could try is see if there are updated drivers for the USB controller or network controller.
Also, as in the old thread, if this is somehow tied to SystemInfo, you could try the procedure for narrowing down which exact module of SystemInfo triggers this. Here is a thread that explains how to manually switch off parts of SystemInfo using a diagnostic tool that is built into it; http://community.futuremark.com/foru...d.php?t=139705
Re: Vantage and 3dMark11 crash on fresh Windows 7 Pro N SP1
Ok, updated network card drivers (wireless and regular) and the driver of usb reader. The drivers on the Dell site of course weren't the newest.
And now when I ran Vantage benchamark it crashed with the following message:
STOP: c000021a {Fatal System Error}
The Windows SubSystem system process terminated unexpectedly with a status of 0xc0000005 (0x779b32d0 0x01fdf0c0).
System has been shut down.
Info extracted from the minidump:
WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: fffff8a00ca66550, String that identifies the problem.
Arg2: ffffffffc0000005, Error Code.
Arg3: 00000000772032d0
Arg4: 000000000029dd80
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
EXCEPTION_PARAMETER1: fffff8a00ca66550
EXCEPTION_PARAMETER2: ffffffffc0000005
EXCEPTION_PARAMETER3: 00000000772032d0
EXCEPTION_PARAMETER4: 29dd80
ADDITIONAL_DEBUG_TEXT: Windows SubSystem
BUGCHECK_STR: 0xc000021a_csrss.exe_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800032ea93e to fffff80002e911c0
Re: Vantage and 3dMark11 crash on fresh Windows 7 Pro N SP1
Hmm, at least the drivers did influence something. Still doesn't quite explain why anything related to 3DMark could cause *Winlogon* process to suddenly die...
I'll have to forward this to the programmers to see if they have any ideas but it'll be next Thursday until the guy who knows everything about SystemInfo is at the office. In the meanwhile... well, since updating some drivers changed the crash to something different, might I suggest looking into updating every other possible device driver just in case if that solves anything?
Re: Vantage and 3dMark11 crash on fresh Windows 7 Pro N SP1
Update to this thread; Our programmers have found the cause for the last crash; It appears it happens only when logged on as "normal user" (rather than administrator user) so it took a while to figure out. We have a fix in testing and it should be available in 1-2 weeks.
As a workaround, you can get things to work even now if you just use an account with administrator permissions.
Reply With Quote
