EDIT: Hi writhziden, looks like you beat me to it.
Welcome to Seven Forums altyfc.
You have had four crashes since 10 Jan '12
The last one is STOP 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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,
This bug check is a very common bug check.
The driver indicated is dxgmms1.sys - DirectX Graphics MMS, this is a Windows system driver and not the cause but the result of the crash.
Code:
*******************************************************************************
* *
* 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: 95908501, The address that the exception occurred at
Arg3: 9ac2bba0, Exception Record Address
Arg4: 9ac2b780, 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:
dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
Followup: MachineOwner
---------
- Make sure you have enough disk space.
- If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
- Try changing video adapters.
- Check with your hardware vendor for any BIOS updates.
- Disable BIOS memory options such as caching or shadowing.
Old drivers that need updated.
Code:
bcm4sbxp.sys Tue Nov 21 20:25:43 2006 - Broadcom Corporation NDIS 5.1 ethernet driver
Go to your Dell Support site and update all drivers including the Broadcom 440x 10/100 Integrated Controller.
Code:
DLABMFSM.SYS Fri Oct 27 07:19:29 2006
DLABOIOM.SYS Fri Oct 27 07:19:24 2006
DLACDBHM.SYS Fri Feb 09 12:05:12 2007
DLADResM.SYS Fri Oct 27 07:20:51 2006
DLAIFS_M.SYS Fri Oct 27 07:18:31 2006
DLAOPIOM.SYS Fri Oct 27 07:20:03 2006
DLAPoolM.SYS Fri Oct 27 07:18:34 2006
DLARTL_M.SYS Fri Feb 09 12:04:41 2007
DDLAUDF_M.SYS Fri Oct 27 07:18:49 2006
DLAUDFAM.SYS Fri Oct 27 07:19:10 2006
DRVMCDB.SYS Sat Jul 22 02:20:31 2006
DRVNDDM.SYS Sat Feb 10 04:33:42 2007
These are Roxio Drag-to-Disc drivers, update drivers or un-install Roxio.
Code:
netw5v32.sys Fri Mar 27 00:10:37 2009 - Intel WiFi Link 5100 AGN wireless driver
Go to your Dell Support site and update the WiFi Link driver.
Code:
VSTAZL3.SYS Thu Oct 16 08:30:03 2008
VSTCNXT3.SYS Thu Oct 16 08:29:13 2008
VSTDPV3.SYS Thu Oct 16 08:32:04 2008
Go to your Dell Support site and update the Conexant SoftK56 Modem drivers.
Noticed some issues with this driver - rapportiaso.sys - Trusteer Ltd. Rapport Security software.
Can you update this driver/software?
System Event Logs.
There are a lot of these.
Code:
Event[923]:
Log Name: System
Source: Service Control Manager
Date: 2012-01-31T09:57:25.996
Event ID: 7034
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Pauls-PC
Description:
The NVIDIA Update Service Daemon service terminated unexpectedly. It has done this 1 time(s).
As mentioned by writhziden, update your graphics card driver.
Code:
Event[2187]:
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2012-01-29T12:45:58.000
Event ID: 10005
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Pauls-PC
Description:
DCOM got error "1053" attempting to start the service RoxMediaDB9 with arguments "" in order to run the server:
{5EFBB572-1CBD-47DA-8BBA-5BAB9CADD108}
Problem with Roxio, update or uninstall.
Code:
Event[2698]:
Log Name: System
Source: Application Popup
Date: 2012-01-27T15:45:49.000
Event ID: 26
Task: N/A
Level: Information
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Pauls-PC
Description:
Application popup: Windows - Application Error : The instruction at 0x5ac00a5a referenced memory at 0x02ef9833. The memory could not be read.
Click on OK to terminate the program
Inconclusive but points to driver or RAM issue.
Application Event Logs.
Code:
Event[10]:
Log Name: Application
Source: Windows Error Reporting
Date: 2012-02-01T09:38:58.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Pauls-PC
Description:
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: daemonu.exe
P2: 1.5.20.0
P3: 4e99198a
P4: daemonu.exe
P5: 1.5.20.0
P6: 4e99198a
P7: 0005f315
P8: c000000d
P9: 00000000
P10:
Attached files:
C:\Users\UpdatusUser.Pauls-PC.000\AppData\Local\Temp\WER5E64.tmp.appcompat.txt
C:\Users\UpdatusUser.Pauls-PC.000\AppData\Local\Temp\WER5F3F.tmp.WERInternalMetadata.xml
C:\Users\UpdatusUser.Pauls-PC.000\AppData\Local\Temp\WER5F50.tmp.hdmp
C:\Users\UpdatusUser.Pauls-PC.000\AppData\Local\Temp\WER60B8.tmp.mdmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_daemonu.exe_e2a490ee3cddc7461fcdae56c822ff2570f9ba9d_cab_114a619f
Analysis symbol:
Rechecking for solution: 0
Report Id: 8f7fcb27-4cb8-11e1-81cc-001c2395d523
Report Status: 4
daemonu.exe - this is from the NVIDIA Settings Update Manager service.
