event 41 lockups help lots of info!

[Gw2]

event 41 lockups help lots of info! UPDATE!

Ok I'm going to try to present the information i have in the easiest way possible. If you need any more info please ask and I'll do my best to get it to you. I'd also like to add a qick apology for the less than perfect punctuation, I'm typing with on hand due to a recent injury (cut my arm with a grinder) but i try my best still anyway. i can post pics of my arm after the surgery too later if you want haha.

- crashes are consistent in the form of a total lockup. screen remains displaying last image before the crash. rarely accompanied by terrible scratching sounds coming from the speakers which subside momentarily. also rarely accompanied by last second or so sound heard looping.

- uploaded some pictures of a crash with HWmonitor running as well as the sf diagnostic tool dump i made.

What I have done already (I was going to call this "what i know" but i guess i cant really know for sure.

what seems right.

- tested memory with memtest 86+ and sisoft sandra, no crashes or errors
- Tested graphics cards with fur(proper name since forgotten lol) no crashes.
- tested graphics cards with vmt, no errors.
- tested cpu with sandra and a couple other stress tests.
- i think ive eliminated the power supply as the problem by running on only 1 graphics card and 1 stick of ram.

reproducing the problem.

- Run World of warcraft for several hours, crashes randomly with seemingly no set time or cause, however does seem to happen more often on load screens.)
- run unigine heaven benchmark, crashes randomly during benchmarking (never without actually starting the benchmark process even though its already doing all the 3d modelling and such. often freezes on loading screens when i swith settings making it reload.
- has also done it once while burning a movie (during transcoding and not the actual burning process

Oddities

- no minidump
- no bsod
- stressing individual componants of the system never seems to reproduce the problem.
- switching my graphics cards and ram around seems to solve the problem for a short while.

Thanks for the help guys!

 

[usasma]

The screenshot shows a system temp of 90º C - awfully hot.
Run the system until it freezes, shut it down and unplug it from the wall.
Open the case and feel around inside (CAREFULLY!!!). You'll be looking for something that's much hotter than the video card is.

The upload doesn't have a copy of the System log file from the Event Viewer.
Please re-download the app (the system log was a recent addition) and rerun it to gather the system log file.

 

[Gw2]

I have the latest version. however it gives me 2 errors

file not found *.dmp
0 file(s) copied
file not found *.dmp

and its at 92 at idle. didnt really notice that. what is sytem temp anyway mobo?

EDIT: okay i felt around but couldnt find anything near the temp of my graphics cards. and sf diag still wont find those files.

EDIT 2: ok ive been doing the 1 graphics card at a time thing and im getting very odd results. last time i used only this card it froze instantly twice in a row, then i switched and it seemed stable. now im using the same card and i cant for the life of me get it to freeze. but i know its not going to stay stable forever. i might rma the motherboard. to eliminate it as a possibility.

 

[Gw2]

Ok i upped memory voltage and it seems good now. ill post again if it happens again.

Ok nevermind that froze again promptly, this time i left it frozen for a while and it gave me a bsod and a minidump! uploading now!

 

[Gw2]

bump for minidump analysis.

 

[Gw2]

Ok I'v got the minidump report but i dont really know how to read it.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\030710-28407-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`03096e50
Debug session time: Sun Mar  7 16:33:20.687 2010 (UTC - 5:00)
System Uptime: 0 days 0:07:08.528
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8003248028, b2000040, 800}

Probably caused by : hardware

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8003248028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  unigine.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f3a58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

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

 

[ickymay]

.dmp shows BugCheck 124, Probably caused by : hardware those are your clues with no driver named as a bugcheck 124 is hardware fault

as Usasma said your system temp is way too high , ideally it should be below CPU temp so 35-40deg c :sarc:

I reckon you have some serious airflow problems in your case, just removing the side panel might help a little adding a large domestic fan temporarily to reduce the system temperature might be a good way to see if this is causing the lockup and bluescreen ?

 

[Gw2]

airflow is definitely not the issue. i have an antec 1200 and a zalman 9700 led. i dont know what that system temp is because in the bios it doesnt say anything is near that hot. and nothing feels hotter than my graphics cards. not even close.

 

[Gw2]

ok i just installed xp on a seperate hard drive to eliminate OS issues as a possibility. going to test after updates.

 

[ickymay]

hmm dunno about that with temperatures then scrap that idea

can you run the windows 7 upgrade advisor to check your hardware compatibility ?

 

[Gw2]

will do.

 

[Jonathan_King]

"Hardware" can sometimes indicate a RAM problem. Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn.

I do agree with the others, though. 90 is very hot for just about everything except the GPU.

I would strongly recommend cooling down that motherboard somehow! I'm guessing that is the issue.

 

[Gw2]

Cooling the motherboard is not an issue, i've felt the entire thing and nothing is near the heat of the graphics cards. ive heard before of programs reading sensors that dont exist on your system as high temps. and the upgrade advisor gives an all clear.

maybe i need to rma the motherboard?

 

[Jonathan_King]

Well try a memory test and also look in your BIOS to see what temps it shows.

Another thing you can try is a hard disk test. Download the appropriate program for your drive and run a scan. Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

 

[Gw2]

i did that yesterday for 3 hours. no memory issues according to it. ill trythe hdd scans.

 

[Gw2]

hdd scans show no errors but say my hdd firmware should be updated. doing that now.

ok seagate site says no firmware updates needed so i'm good there as far as i can tell. i think the southbridge might be whats getting too hot.

 

[Gw2]

I ran driver verifier and got 2 crashes, on in 3d one on shutdown. heres the dumps.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\030810-25958-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`03043e50
Debug session time: Mon Mar  8 21:09:22.645 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:10.502
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {226, fffff88005d4dde4, fffff98030752c60, 0}

Unable to load image RimUsb_AMD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RimUsb_AMD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RimUsb_AMD64.sys
Probably caused by : RimUsb_AMD64.sys ( RimUsb_AMD64+1de4 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000226, An IRP dispatch handler has returned without passing down or completing this IRP,
	or someone forgot to return STATUS_PENDING.
Arg2: fffff88005d4dde4, The address in the driver's code where the error was detected.
Arg3: fffff98030752c60, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_226

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226

FAULTING_IP: 
RimUsb_AMD64+1de4
fffff880`05d4dde4 48895c2408      mov     qword ptr [rsp+8],rbx

FOLLOWUP_IP: 
RimUsb_AMD64+1de4
fffff880`05d4dde4 48895c2408      mov     qword ptr [rsp+8],rbx

IRP_ADDRESS:  fffff98030752c60

DEVICE_OBJECT: fffffa8005546ab0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800033013dc to fffff80002e77f00

STACK_TEXT:  
fffff880`0afbaa18 fffff800`033013dc : 00000000`000000c9 00000000`00000226 fffff880`05d4dde4 fffff980`30752c60 : nt!KeBugCheckEx
fffff880`0afbaa20 fffff800`0330b47a : fffff800`032ff9f0 fffff880`05d4dde4 fffff980`30752c60 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0afbaa60 fffff800`0330c483 : 00000000`00000226 fffffa80`06990e18 fffff980`30752c60 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`0afbaab0 fffff800`0331779c : 00000000`00000000 fffffa80`06990d60 fffffa80`06990e18 fffff800`0330e24c : nt!VfErrorReport1+0x63
fffff880`0afbab50 fffff800`03317b63 : fffffa80`06990d60 00000000`00000002 fffffa80`05546ab0 fffff800`02f79502 : nt!IovpCallDriver2+0x1bc
fffff880`0afbabb0 fffff800`0331dc2e : fffff980`30752c60 fffff980`30752c60 00000000`00000002 fffffa80`05546ab0 : nt!VfAfterCallDriver+0x353
fffff880`0afbac00 fffff800`0331cc42 : fffff980`30752f28 00000000`00000000 fffffa80`055469a0 fffffa80`06990d60 : nt!IovCallDriver+0x57e
fffff880`0afbac60 fffff800`02f91e55 : 00000000`00000001 00000000`00000000 fffffa80`05546850 fffff980`30752d08 : nt!ViFilterDispatchPower+0x62
fffff880`0afbac90 fffff800`0311b166 : ffffffff`fa0a1f00 fffffa80`06d5d820 00000000`00000080 00000000`00010286 : nt!PopIrpWorker+0x3c5
fffff880`0afbad40 fffff800`02e56486 : fffff880`009eb180 fffffa80`06d5d820 fffff880`009f5fc0 00000000`00000200 : nt!PspSystemThreadStartup+0x5a
fffff880`0afbad80 00000000`00000000 : fffff880`0afbb000 fffff880`0afb5000 fffff880`0afba600 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  RimUsb_AMD64+1de4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RimUsb_AMD64

IMAGE_NAME:  RimUsb_AMD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  480611fc

FAILURE_BUCKET_ID:  X64_0xc9_226_RimUsb_AMD64+1de4

BUCKET_ID:  X64_0xc9_226_RimUsb_AMD64+1de4

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

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\030810-35615-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e5f000 PsLoadedModuleList = 0xfffff800`0309ce50
Debug session time: Mon Mar  8 21:05:36.332 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:18.815
Loading Kernel Symbols
...............................................................
.......................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ec7e44, fffff8800356a8b8, fffff8800356a110}

Unable to load image 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 : nvlddmkm.sys ( nvlddmkm+891d8 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ec7e44, The address that the exception occurred at
Arg3: fffff8800356a8b8, Exception Record Address
Arg4: fffff8800356a110, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!memcpy+204
fffff800`02ec7e44 488b040a        mov     rax,qword ptr [rdx+rcx]

EXCEPTION_RECORD:  fffff8800356a8b8 -- (.exr 0xfffff8800356a8b8)
ExceptionAddress: fffff80002ec7e44 (nt!memcpy+0x0000000000000204)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000010fb29120
Attempt to read from address 000000010fb29120

CONTEXT:  fffff8800356a110 -- (.cxr 0xfffff8800356a110)
rax=fffff8a0006eb270 rbx=0000000000000008 rcx=fffff8a0006eb270
rdx=000007610f43deb0 rsi=fffff8a0006eb270 rdi=0000000000000008
rip=fffff80002ec7e44 rsp=fffff8800356aaf8 rbp=fffff8800356aec0
 r8=0000000000000008  r9=0000000000000001 r10=fffffa8001854148
r11=fffff8a0006eb270 r12=000000000000000a r13=fffff8800356ac38
r14=000000010fb29120 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!memcpy+0x204:
fffff800`02ec7e44 488b040a        mov     rax,qword ptr [rdx+rcx] ds:002b:00000001`0fb29120=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000010fb29120

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031070e0
 000000010fb29120 

FOLLOWUP_IP: 
nvlddmkm+891d8
fffff880`0f4901d8 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff800031c6132 to fffff80002ec7e44

STACK_TEXT:  
fffff880`0356aaf8 fffff800`031c6132 : 00000000`00000001 00000000`00000008 00000000`00000000 00000000`000007ff : nt!memcpy+0x204
fffff880`0356ab00 fffff800`031c5feb : fffffa80`04a36a60 fffff880`0356af70 00064d0a`00000001 00000000`00000001 : nt!ObpCaptureObjectName+0x102
fffff880`0356ab80 fffff800`031c9e35 : fffffa80`01860a90 fffffa80`018e6580 00000000`0000006c 00000000`00000000 : nt!ObpCaptureObjectCreateInformation+0x279
fffff880`0356ac00 fffff800`0316719e : fffffa80`018ffb60 fffff880`0356ad80 fffff880`0356af00 00000000`00000000 : nt!ObCreateObject+0x75
fffff880`0356ac70 fffff800`02ed0153 : fffffa80`018ffb60 fffffa80`04a32c70 00000000`00000000 00000000`00000000 : nt!NtCreateSymbolicLinkObject+0xbe
fffff880`0356ad00 fffff800`02ecc6f0 : fffff800`032439b6 00000000`000090de fffffa80`04a32c70 fffff980`13f28fa0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0356ae98 fffff800`032439b6 : 00000000`000090de fffffa80`04a32c70 fffff980`13f28fa0 fffffa80`04a27000 : nt!KiServiceLinkage
fffff880`0356aea0 fffff880`0f4901d8 : 00000000`00000000 fffffa80`04a27000 fffffa80`04a32c70 00000000`00000202 : nt!IoCreateSymbolicLink+0x46
fffff880`0356af00 00000000`00000000 : fffffa80`04a27000 fffffa80`04a32c70 00000000`00000202 00000000`00000100 : nvlddmkm+0x891d8


SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  nvlddmkm+891d8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4c080b

STACK_COMMAND:  .cxr 0xfffff8800356a110 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+891d8

BUCKET_ID:  X64_0x7E_nvlddmkm+891d8

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

What do you guys make of it?

 

[ickymay]

What do you guys make of it?

RimUsb_AMD64.sys which is a blackberry USB driver is suspect on one .dmp

and nvlddmkm.sys on the 2nd is also suspect, this is your Nvidia graphics driver ?
ideally you need to upload the dumps so that we can run them ?

 

[Gw2]

Okay here are the dumps (both in one zip).

 

[ickymay]

Okay here are the dumps (both in one zip).

thnx and yes I suggest update your Blackberry Desktop Software.

and also update your gfx card driver and or try different versions or rollback ?

are there any conflicts in your device manager ?

you also need to remove sonic burner software ?

PxHlpa64.sys fffff880`01591000 fffff880`0159c380 0x0000b380 0x45c3ac06 02/02/2007 21:24:22

and these drivers

speedfan.sys fffff880`019f5000 fffff880`019fc000 0x00007000 0x45168798 24/09/2006 13:26:48
RimUsb_AMD64.sys RimUsb_AMD64.sys+1de4 fffff880`05d4c000 fffff880`05d52f00 0x00006f00 0x480611fc 16/04/2008 14:49:32
adfs.SYS fffff880`07e9d000 fffff120`07eb5000 0xfffff8a000018000 0x48640195 26/06/2008 20:52:37
nvm62x64.sys fffff880`0f400000 fffff880`0f463d80 0x00063d80 0x48f8fd12 17/10/2008 21:01:06
RimSerial_AMD64.sys fffff880`04704000 6c5265cd`0470bc00 0x6c526d4d00007c00 0x492addcd 24/11/2008 :01:01

which are more old drivers for your blackberry suite RimUsb_AMD64.sys and RimSerial_AMD64.sys

speedfan.sys speedfan version is ancient and the driver pre dates windows 7 :shock:

also this driver nvm62x64.sys which is part of the NVIDIA nForce hardware firewall, built into nVidia nForce motherboard chipsets and is known for causing problems.
Try to uninstall it as you don't really need it ?

process is Open Notepad.
Copy, and paste the text below:

c:
cd %windir%\system32\wbem\
net stop winmgmt /y
ping -n 10 127.0.0.1
rmdir /s /q repository
rmdir /s /q Logs
mkdir Logs
net start winmgm
ping -n 10 127.0.0.1
exit

Save it as nvidia.bat

Run it, by doubleclicking on nvidia.bat

Restart computer.


let us know how it goes