Welcome to the forum, HiddenC; sorry you are having trouble.
To begin your troubleshooting, I suggest that you uninstall Norton using this removal tool: Tool. Norton is known to cause BSOD's on some Win 7 systems. Once you get your system stable, you can try it again; but I do not recommend doing so. Two of your dumps directly blames Norton. Download and install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on.
Error code 1, APC_INDEX_MISMATCH.
BSOD Index
Error code 3B (2X), SYSTEM_SERVICE_EXCEPTION.
Usual causes: System service, Device driver, graphics driver, ?memory.
Error code 24, NTFS_FILE_SYSTEM.
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure'
Error code 19, BAD_POOL_HEADER.
Usual causes: Device driver.
Code:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0321b000 PsLoadedModuleList = 0xfffff800`03458e50
Debug session time: Mon Nov 1 12:19:32.705 2010 (GMT-4)
System Uptime: 0 days 0:11:49.047
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1, {76e0feca, 0, fffe, fffff880077f5ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 0000000076e0feca, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000fffe, Thread->KernelApcDisable
Arg4: fffff880077f5ca0, Previous KernelApcDisable
Debugging Details:
------------------
FAULTING_IP:
+56ae952f019bdd84
00000000`76e0feca ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1
PROCESS_NAME: crashreporter.
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000328aca9 to fffff8000328b740
STACK_TEXT:
fffff880`077f5a68 fffff800`0328aca9 : 00000000`00000001 00000000`76e0feca 00000000`00000000 00000000`0000fffe : nt!KeBugCheckEx
fffff880`077f5a70 fffff800`0328abe0 : fffffa80`041aa060 00000000`0283e168 00000000`00000002 00000000`03aee2a0 : nt!KiBugCheckDispatch+0x69
fffff880`077f5bb0 00000000`76e0feca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`0283e148 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e0feca
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`0328abe0 4883ec50 sub rsp,50h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceExit+245
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245
BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800032f9538, fffff88003dbb150, 0}
Unable to load image \SystemRoot\system32\drivers\NISx64\1201000.025\SYMEFA64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
Probably caused by : SYMEFA64.SYS ( SYMEFA64+3f9e )
Followup: MachineOwner
---------
1: 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: fffff800032f9538, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003dbb150, 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!RtlSplay+a
fffff800`032f9538 488b10 mov rdx,qword ptr [rax]
CONTEXT: fffff88003dbb150 -- (.cxr 0xfffff88003dbb150)
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a000543328
rdx=fffff8a000543338 rsi=fffff8a0002e2208 rdi=fffff88001349230
rip=fffff800032f9538 rsp=fffff88003dbbb28 rbp=0000000000000002
r8=fffff8a00b4882f0 r9=0000000000000020 r10=fffff880009ea660
r11=fffff8a0002e2208 r12=fffff88003dbbcf0 r13=0000000000000001
r14=fffff880010d7a00 r15=0000000000000001
iopl=0 nv up ei pl nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010217
nt!RtlSplay+0xa:
fffff800`032f9538 488b10 mov rdx,qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800032a3cd5 to fffff800032f9538
STACK_TEXT:
fffff880`03dbbb28 fffff800`032a3cd5 : 00000000`00000000 00000000`000007ff fffff8a0`09be1490 fffff880`012b20d0 : nt!RtlSplay+0xa
fffff880`03dbbb30 fffff880`012b1f9e : 00000000`000007ff 00000000`00000020 fffff8a0`0b4aadc0 fffff800`035742fe : nt!RtlDelete+0x5d
fffff880`03dbbb60 00000000`000007ff : 00000000`00000020 fffff8a0`0b4aadc0 fffff800`035742fe fffff8a0`09be14d8 : SYMEFA64+0x3f9e
fffff880`03dbbb68 00000000`00000020 : fffff8a0`0b4aadc0 fffff800`035742fe fffff8a0`09be14d8 fffff880`013669fb : 0x7ff
fffff880`03dbbb70 fffff8a0`0b4aadc0 : fffff800`035742fe fffff8a0`09be14d8 fffff880`013669fb fffff8a0`002e2200 : 0x20
fffff880`03dbbb78 fffff800`035742fe : fffff8a0`09be14d8 fffff880`013669fb fffff8a0`002e2200 fffff880`03dbbd28 : 0xfffff8a0`0b4aadc0
fffff880`03dbbb80 fffff880`012b1d81 : fffff880`03dbbcf0 00000000`00000001 00000000`74704153 fffff8a0`09be1450 : nt!RtlCompareUnicodeString+0x26
fffff880`03dbbbc0 fffff880`03dbbcf0 : 00000000`00000001 00000000`74704153 fffff8a0`09be1450 fffff8a0`09be14e0 : SYMEFA64+0x3d81
fffff880`03dbbbc8 00000000`00000001 : 00000000`74704153 fffff8a0`09be1450 fffff8a0`09be14e0 fffff880`013664ca : 0xfffff880`03dbbcf0
fffff880`03dbbbd0 00000000`74704153 : fffff8a0`09be1450 fffff8a0`09be14e0 fffff880`013664ca fffff8a0`09be1548 : 0x1
fffff880`03dbbbd8 fffff8a0`09be1450 : fffff8a0`09be14e0 fffff880`013664ca fffff8a0`09be1548 00000000`00000000 : 0x74704153
fffff880`03dbbbe0 fffff8a0`09be14e0 : fffff880`013664ca fffff8a0`09be1548 00000000`00000000 00000000`00000001 : 0xfffff8a0`09be1450
fffff880`03dbbbe8 fffff880`013664ca : fffff8a0`09be1548 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffff8a0`09be14e0
fffff880`03dbbbf0 fffff8a0`09be1548 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : SYMEFA64+0xb84ca
fffff880`03dbbbf8 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`0136551c : 0xfffff8a0`09be1548
FOLLOWUP_IP:
SYMEFA64+3f9e
fffff880`012b1f9e ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: SYMEFA64+3f9e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMEFA64
IMAGE_NAME: SYMEFA64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4c48fc4b
STACK_COMMAND: .cxr 0xfffff88003dbb150 ; kb
FAILURE_BUCKET_ID: X64_0x3B_SYMEFA64+3f9e
BUCKET_ID: X64_0x3B_SYMEFA64+3f9e
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff880067d0fe8, fffff880067d0850, fffff8000340890d}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )
Followup: MachineOwner
---------
2: 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: fffff880067d0fe8
Arg3: fffff880067d0850
Arg4: fffff8000340890d
Debugging Details:
------------------
EXCEPTION_RECORD: fffff880067d0fe8 -- (.exr 0xfffff880067d0fe8)
Cannot read Exception record @ fffff880067d0fe8
CONTEXT: fffff880067d0850 -- (.cxr 0xfffff880067d0850)
rax=00530041005c0073 rbx=fffffa80039656d0 rcx=fffff8a00dbee170
rdx=0000000000000004 rsi=0000000000001000 rdi=0000000000000001
rip=fffff8000340890d rsp=fffff880067d1220 rbp=fffffa8003965500
r8=0000000000000001 r9=fffffa80039656d0 r10=fffffa8003965508
r11=0000000000000004 r12=000000000000000a r13=0000000000000000
r14=fffffa8004c91b60 r15=00000000f4636553
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!ExAllocatePoolWithTag+0x53d:
fffff800`0340890d 48895808 mov qword ptr [rax+8],rbx ds:002b:00530041`005c007b=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: Rim.Desktop.ex
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.
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350c0e0
0000000000000000
FOLLOWUP_IP:
Ntfs! ?? ::FNODOBFM::`string'+2cc9
fffff880`0146d3d8 cc int 3
FAULTING_IP:
nt!ExAllocatePoolWithTag+53d
fffff800`0340890d 48895808 mov qword ptr [rax+8],rbx
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000340890d
STACK_TEXT:
fffff880`067cffe8 fffff880`0146d3d8 : 00000000`00000024 00000000`001904fb fffff880`067d0fe8 fffff880`067d0850 : nt!KeBugCheckEx
fffff880`067cfff0 fffff880`01465951 : fffff880`014991b4 fffff880`067d18c0 fffff880`067d1890 fffffa80`047a2010 : Ntfs! ?? ::FNODOBFM::`string'+0x2cc9
fffff880`067d0030 fffff800`03302d1c : 00000000`00000000 fffff8a0`0c3a9680 fffffa80`00100001 fffffa80`08f02f20 : Ntfs! ?? ::FNODOBFM::`string'+0x1446
fffff880`067d0070 fffff880`01465775 : fffff880`014991bc fffff880`067d1890 fffff880`067d0fe8 fffff880`067d1890 : nt!_C_specific_handler+0x8c
fffff880`067d00e0 fffff800`032fa40d : fffff880`014991a8 00000000`00000000 fffff880`0144c000 00000000`00000000 : Ntfs!_GSHandlerCheck_SEH+0x75
fffff880`067d0110 fffff800`03301a90 : fffff880`014991a8 fffff880`067d0188 fffff880`067d0fe8 fffff880`0144c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`067d0140 fffff800`0330e9ef : fffff880`067d0fe8 fffff880`067d0850 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x410
fffff880`067d0820 fffff800`032d3d82 : fffff880`067d0fe8 fffffa80`039656d0 fffff880`067d1090 00000000`00001000 : nt!KiDispatchException+0x16f
fffff880`067d0eb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs! ?? ::FNODOBFM::`string'+2cc9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f
FAILURE_BUCKET_ID: X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2cc9
BUCKET_ID: X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2cc9
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffffa8003962ef0, fffffa8003962ef0, fffffa8003962e70}
Unable to load image \SystemRoot\system32\drivers\NISx64\1201000.025\SRTSP64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 )
Followup: Pool_corruption
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa8003962ef0, the pool entry being checked.
Arg3: fffffa8003962ef0, the read back flink freelist value (should be the same as 2).
Arg4: fffffa8003962e70, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000340bd6f to fffff800032d8740
STACK_TEXT:
fffff880`06f89fd8 fffff800`0340bd6f : 00000000`00000019 00000000`00000003 fffffa80`03962ef0 fffffa80`03962ef0 : nt!KeBugCheckEx
fffff880`06f89fe0 fffff880`06a78d1f : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0xa56
fffff880`06f8a0d0 00000000`00000001 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`01ff6c38 : SRTSP64+0x78d1f
fffff880`06f8a0d8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff8a0`01ff6c38 fffff880`0726c926 : 0x1
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+a56
fffff800`0340bd6f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExDeferredFreePool+a56
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a56
BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a56
Followup: Pool_corruption
---------
All three of these error codes mention device driver in the usual causes. The following outdated drivers are loading on your system. Those in red font are really outdated. Update the drivers below.
AsUpIO.sys – Asus utility driver.
ASUSTeK Computer Inc.-Support-
hamachi.sys Thu Feb 19 05:36:41 2009 -
Hamachi Virtual Network Interface Driver from LogMeIn, Inc. Update or uninstall Logmein.
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 - Virtual Serial Port driver for Blackberry
Research In Motion - Products. I suggest you unistall this software. It is obsolete. Upgrade to Win 7 compatible Blackberry software.
RimUsb_AMD64.sys Wed Apr 16 10:49:32 2008 -
BlackBerry Device Driver is a driver file from Research In Motion Limited belonging to BlackBerry Device Driver. Research In Motion - Products
Uninstall Norton and take care of the above drivers. Reboot and lets see how your system runs. Let us know how your system is doing and upload any new BSOD's and we will go from there.
And you are very welcome.
Quote