

Computer Running Slow and Nothing is Working [Closed]
Started by
Slayer21
, Oct 03 2011 04:02 PM
#46
Posted 11 December 2011 - 11:09 AM


#47
Posted 12 December 2011 - 01:34 PM

your welcome but you did all the heavy lifting on this one...

#48
Posted 12 December 2011 - 02:23 PM

Thanks 
It was just the BSOD I was unsure about, but that tool you posted looks good. May run it next time I ever get one

It was just the BSOD I was unsure about, but that tool you posted looks good. May run it next time I ever get one

#49
Posted 06 January 2012 - 11:49 AM

yep...

#50
Posted 09 January 2012 - 09:57 PM

System Information (local)
--------------------------------------------------------------------------------
computer name: CHRISREAPER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium® Dual-Core CPU T4300 @ 2.10GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4258357248 total
VM: 2147352576, free: 1877594112
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 1/10/2012 3:45:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010912-40934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1 (0x778F226A, 0x0, 0xFFFFFFFF, 0xFFFFF8800B7C4C60)
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 1/10/2012 3:45:33 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1 (0x778F226A, 0x0, 0xFFFFFFFF, 0xFFFFF8800B7C4C60)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
computer name: CHRISREAPER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium® Dual-Core CPU T4300 @ 2.10GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4258357248 total
VM: 2147352576, free: 1877594112
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 1/10/2012 3:45:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010912-40934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1 (0x778F226A, 0x0, 0xFFFFFFFF, 0xFFFFF8800B7C4C60)
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 1/10/2012 3:45:33 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1 (0x778F226A, 0x0, 0xFFFFFFFF, 0xFFFFF8800B7C4C60)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
#51
Posted 10 January 2012 - 11:08 AM

try running chkdsk /r
#52
Posted 12 May 2012 - 09:13 AM

Due to lack of feedback, this topic has been closed.
If you need this topic reopened, please contact a staff member. This applies only to the original topic starter. Everyone else please begin a New Topic.
If you need this topic reopened, please contact a staff member. This applies only to the original topic starter. Everyone else please begin a New Topic.
Similar Topics
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users
As Featured On:






