Here is the most recent minidump, which was accompanied by video card error messages sometime later, possibly related, possibly not...
Any help, gratefully received as this is used every day as my main tv server and my GF is getting a bit ratty over the crashes.
cheers
D.
Your mini dump shows a stop error code of 7E. This a hardware or hardware related issue.
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (go to top of page)
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,You have an extremely obsolete driver on your system. Windows 7 does not like old drivers and they can cause memory corruption and BSOD's.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 813b018e, 88644b2c, 88644710} Probably caused by : win32k.sys ( win32k!CMutex::Lock+6 ) Followup: MachineOwner --------- 0: 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: c0000005, The exception code that was not handled Arg2: 813b018e, The address that the exception occurred at Arg3: 88644b2c, Exception Record Address Arg4: 88644710, 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: win32k!CMutex::Lock+6 813b018e ff31 push dword ptr [ecx] EXCEPTION_RECORD: 88644b2c -- (.exr 0xffffffff88644b2c) ExceptionAddress: 813b018e (win32k!CMutex::Lock+0x00000006) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 52f4cf5f Attempt to read from address 52f4cf5f CONTEXT: 88644710 -- (.cxr 0xffffffff88644710) eax=00000000 ebx=986a14d8 ecx=52f4cf5f edx=00000000 esi=88644c24 edi=88644cc0 eip=813b018e esp=88644bf4 ebp=88644c0c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 win32k!CMutex::Lock+0x6: 813b018e ff31 push dword ptr [ecx] ds:0023:52f4cf5f=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe 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: 00000000 EXCEPTION_PARAMETER2: 52f4cf5f READ_ADDRESS: GetPointerFromAddress: unable to read from 81b74718 Unable to read MiSystemVaType memory at 81b54160 52f4cf5f FOLLOWUP_IP: win32k!CMutex::Lock+6 813b018e ff31 push dword ptr [ecx] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 813b01fa to 813b018e STACK_TEXT: 88644c00 813b01fa 814cf7bc 88644c2c 814bf333 win32k!CMutex::Lock+0x6 88644c0c 814bf333 52f4cf5f 81e216ee a4070ca8 win32k!CAutoMutex::CAutoMutex+0x12 88644c2c 814bf3b6 88644cac 88644c78 81baeaf9 win32k!CMonitorPDO::MonitorInterfaceCallbackInternal+0x30 88644c38 81baeaf9 88644cac 986a14d8 a4070ca8 win32k!CMonitorPDO::MonitorInterfaceCallback+0x10 88644c78 81bc10f4 88644cac 88644ca0 00000000 nt!PnpNotifyDriverCallback+0xa5 88644cd8 81bc2d25 a1ef6eac 88644cf8 8430e0d0 nt!PnpNotifyDeviceClassChange+0x159 88644d00 81a7a02b 8430e0d0 00000000 838c4d48 nt!PnpDeviceEventWorker+0x1e3 88644d50 81c1a66d 00000001 a8b61b76 00000000 nt!ExpWorkerThread+0x10d 88644d90 81acc1d9 81a79f1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!CMutex::Lock+6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc2a2 STACK_COMMAND: .cxr 0xffffffff88644710 ; kb FAILURE_BUCKET_ID: 0x7E_win32k!CMutex::Lock+6 BUCKET_ID: 0x7E_win32k!CMutex::Lock+6 Followup: MachineOwner ---------
giveio.sys Wed Apr 03 22:33:25 1996 It belongs to belongs to the software giveio or ADC Analyzer or SwiftForth or Disspy by unknown. I cannot find the company that produced this driver. If you have any of the above software installed, uninstall it using Revo Uninstaller.
When you have uninstalled this driver, post back.
[QUOTE=CarlTR6;836479]Your mini dump shows a stop error code of 7E. This a hardware or hardware related issue.
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (go to top of page)
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,You have an extremely obsolete driver on your system. Windows 7 does not like old drivers and they can cause memory corruption and BSOD's.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 813b018e, 88644b2c, 88644710} Probably caused by : win32k.sys ( win32k!CMutex::Lock+6 ) Followup: MachineOwner --------- 0: 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: c0000005, The exception code that was not handled Arg2: 813b018e, The address that the exception occurred at Arg3: 88644b2c, Exception Record Address Arg4: 88644710, 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: win32k!CMutex::Lock+6 813b018e ff31 push dword ptr [ecx] EXCEPTION_RECORD: 88644b2c -- (.exr 0xffffffff88644b2c) ExceptionAddress: 813b018e (win32k!CMutex::Lock+0x00000006) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 52f4cf5f Attempt to read from address 52f4cf5f CONTEXT: 88644710 -- (.cxr 0xffffffff88644710) eax=00000000 ebx=986a14d8 ecx=52f4cf5f edx=00000000 esi=88644c24 edi=88644cc0 eip=813b018e esp=88644bf4 ebp=88644c0c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 win32k!CMutex::Lock+0x6: 813b018e ff31 push dword ptr [ecx] ds:0023:52f4cf5f=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe 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: 00000000 EXCEPTION_PARAMETER2: 52f4cf5f READ_ADDRESS: GetPointerFromAddress: unable to read from 81b74718 Unable to read MiSystemVaType memory at 81b54160 52f4cf5f FOLLOWUP_IP: win32k!CMutex::Lock+6 813b018e ff31 push dword ptr [ecx] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 813b01fa to 813b018e STACK_TEXT: 88644c00 813b01fa 814cf7bc 88644c2c 814bf333 win32k!CMutex::Lock+0x6 88644c0c 814bf333 52f4cf5f 81e216ee a4070ca8 win32k!CAutoMutex::CAutoMutex+0x12 88644c2c 814bf3b6 88644cac 88644c78 81baeaf9 win32k!CMonitorPDO::MonitorInterfaceCallbackInternal+0x30 88644c38 81baeaf9 88644cac 986a14d8 a4070ca8 win32k!CMonitorPDO::MonitorInterfaceCallback+0x10 88644c78 81bc10f4 88644cac 88644ca0 00000000 nt!PnpNotifyDriverCallback+0xa5 88644cd8 81bc2d25 a1ef6eac 88644cf8 8430e0d0 nt!PnpNotifyDeviceClassChange+0x159 88644d00 81a7a02b 8430e0d0 00000000 838c4d48 nt!PnpDeviceEventWorker+0x1e3 88644d50 81c1a66d 00000001 a8b61b76 00000000 nt!ExpWorkerThread+0x10d 88644d90 81acc1d9 81a79f1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!CMutex::Lock+6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc2a2 STACK_COMMAND: .cxr 0xffffffff88644710 ; kb FAILURE_BUCKET_ID: 0x7E_win32k!CMutex::Lock+6 BUCKET_ID: 0x7E_win32k!CMutex::Lock+6 Followup: MachineOwner ---------
giveio.sys Wed Apr 03 22:33:25 1996 It belongs to belongs to the software giveio or ADC Analyzer or SwiftForth or Disspy by unknown. I cannot find the company that produced this driver. If you have any of the above software installed, uninstall it using Revo Uninstaller.
When you have uninstalled this driver, post back.
I also found another obsolete driver, nvm62x32.sys Fri Oct 17 17:00:39 2008. This is your NVidia network adapter card driver. This ties in with the error you saw regarding your network adapter.
You have not included your system specs, so I don't know what kind of computer you have. If yours is a laptop, go to the manufacturer's site and look for an updated network adapter driver. Download it and install it. If yours is a desktop and your network adapter card is a separate card, go to Nvidia's website and download the latest driver from there.
This may clear up the problem.
Thanks Carl, very informative.
I had a scoot through device manager and noticed that there wasn't a driver installed for a co-processor, which is the nForce 730i chipset. There should have been so I don't know what happened there...
I found a newer, although unofficial chipset driver on NforcersHQ and so far it seems to be stable.
I'll report back if nothing has changed!
thanks again
D.
PS this is my self built system here;
Intel Xeon 3075 | Scythe Shuriken | Gigabyte GA-E7AUM-DS2H | 2GB Corsair XMS 6400 | Hauppauge Nova-T 500 | Seagate 60Gb Sata 2.5" | WD 250Gb Scorpio 2.5" | LG GGC H20L | Elan Vital 400w Greenerger PSU | Omaura TF8 case | Win 7 Home X86
Thanks for the update and I am glad your system is improving. Did you uninstall that obsolete software? You need to remove that potential conflict.
Please keep us posted, I am hoping we can mark this thread as solved. :)
Quote