Welcome to Seven Forums.
Your first crash today was STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check.
Have you installed any new hardware recently?
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff880012b51f0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
PROCESS_NAME: java.exe
IMAGE_NAME: Ntfs.sys
Update Java
Download Java for Windows
Ntfs is your hard drive file system and may indicate a HDD problem or file corruption.
Disconnect your Seagate external HDD.
Then Run Seagate SeaTools for Windows on your Samsung HDD.
Run both the Short Drive Self Test and Long Drive Self Test.
SeaTools for Windows
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
This bug check is usually caused by drivers that have used improper addresses.
Update drivers as mentioned.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff800029d6d68, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff800029d6d68, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0a0e8
fffff800029d6d68
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
Same as above: STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
[COLOR="Red"]IMAGE_NAME: hardware
MODULE_NAME: hardware[/COLOR]
Two of these, indicating hardware.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0889f2db0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800455a84f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
[COLOR="red"]Could not read faulting driver name[/COLOR]
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb2100
fffff8a0889f2db0
FAULTING_IP:
dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+57
fffff880`0455a84f 833801 cmp dword ptr [rax],1
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
dxgmms1.sys - DirectX Graphics MMS
Inconclusive.
Last crash, as mentioned below uninstall iTunes for testing purposes.
PROCESS_NAME: iPodService.ex
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80082baed90, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80082baed90, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb2100
fffff80082baed90
FAULTING_IP:
+3833373038303538
fffff800`82baed90 ?? ???
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
[COLOR="Red"]PROCESS_NAME: iPodService.ex[/COLOR]
CURRENT_IRQL: 0
TRAP_FRAME: fffff88009c62490 -- (.trap 0xfffff88009c62490)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000020 rbx=0000000000000000 rcx=fffff8a003065510
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80082baed90 rsp=fffff88009c62628 rbp=fffff88009c62788
r8=0000000000000000 r9=0000000000000000 r10=0049005f0067006e
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
fffff800`82baed90 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a2a3bf to fffff80002a7fc40
STACK_TEXT:
fffff880`09c62328 fffff800`02a2a3bf : 00000000`00000050 fffff800`82baed90 00000000`00000008 fffff880`09c62490 : nt!KeBugCheckEx
fffff880`09c62330 fffff800`02a7dd6e : 00000000`00000008 fffff800`82baed90 00000000`00000000 fffffa80`06e60480 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`09c62490 fffff800`82baed90 : fffff800`02d7aed4 fffffa80`06e604a0 fffff880`09c62788 00000000`0000003e : nt!KiPageFault+0x16e
fffff880`09c62628 fffff800`02d7aed4 : fffffa80`06e604a0 fffff880`09c62788 00000000`0000003e 00000000`000007ff : 0xfffff800`82baed90
fffff880`09c62630 fffff800`02d623dd : 00000000`00000000 fffffa80`06e60480 fffffa80`03af19c0 fffffa80`03af19c0 : nt!ObpLookupObjectName+0xc24
fffff880`09c62720 fffff800`02d78e87 : fffff880`09c62960 00000000`00000000 fffffa80`06498c60 00000000`00000080 : nt!ObpInsertOrLocateNamedObject+0xcd
fffff880`09c627e0 fffff800`02d6a416 : fffffa80`00000000 fffffa80`06e604d0 00000000`00000000 fffffa80`06195b00 : nt!ObpCreateHandle+0x687
fffff880`09c628f0 fffff800`02d459c8 : 00000000`0214f1a8 fffff880`09c62ca0 00000000`00000000 00000000`00000001 : nt!ObInsertObjectEx+0x276
fffff880`09c62b40 fffff800`02a7eed3 : fffffa80`06eb1060 00000000`0214f188 fffff880`09c62bc8 00000000`00000000 : nt!NtCreateEvent+0xd8
fffff880`09c62bb0 00000000`7707179a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0214f168 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7707179a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+44791
fffff800`02a2a3bf cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+44791
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+44791
BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+44791
Followup: MachineOwner
---------
Out of date or problem drivers.
As mentioned by JMH
Code:
ASACPI.sys Mon Mar 28 10:30:36 2005
Code:
GEARAspiWDM.sys Mon May 18 20:17:04 2009 - CD-ROM Class Filter Driver by Gear Software Also comes with iTunes
iTunes is known to cause crashes in some Windows 7 systems, uninstall iTunes for testing purposes.
Code:
Rt64win7.sys Thu Feb 26 17:04:13 2009 - Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Got to your motherboard driver site and install all updated drivers.
ASUS M4A78LT-M Driver download
System Event Log info.
This is showing an issue with Apple Mobile Device and/or iTunes.
Code:
Event[703]:
Log Name: System
Source: Service Control Manager
Date: 2012-02-02T01:33:34.112
Event ID: 7031
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Delta
Description:
The Apple Mobile Device service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Event[704]:
Log Name: System
Source: Application Popup
Date: 2012-02-02T01:33:34.000
Event ID: 26
Task: N/A
Level: Information
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Delta
Description:
Application popup: WerFault.exe - Application Error : The instruction at 0x754f6c9c referenced memory at 0x754f6c9c. The memory could not be written.
Click on OK to terminate the program
Can you
download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
