Thank you for uploading the files. I looked at your five most recent dumps. Two of them are error code 124, a fatal hardware error, two are error 24, NTFS file system, one error code 3B, SYSTEM_SERVICE_EXCEPTION.
Error code 124 usual causes: Hardware, Incompatibility, May be driver corruption.
Error code 24 usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.
Error code 3B usual causes: System service, Device driver, graphics driver, ?memory.
Read this thread for information on your 124 error code: [2-Int] Stop 0x124 - what it means and what to try.
Because you don't have a specific cause of your crashes, you are going to have to troubleshoot. Begin this process by uninstalling Daemon Tools. It has a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. I also notice that Daemon has crashed several times. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select uninstall; do NOT select reinstall.
Here is a free alternative CD virtualization program that does not use the sptd.sys driver.
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
Out of date drivers can and do cause conflicts and memory corruption. I find the following outdated drivers loaded on your system. Those in red font are really obsolete. Update these drivers.
adfs.SYS Thu Jun 26 16:52:37 2008 - Adobe File System Driver.
Adobe. Rename this driver; see Note below.
iaStor.sys Thu Jun 04 21:53:40 2009 - Intel Storage drivers.
http://downloadcenter.intel.com/Default.aspx. Update this driver.
iaStorV.sys Wed Apr 08 12:57:17 2009 - Intel Matrix Storage Manager driver (base).
http://downloadcenter.intel.com/Default.aspx. Update.
PxHlpa64.sys Mon Dec 10 18:49:01 2007 - Sonic CD/DVD driver (used by many different CD/DVD programs)
pxHelp20.sys programs
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.
Note
using Windows Explorer, navigate to C:\Windows\System32\Drivers, locate the driver files, and rename them from .sys to .bak. Reboot and the drivers will not load. This will break whatever software or hardware these drivers are associated with.
how to find drivers -
- I have listed links to most of the drivers in the code box above. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Uninstall sptd.sys, update or rename the drivers above and reboot. Let's how your system runs. Update us and let us know. If you get another BSOD, upload it to us and we start testing hardware.
Because of error code 24, I recommend that you run Check Disk.
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7).
Copy/paste the results into your next post.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50
Debug session time: Thu Dec 2 06:03:52.038 2010 (GMT-5)
System Uptime: 0 days 3:34:22.271
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff880028d35b8, fffff880028d2e20, fffff80002daef8c}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
Followup: Pool_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880028d35b8
Arg3: fffff880028d2e20
Arg4: fffff80002daef8c
Debugging Details:
------------------
EXCEPTION_RECORD: fffff880028d35b8 -- (.exr 0xfffff880028d35b8)
ExceptionAddress: fffff80002daef8c (nt!ExDeferredFreePool+0x0000000000000100)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880028d2e20 -- (.cxr 0xfffff880028d2e20)
rax=fffff8a00b14c240 rbx=0000000000000004 rcx=fffffa8004870710
rdx=fbfff8a00c22a620 rsi=0000000000000000 rdi=fffff8a00e835150
rip=fffff80002daef8c rsp=fffff880028d37f0 rbp=0000000000000000
r8=fbfff8a00c22a620 r9=0000000000000000 r10=fffff8a00c279a80
r11=0000000000000001 r12=fffffa8004870500 r13=0000000000000000
r14=000000000000001d r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!ExDeferredFreePool+0x100:
fffff800`02daef8c 4c8b02 mov r8,qword ptr [rdx] ds:002b:fbfff8a0`0c22a620=????????????????
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_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb30e0
ffffffffffffffff
FOLLOWUP_IP:
nt!ExDeferredFreePool+100
fffff800`02daef8c 4c8b02 mov r8,qword ptr [rdx]
FAULTING_IP:
nt!ExDeferredFreePool+100
fffff800`02daef8c 4c8b02 mov r8,qword ptr [rdx]
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff80002db04c1 to fffff80002daef8c
STACK_TEXT:
fffff880`028d37f0 fffff800`02db04c1 : fffffa80`057b4680 fffff8a0`0c1bf110 fffffa80`0817c428 00000000`00000000 : nt!ExDeferredFreePool+0x100
fffff880`028d3880 fffff880`014b5d2e : 00000000`0b93f35b fffffa80`06666350 00000000`3066744e fffff800`02f6a896 : nt!ExFreePoolWithTag+0x411
fffff880`028d3930 fffff880`0142ffa6 : fffff8a0`0bac39a0 fffff800`02e205a0 fffff880`028d3b01 fffff880`014bc8d5 : Ntfs!NtfsRemoveHashEntry+0xe2
fffff880`028d39c0 fffff880`014ba2cc : fffffa80`09406ad0 fffffa80`06665180 fffff8a0`0bac39a0 fffff8a0`0bac3d38 : Ntfs!NtfsTeardownFromLcb+0x226
fffff880`028d3a50 fffff880`01438882 : fffffa80`09406ad0 fffffa80`09406ad0 fffff8a0`0bac39a0 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`028d3ad0 fffff880`014d1813 : fffffa80`09406ad0 fffff800`02e205a0 fffff8a0`0bac39a0 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`028d3b10 fffff880`014ab38f : fffffa80`09406ad0 fffff8a0`0bac3ad0 fffff8a0`0bac39a0 fffffa80`06665180 : Ntfs!NtfsCommonClose+0x353
fffff880`028d3be0 fffff800`02c88961 : 00000000`00000000 fffff880`017a7000 fffff800`02e20501 00000000`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`028d3cb0 fffff800`02f1fc06 : 00000000`00000000 fffffa80`085fc390 00000000`00000080 fffffa80`0487f890 : nt!ExpWorkerThread+0x111
fffff880`028d3d40 fffff800`02c59c26 : fffff800`02df5e80 fffffa80`085fc390 fffffa80`08758390 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`028d3d80 00000000`00000000 : fffff880`028d4000 fffff880`028ce000 fffff880`028d39f0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+100
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
STACK_COMMAND: .cxr 0xfffff880028d2e20 ; kb
FAILURE_BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+100
BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+100
Followup: Pool_corruption
---------
Debug session time: Mon Dec 6 08:47:16.582 2010 (GMT-5)
System Uptime: 0 days 6:00:40.598
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002fb179a, fffff88009c79770, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+22a )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fb179a, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009c79770, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!CmpKcbCacheLookup+22a
fffff800`02fb179a 3819 cmp byte ptr [rcx],bl
CONTEXT: fffff88009c79770 -- (.cxr 0xfffff88009c79770)
rax=000000002d78189c rbx=0000000000000000 rcx=fbfff8a00c7fe970
rdx=000000000bcd9443 rsi=fffff8a000023978 rdi=fffff88009c7a2c0
rip=fffff80002fb179a rsp=fffff88009c7a140 rbp=fffff8a000023380
r8=0000000000000000 r9=0000000000000000 r10=00000000000001e1
r11=fffff88009c7a2c0 r12=fffff8a005cc9a70 r13=fffff8a005cc9a80
r14=fffff88009c7a2c8 r15=fffff8a005cc9a70
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!CmpKcbCacheLookup+0x22a:
fffff800`02fb179a 3819 cmp byte ptr [rcx],bl ds:002b:fbfff8a0`0c7fe970=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: Skype.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002fb0d08 to fffff80002fb179a
STACK_TEXT:
fffff880`09c7a140 fffff800`02fb0d08 : fffff880`09c7a2c0 fffff880`00000002 fffff880`09c7a6c8 fffff880`09c7a6e0 : nt!CmpKcbCacheLookup+0x22a
fffff880`09c7a230 fffff800`02faef61 : fffff8a0`0ba87ad0 fffff880`09c7a6e0 fffff880`09c7a718 fffff880`09c7a700 : nt!CmpBuildHashStackAndLookupCache+0x328
fffff880`09c7a610 fffff800`02fcee84 : fffff800`02faecc0 00000000`00000000 fffffa80`0959bb10 00000000`00000001 : nt!CmpParseKey+0x2a1
fffff880`09c7a8e0 fffff800`02fd3e4d : fffffa80`0959bb10 fffff880`09c7aa40 00000000`00000040 fffffa80`04912510 : nt!ObpLookupObjectName+0x585
fffff880`09c7a9e0 fffff800`02fb2dcc : 00000000`00000000 00000000`00000000 fffff8a0`0ba87a01 fffff880`09c7aaa8 : nt!ObOpenObjectByName+0x1cd
fffff880`09c7aa90 fffff800`02fb4f0f : 00000000`05f8e778 00000000`0002001f 00000000`05f8e798 00000000`00000000 : nt!CmOpenKey+0x28a
fffff880`09c7abe0 fffff800`02cd4993 : fffffa80`09a59060 fffff880`09c7aca0 00000000`7ef9b000 fffffa80`00000004 : nt!NtOpenKeyEx+0xf
fffff880`09c7ac20 00000000`77630caa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`05f8e738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77630caa
FOLLOWUP_IP:
nt!CmpKcbCacheLookup+22a
fffff800`02fb179a 3819 cmp byte ptr [rcx],bl
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CmpKcbCacheLookup+22a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff88009c79770 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+22a
BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+22a
Followup: MachineOwner
---------
Debug session time: Thu Nov 25 07:39:01.330 2010 (GMT-5)
System Uptime: 0 days 0:00:29.516
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80087b5028, fa000000, 400405}
Probably caused by : hardware
Followup: MachineOwner
---------
0: 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: fffffa80087b5028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fa000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, 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: wininit.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff800`0421fa98 fffff800`02c2e903 : 00000000`00000124 00000000`00000000 fffffa80`087b5028 00000000`fa000000 : nt!KeBugCheckEx
fffff800`0421faa0 fffff800`02deb593 : 00000000`00000001 fffffa80`08c00980 00000000`00000000 fffffa80`08c009d0 : hal!HalBugCheckSystem+0x1e3
fffff800`0421fae0 fffff800`02c2e5c8 : 00000000`00000728 fffffa80`08c00980 fffff800`0421fe70 fffff800`0421fe00 : nt!WheaReportHwError+0x263
fffff800`0421fb40 fffff800`02c2df1a : fffffa80`08c00980 fffff800`0421fe70 fffffa80`08c00980 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`0421fc90 fffff800`02c2ddd5 : 00000000`00000004 00000000`00000001 fffff800`0421fef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`0421fcd0 fffff800`02c21e88 : 00000000`00000080 fffff880`03d44418 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`0421fd00 fffff800`02cd3fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`0421fd30 fffff800`02cd3e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`0421fe70 fffff800`02cdbfad : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03d442e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepNormalAccessCheck+0x17d
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
---------
Quote