Five Reports submitted-Five Different Possibilites
STOP 0x00000024: NTFS_FILE_SYSTEM (go to top of page)
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL (go to top of page)
Usual causes: Device driver
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP (go to top of page)
Usual causes: Memory corruption, Hardware (memory in particular), Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED (go to top of page)
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA (go to top of page)
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Summary of your Dump Reports
Code:
uilt by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x82a46000 PsLoadedModuleList = 0x82b5dc70
Debug session time: Mon Jul 19 10:18:28.841 2010 (GMT-4)
System Uptime: 0 days 0:14:20.510
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904aa, a72a4aa8, a72a47a4, 8ae97411}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x82a03000 PsLoadedModuleList = 0x82b1ac70
Debug session time: Fri Jul 23 04:24:31.862 2010 (GMT-4)
System Uptime: 2 days 15:37:33.191
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {11f7, 2, 0, 8f1364b9}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iSignal+10 )
Followup: MachineOwner
---------
uilt by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x82a4a000 PsLoadedModuleList = 0x82b61c70
Debug session time: Tue Jul 27 17:02:00.887 2010 (GMT-4)
System Uptime: 4 days 12:34:02.542
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 8015b000, 0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
uilt by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x82a51000 PsLoadedModuleList = 0x82b68c70
Debug session time: Tue Jul 27 17:28:26.144 2010 (GMT-4)
System Uptime: 0 days 0:25:20.579
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000092, 82c55ed1, a38859b0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x82a01000 PsLoadedModuleList = 0x82b18c70
Debug session time: Wed Jul 28 09:14:41.713 2010 (GMT-4)
System Uptime: 0 days 3:15:59.245
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {fa7dbd50, 0, 82aef00c, 0}
Could not read faulting driver name
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+108 )
Followup: MachineOwner
---------
Out Dated Drivers
Code:
giveio.sys Wed Apr 03 22:33:25 1996 (
aic78xx.sys Thu Jul 06 16:16:11 2006 (
secdrv.SYS Wed Sep 13 09:18:32 2006 (
speedfan.sys Sun Sep 24 09:28:47 2006 (
Rtlh86.sys Tue Sep 26 07:20:27 2006 (
ASACPI.sys Wed Oct 18 01:44:46 2006 (
peauth.sys Mon Oct 23 04:55:32 2006 (
crcdisk.sys Thu Nov 02 04:52:27 2006 (
VX1000.sys Tue Dec 05 23:04:16 2006 (
nvstor.sys Sat Dec 23 11:07:25 2006 (
L8042Kbd.sys Wed Apr 11 19:29:06 2007 (
spldr.sys Thu Jun 21 20:29:17 2007 (
RtNdPt60.sys Mon Dec 10 21:50:18 2007 (
intelppm.sys Sat Jan 19 00:27:20 2008 (
cdfs.sys Sat Jan 19 00:28:02 2008 (
bowser.sys Sat Jan 19 00:28:26 2008 (
luafv.sys Sat Jan 19 00:30:35 2008 (
msisadrv.sys Sat Jan 19 00:32:51 2008 (
mssmbios.sys Sat Jan 19 00:32:55 2008 (
fileinfo.sys Sat Jan 19 00:34:27 2008 (
Dxapi.sys Sat Jan 19 00:36:12 2008 (
Beep.SYS Sat Jan 19 00:49:10 2008 (
mountmgr.sys Sat Jan 19 00:49:13 2008 (
kbdclass.sys Sat Jan 19 00:49:14 2008 (
mouclass.sys Sat Jan 19 00:49:14 2008 (
i8042prt.sys Sat Jan 19 00:49:17 2008 (
swenum.sys Sat Jan 19 00:49:20 2008 (
serenum.sys Sat Jan 19 00:49:29 2008 (
parport.sys Sat Jan 19 00:49:32 2008 (
serial.sys Sat Jan 19 00:49:34 2008 (
SCSIPORT.SYS Sat Jan 19 00:49:44 2008 (
volmgr.sys Sat Jan 19 00:49:51 2008 (
vga.sys Sat Jan 19 00:52:06 2008 (
VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 (
monitor.sys Sat Jan 19 00:52:19 2008 (
WDFLDR.SYS Sat Jan 19 00:52:19 2008 (
Wdf01000.sys Sat Jan 19 00:52:21 2008 (
WUDFPf.sys Sat Jan 19 00:52:49 2008 (
WUDFRd.sys Sat Jan 19 00:53:04 2008 (
WMILIB.SYS Sat Jan 19 00:53:08 2008 (
HIDPARSE.SYS Sat Jan 19 00:53:16 2008 (
USBD.SYS Sat Jan 19 00:53:17 2008 (
usbccgp.sys Sat Jan 19 00:53:29 2008 (
umbus.sys Sat Jan 19 00:53:40 2008 (
mpsdrv.sys Sat Jan 19 00:54:45 2008 (
rspndr.sys Sat Jan 19 00:55:03 2008 (
lltdio.sys Sat Jan 19 00:55:03 2008 (
tunmp.sys Sat Jan 19 00:55:40 2008 (
netbios.sys Sat Jan 19 00:55:45 2008 (
nsiproxy.sys Sat Jan 19 00:55:50 2008 (
ndistapi.sys Sat Jan 19 00:56:24 2008 (
NDProxy.SYS Sat Jan 19 00:56:28 2008 (
asyncmac.sys Sat Jan 19 00:56:29 2008 (
wanarp.sys Sat Jan 19 00:56:31 2008 (
rasacd.sys Sat Jan 19 00:56:31 2008 (
rasl2tp.sys Sat Jan 19 00:56:33 2008 (
raspptp.sys Sat Jan 19 00:56:34 2008 (
TDI.SYS Sat Jan 19 00:57:10 2008 (
RDPCDD.sys Sat Jan 19 01:01:08 2008 (
tdtcp.sys Sat Jan 19 01:01:08 2008 (
rdpencdd.sys Sat Jan 19 01:01:09 2008 (
TSDDD.dll Sat Jan 19 01:01:09 2008 (
tssecsrv.sys Sat Jan 19 01:01:15 2008 (
serscan.sys Sat Jan 19 01:14:10 2008 (
drmk.sys Sat Jan 19 01:53:02 2008 (
BOOTVID.dll Sat Jan 19 02:27:15 2008 (
As shown above you had several different reports, with their possible causes. I will list the steps that should be taken (in order) to correct the problem. Take one or two steps and test the computer for BSOD's. Then continue. It is my hope that testing the memory and taking the driver verifier will resolve this problem. Do one step and test the computer. If not working properly continue with the next suggestion
Many of the listed suggestions appear on only one dump report. The suggestions listed at the top of my list will most likely correct the problem, since they are applicable to all the reports. It is my hope that the problem will be solved before all the steps are completed. Do one step at a time and test the computer
If overclocking restore normal settings
Download memtest86 and test RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Enable the Driver Verifier
http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html
Run the upgrade advisor to help discover hardware problems
http://www.microsoft.com/Windows/windows-7/get/upgrade-advisor.aspx
Uninstall your current Anti Virus and replace with Microsoft Security Essentials.
http://www.microsoft.com/Security_Essentials/ Uninstall your firewall and use the Windows firewall included with the Windows Anti Virus
Test your hard drive at the manufacturers website.
Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored.
Video card stress test Video Card - Stress Test with Furmark
Scan with your Anti Virus
SFC /scannow
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
How to Find 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 help you 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
- - 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
To remove any left over driver remnants, especially from graphics cards, use driver sweeper http://www.guru3d.com/category/driversweeper/
After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
Remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.
I am sorry for the delay. I put your thread on the side until I had time for the lengthy detailed explanation that your Dump Reports deserve
