Welcome to the forum, Tensu. Sorry you are having problems. To begin, I recommend that you uninstall Daemon Tools. It uses a driver, found in your dump, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select delete; do not select reinstall.
Here is an alternative virtualization program that does not user the sptd.sys driver:
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
Both dumps are error code 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes are Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.
Both dumps directly blame danew.sys, a Razer NewDeathAdder Mouse driver. This driver is out of date, 2009-04-21. Update your mouse drivers or uninstall this mouse and try another one. Razer Support
Another outdated driver was in involved in the crashes, Rt64win7.sys, 2009-06-10: Latest PCIe GBE (GigaBit Ethernet) drivers here: Realtek. Update this driver.
Code:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01c0b000 PsLoadedModuleList = 0xfffff800`01e48e50
Debug session time: Thu Nov 4 14:41:20.840 2010 (GMT-4)
System Uptime: 0 days 4:49:57.606
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000047, fffff80001caa034, fffffa8004689010, 100000000}
Unable to load image \SystemRoot\system32\drivers\danew.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for danew.sys
*** ERROR: Module load completed but symbols could not be loaded for danew.sys
Probably caused by : danew.sys ( danew+6da )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffffffc0000047, The exception code that was not handled
Arg2: fffff80001caa034, The address that the exception occurred at
Arg3: fffffa8004689010, Parameter 0 of the exception
Arg4: 0000000100000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.
FAULTING_IP:
nt!RtlRaiseStatus+18
fffff800`01caa034 488b8424b8010000 mov rax,qword ptr [rsp+1B8h]
EXCEPTION_PARAMETER1: fffffa8004689010
EXCEPTION_PARAMETER2: 0000000100000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff880009f9360 -- (.exr 0xfffff880009f9360)
ExceptionAddress: fffff80001caa034 (nt!RtlRaiseStatus+0x0000000000000018)
ExceptionCode: c0000047
ExceptionFlags: 00000001
NumberParameters: 0
TRAP_FRAME: fffff880009f91a0 -- (.trap 0xfffff880009f91a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009f9400
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001caa034 rsp=fffff880009f9340 rbp=0000000000000000
r8=0000000000000002 r9=0000000000000000 r10=0000000000000000
r11=fffff88005f79ca0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!RtlRaiseStatus+0x18:
fffff800`01caa034 488b8424b8010000 mov rax,qword ptr [rsp+1B8h] ss:0018:fffff880`009f94f8=fffff80001caa034
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001cb5a39 to fffff80001c7b740
STACK_TEXT:
fffff880`009f8898 fffff800`01cb5a39 : 00000000`0000001e ffffffff`c0000047 fffff800`01caa034 fffffa80`04689010 : nt!KeBugCheckEx
fffff880`009f88a0 fffff800`01d7f459 : fffff880`009f9360 fffff880`009f9360 fffff880`009f91a0 fffff880`009f9400 : nt!KiDispatchException+0x1b9
fffff880`009f8f30 fffff800`01c7d3fb : fffff880`009f9360 fffff880`009f0f80 fffffa80`04508dc0 00000000`00000000 : nt!KiRaiseException+0x1b9
fffff880`009f9060 fffff800`01c7a993 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtRaiseException+0x7b
fffff880`009f91a0 fffff800`01caa034 : fffff880`009f9360 fffff880`009f9400 fffffa80`00000001 00000000`0021f1e4 : nt!KiSystemServiceCopyEnd+0x13
fffff880`009f9340 fffff800`01cd6112 : fffffa80`02748b98 fffff880`055a05c2 fffffa80`02748050 fffffa80`04504870 : nt!RtlRaiseStatus+0x18
fffff880`009f98e0 fffff880`05f786da : fffffa80`02af6f30 fffff800`00000000 fffffa80`00000009 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xf5fc
fffff880`009f9960 fffffa80`02af6f30 : fffff800`00000000 fffffa80`00000009 00000000`00000000 00000000`ffffffff : danew+0x6da
fffff880`009f9968 fffff800`00000000 : fffffa80`00000009 00000000`00000000 00000000`ffffffff fffffa80`02748050 : 0xfffffa80`02af6f30
fffff880`009f9970 fffffa80`00000009 : 00000000`00000000 00000000`ffffffff fffffa80`02748050 fffffa80`04315c60 : 0xfffff800`00000000
fffff880`009f9978 00000000`00000000 : 00000000`ffffffff fffffa80`02748050 fffffa80`04315c60 fffff800`01c7dd26 : 0xfffffa80`00000009
STACK_COMMAND: kb
FOLLOWUP_IP:
danew+6da
fffff880`05f786da ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: danew+6da
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: danew
IMAGE_NAME: danew.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ba87dcd
FAILURE_BUCKET_ID: X64_0x1E_danew+6da
BUCKET_ID: X64_0x1E_danew+6da
Followup: MachineOwner
---------
Uninstall Daemon tools, take care of those two drivers and let's see how your system does. Please let us know. If you get another BSOD, upload it and we will go from there
Quote