Blue screen of death in windows xp: Stop 0xD1

every time I tried to start out of the hibernation mode, I get the blue screen.  I restarted by using the last known good configuration.  When the computer is started, the screen of support from microsoft to stop 0x000000D1 comes.  I followed the instructions for updating the Gv3.sys, but it indicates that windows did not find a better match for your hardware.   I'm under SP3, then why it wont update intelppm.sys?

Many STOP error 0xD1.  Run the driver verifier according to the instructions on this link: http://www.carrona.org/verifier.html

Nothing unusual in the file MSINFO32 - but XP doesn't have much info here.

18 and 19 January 2012 errors blame gv3.sys - a driver of Intel processor.  Ensure that you have all the Windows updates and update your drivers for your motherboard chipset.  If the BSOD persists, try the free CPU stress tests at this link (try the other diagnoses also): http://www.carrona.org/hwdiag.html

It seems that you have both McAfee and Norton installed on this system.  Follow these steps:
[b] [u] removal of Anti-Virus: [/ b] [/ u]
Follow these steps:
-Download a free antivirus for testing purposes: http://www.carrona.org/freeav.html
-uninstall the Norton [B] [/ b] of your system (you can reinstall, if desired, when we finished troubleshooting)
-remove the remnants of Norton [B] [/ b] using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
-Uninstall McAfee [B] [/ b] of your system (you can reinstall, if desired, when we finished troubleshooting)
-remove the remains of McAfee [B] [/ b] using this free tool: http://service.mcafee.com/FAQDocument.aspx?id=TS100507
-[b] [u]IMMEDIATELY[/ b] [/ u] install and update the free antivirus, and then check to make sure that the Windows Firewall is enabled.
-check to see if this corrects the BSOD
[b] [u] NOTES: [/ u] NEVER [/ b] run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

Just a note for later.  See the underclock it is stated in some of the dump below files...
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 599
******************************************************************************************
BSOD BUGCHECK SUMMARY [/ U] [/ COLOR] [/ SIZE] [/ DO]
[code] [font = lucida console]
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini011912-03.dmp]
By: 2600.xpsp_sp3_gdr.111025 - 1629
The debugging session: 19:20:50.917 Thu 19 Jan 2012 (UTC - 05:00)
System Uptime: 0 days 1:16:21.524
Probably caused by: gv3.sys (gv3! SetPerfLevelGeneric + 19)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: Idle
FAILURE_BUCKET_ID: 0xD1_gv3! SetPerfLevelGeneric + 19
Code 100000 1 Bugcheck
Arguments 0000000c 00000000 f8d98a89 000000ff
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini011912-02.dmp]
By: 2600.xpsp_sp3_gdr.111025 - 1629
The debugging session: 12:45:47.442 Thu 19 Jan 2012 (UTC - 05:00)
System Uptime: 0 days 0:40:15.035
Probably caused by: gv3.sys (gv3! SetPerfLevelGeneric + 19)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: Idle
FAILURE_BUCKET_ID: 0xD1_gv3! SetPerfLevelGeneric + 19
Code 100000 1 Bugcheck
Arguments 0000000 00000000 00000002 f8bc0a89 c
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini011912-01.dmp]
By: 2600.xpsp_sp3_gdr.111025 - 1629
The debugging session: 11:59:04.385 Thu 19 Jan 2012 (UTC - 05:00)
System Uptime: 0 days 15:34:47.001
Probably caused by: gv3.sys (gv3! SetPerfLevelGeneric + 19)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: Idle
FAILURE_BUCKET_ID: 0xD1_gv3! SetPerfLevelGeneric + 19
Code 100000 1 Bugcheck
Arguments 0000000 00000000 00000002 f8ea8a89 c
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini011812-01.dmp]
By: 2600.xpsp_sp3_gdr.111025 - 1629
The debugging session: 20:22:37.570 sea 18 Jan 2012 (UTC - 05:00)
System Uptime: 2 days 4:24:49.190
Probably caused by: gv3.sys (gv3! SetPerfLevelGeneric + 19)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: Idle
FAILURE_BUCKET_ID: 0xD1_gv3! SetPerfLevelGeneric + 19
Code 100000 1 Bugcheck
Arguments 0000000 00000000 00000002 f8e88a89 c
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini011512-01.dmp]
By: 2600.xpsp_sp3_gdr.111025 - 1629
The debugging session: 19:47:42.590 Sun 15 Jan 2012 (UTC - 05:00)
System: 12 days 22:02:45.527
Probably caused by: usbehci.sys (usbehci! EHCI_MarkOldQueueHeadsInvalid + 67)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: System
FAILURE_BUCKET_ID: 0xD1_usbehci! EHCI_MarkOldQueueHeadsInvalid + 67
Code 100000 1 Bugcheck
Arguments f3387158 00000002 00000000 f8eb2d5d
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini121211-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 19:56:32.590 Mon 12 Dec 2011 (UTC - 05:00)
System Uptime: 3 days 13:28:11.198
Probably caused by: usbehci.sys (usbehci! EHCI_MarkOldQueueHeadsInvalid + 67)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: System
FAILURE_BUCKET_ID: 0xD1_usbehci! EHCI_MarkOldQueueHeadsInvalid + 67
Code 100000 1 Bugcheck
Arguments f2310158 00000002 00000000 f8eaad5d
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini120411-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 12:51:19.670 sat Dec 3, 2011 (UTC - 05:00)
System Uptime: 1 day 14:59:12.280
Probably caused by: usbehci.sys (usbehci! EHCI_MarkOldQueueHeadsInvalid + 67)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: System
FAILURE_BUCKET_ID: 0xD1_usbehci! EHCI_MarkOldQueueHeadsInvalid + 67
Code 100000 1 Bugcheck
Arguments f33b7158 00000002 00000000 f8ea2d5d
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini111911-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 04:20:13.000 sam 19 Nov 2011 (UTC - 05:00)
System Uptime: 4 days 4:02:45.678
Probably caused by: gv3.sys (gv3! SetPerfLevelGeneric + 19)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: iexplore.exe
FAILURE_BUCKET_ID: 0xD1_gv3! SetPerfLevelGeneric + 19
Code 100000 1 Bugcheck
Arguments 0000000 00000000 00000002 f8e80a89 c
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini111311-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 15:45:17.810 Sun 13 Nov 2011 (UTC - 05:00)
System Uptime: 1 day 3:24:01.410
WARNING: Unable to verify timestamp for SYMTDI. SYS
ERROR: Module load completed but symbols cannot be loaded for SYMTDI. SYS
WARNING: Unable to verify timestamp for KL1 Device wpsdrvnt.sys
ERROR: Module load completed but symbols can be loaded for KL1 Device wpsdrvnt.sys
Probably caused by: SYMTDI. SYS (SYMTDI + 12186)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: ccSvcHst.exe
FAILURE_BUCKET_ID: 0xD1_SYMTDI + 12186
Code 100000 1 Bugcheck
Arguments fefefefe 00000002 00000000 f6f63df4
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini111111-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 13:22:54.590 Fri 11 Nov 2011 (UTC - 05:00)
System Uptime: 1 day 17:46:52.200
Probably caused by: usbehci.sys (usbehci! EHCI_MarkOldQueueHeadsInvalid + 67)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: System
FAILURE_BUCKET_ID: 0xD1_usbehci! EHCI_MarkOldQueueHeadsInvalid + 67
Code 100000 1 Bugcheck
Arguments f6ceb158 00000002 00000000 f8ea2d5d
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini110811-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 23:24:54.636 Mar 8 Nov 2011 (UTC - 05:00)
System Uptime: 0 days 0:12:26.003
Probably caused by: gv3.sys (gv3! SetPerfLevelGeneric + 19)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
NOM_PROCESSUS: BCMWLTRY. EXE
FAILURE_BUCKET_ID: 0xD1_gv3! SetPerfLevelGeneric + 19
Code 100000 1 Bugcheck
Arguments 0000000 00000000 00000002 f8e90a89 c
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini101111-02.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 14:58:50.995 Mar 11 Oct 2011 (UTC - 05:00)
System Uptime: 0 days 3:15:13.958
WARNING: Unable to verify timestamp for C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT. SYS
ERROR: Module load completed but symbols cannot be loaded for C:\WINDOWS\SYSTEM32\DRIVERS\SYMEVENT. SYS
Probably caused by: Pool_Corruption (nt! ExDeferredFreePool + 158)
BUGCHECK_STR: 0xC5_2
DEFAULT_BUCKET_ID: DRIVER_FAULT
Nom_processus: mfevtps.exe
FAILURE_BUCKET_ID: 0xC5_2_nt! ExDeferredFreePool + 158
Error checking code 5 100000
Arguments 00000002 00000001 8054c 009 fefeff02
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini101111-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 11:42:29.610 Mar 11 Oct 2011 (UTC - 05:00)
System Uptime: 1 day 0:48:28.664
Probably caused by: usbehci.sys (usbehci! EHCI_MarkOldQueueHeadsInvalid + 67)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: System
FAILURE_BUCKET_ID: 0xD1_usbehci! EHCI_MarkOldQueueHeadsInvalid + 67
Code 100000 1 Bugcheck
Arguments ff7c6158 00000002 00000000 f8eaad5d
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini101011-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 10:53:51.551 MON 10 Oct 2011 (UTC - 05:00)
System Uptime: 1 day 13:29:17.170
Probably caused by: ntoskrnl.exe (nt! KiFastCallEntry + a4)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0 X 50
Nom_processus: svchost.exe
FAILURE_BUCKET_ID: 0x50_nt! KiFastCallEntry + a4
Verification of error code 10000050
Arguments fefeff06 00000000 00000000 804de798
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini100811-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 21:22:40.610 Sam 8 Oct 2011 (UTC - 05:00)
System Uptime: 2 days 9:02:26.848
Probably caused by: usbehci.sys (usbehci! EHCI_MarkOldQueueHeadsInvalid + 67)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: System
FAILURE_BUCKET_ID: 0xD1_usbehci! EHCI_MarkOldQueueHeadsInvalid + 67
Code 100000 1 Bugcheck
Arguments f296f158 00000002 00000000 f8ef2d5d
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 1598
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading dump file [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\Mini100611-01.dmp]
By: 2600.xpsp_sp3_gdr.101209 - 1647
The debugging session: 12:19:42.610 game 6 Oct 2011 (UTC - 05:00)
System Uptime: 0 days 1:06:37.068
Probably caused by: usbehci.sys (usbehci! EHCI_MarkOldQueueHeadsInvalid + 67)
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0XD1
Nom_processus: System
FAILURE_BUCKET_ID: 0xD1_usbehci! EHCI_MarkOldQueueHeadsInvalid + 67
Code 100000 1 Bugcheck
Arguments f276f158 00000002 00000000 f8f0ad5d
BiosVersion = A08
BiosReleaseDate = 26/04/2004
CPUID: "Intel (r) Pentium (r) M processor 1.60 GHz"
MaxSpeed: 1600
CurrentSpeed: 599
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
[/ do] [/ code]

Tags: Windows

Similar Questions

  • Blue screen of death. Windows xp family on dell e520

    I got the blue screen of death since 10/17 and have found no solution.
    I can't get into safe mode (networking, command, prompt etc.), nor any other
    f8 options option in the menu. I can't change the cache or shading where the blue screen would recommend either.
    Can anyone help

    It seems that this happened during the night with the automatic updates. my brother got up and the screen is stuck on windows stops. It was restarted by pressing the button and this screen comes up with codes such as 0 x 00000050 or 0x0000007e and other codes. nothing I've tried works. I can't get any internet access when I connect to this computer. What are my other options. my mother also lost the discs when this is supplied with the computer.

    any help will be great...

    read this http://www.asklaptopfreak.com/laptop-notebook-help/2006/06/04/blue-screen-when-start-computer/

    some good stuff there for you to try

  • Blue Screen of Death After Windows Update

    I was out of the House one night and while outside, my cell phone went through a routine Windows Update and restarted (what he did specifically I'm not aware of). Unfortunately, when I came back, I met a blue screen of death. I tried a system repair and restoration of the system, and none of them worked. I'm typing this from my wife's computer as we speak. I am very anxious, and I would like to use my laptop again. If anyone can help, please reply as soon as possible.

    Visit the Microsoft Solution Center and antivirus security for resources and tools to keep your PC safe and healthy. If you have problems with the installation of the update itself, visit the Microsoft Update Support for resources and tools to keep your PC updated with the latest updates.

    MS - MVP - Elephant Boy computers - don't panic!

  • Blue Screen Of Death with Windows Vista

    I am running Windows Vista and after trying to update a NVIDIA Geforce driver, my computer will not start at the top and comes up with the "blue screen of death/Disconnections. Initially it started, but icons were very large and I could finally get the right size. Thought that there was a problem with the driver compatibililty and deleted driver (I think), not knowing that I would not be able to find the original driver. Restarted and it is when I got the dreaded "BSOD" and knew with my computer knowledge, I was in trouble. Tried to reboot and then restart with the Windows disk, with the same results. Past to start in safe mode, normal mode, etc... and does not boot in any mode, when eneter is pushed (of your choice) Unit acts as if it starts successfully, with the small bar down Center of screen scrolling as it should, but then the BOSD rises. Support, not much luck, worked with NVIDIA replaced card video, restarted, same result. Need help please.

    Hello

    Here's a problem similar to yours that I help a CO-OP with.

    See if it helps you too.

    http://answers.Microsoft.com/en-us/Windows/Forum/windows_vista-system/unable-to-successfully-boot-syste-after-trying-to/14523396-5c88-4460-A29E-87d03fa00074

    See you soon.

  • Lenovo z50-70 used power up after the blue screen of death on windows 10

    Hello Sir/mam,.

    My laptop wouldn't boot / lights up once the blue screen of death appeared this morning.

    I am browsing and suddenly the blue screen appeared and I remember in the written form 'system error' and the laptop will restart. something like that. I can not really remembered the exact error. But I'm sure it's the BSOD.

    When I tried the laptop powered, the power light was for about 1-2 sec even with the fan, and then they continue or let's just say that it will not feed. I've done several times, but the result is the same.

    I also tried the solution on what I read here in the forum. "Press and hold the power down for about 30 seconds."

    I tried too many times but it won't work.

    Please help me to LENOVO.

    Thank you

    Thanks for the reply. I already solve the problem. I already did what you said so many times, but did not work.

    I just discovered that one of the ram is not working. That's all /... case closed

  • repeated the blue screen of death in windows vista.

    hope that someone would be able to give me easy understandable advice? It is all the information that I received the error report that I apologise for the collage what anyone who is not relevant, but not'm not computer savvy.

    Thanks gavin.

    Problem event name: BlueScreen

    The system version: 6.0.6002.2.2.0.768.3

    Locale ID: 2057

    More information about the problem:

    BCCode: 1a

    BCP1: 00000402

    BCP2: C008BFE8

    BCP3: 83 53866

    BCP4: 86457198

    OS version: 6_0_6002

    Service Pack: 2_0

    Product: 768_1

    Files helping to describe the problem:

    C:\Windows\Minidump\Mini011610-01.dmp

    C:\Users\gavin\AppData\Local\Temp\WER-47408-0.SysData.XML

    C:\Users\gavin\AppData\Local\Temp\WER618.tmp.version.txt

    Read our privacy statement:

     

    Hello

    If memory couldn't then 'some' of it is likely to be bad - there could be other causes for memory failed
    test as BIOS and motherboard issues but those are rare. If you have several sticks of RAM memory
    You can try to turn off and exchanging leaving them the primary slots populated to see what stick is
    in fact, evil.

    The RAM of your old machine is not likely to be compatible with the new machine. A real computer store
    can replace RAM quickly.

    I hope this helps.
    Rob - bicycle - Mark Twain said it is good.

  • How to fix the BSOD (blue screen of death) on windows 8 cause of tcpip.sys

    I bought a Hp Pavilion h8 - 1360t last year in 2012. He had Windows 7 installed on it, but I have upgraded to Windows 8 pro X 64 some time earlier this year. At first, everything was going well until I kept getting BSOD every few hours or so at random. The BSOD said that tcpip.sys driver_irql_not_less_or_equal. As a first step, I try to understand me and only probably caused by: (tcpip + 65 95 d) tcpip.sys with the debugger tool can someone help me or tell me what it is.

    WP

    Often of tcpip.sys errors are caused by the application of malicious programs installed (in your case AVG).  I delete AVG and use the built in Defender (at least for testing)

    If you continue to crash after removing AVG download DMP files and we can get more aggressive with them.

  • Blue screen of death after the update installed at startup upward.

    I have windows xp sp3 after installed updates don't know which ones, because the installed when I stop and 52 of them there I now get a blue screen of death which says:

    Stop: c000007b {bad image}

    The application or DLL? \c:\windows\system32\winsrv.dll is not a valid windows image. Please check this against your installation diskette.

    I can't go to the safe mode get the same error and same with the last known good configuration. I can't even to safe mode command prompt, system, or debug mode recovery still giving me the same error. I repaired windows 3 times already and the same thing happens each time after that some update that I don't know he messes all this. Give me advice. I have antivirus Iola system mechanic. I think just to wipe the entire disk and do a clean install if you do not have anything else to tell me I'll do it, but I don't know if that even the problem will be solved because there seems to be a problem of windows software update. I also notice from the internet explorer 7 installed it stops working a few flashes upwards on you whenever you try to open it up if it's maybe part of the problem too. I do not plan to let internet 7 install go into all this time.

    Install the updates one at a time or 5 at the time may not be a bad idea.  Then when it breaks watch you and see if one of those is eager to replace your winsrv.dll file.

    You said you DO or DO NOT have to System Mechanic configured to run at startup?  Sometimes after installation of the updates, who see the new files (and if they are obsolete), can interpret the new legitimate files to be a threat.  If you could get started and uninstall that (at least temporarily) that would eliminate this possibility of this equation of many variables.

    The Dell has a number of service tag sticker and if so what does it say?  You can search for things by service number

    You should make a bootable CD of XP (no XP media required) Recovery Console.

    You see, Microsoft support engineers won't tell you how to do this either - since there is not an article of KB Microsoft Bing and link to.

    If you have a SATA drive, which will give you another challenge because you need to maybe get into BIOS and temporarily change the disk other than SATA configuration mode so the Recovery Console will be able to see, replace the suspicious winsrv.dll file, change the SATA drive and reboot...

    First, do the XP Recovery CD of Console and if you are able to use a system of work to ensure that the CD you made at least boots (you don't have to "do" something with it), which would be a good thing.

    Here's how:

    If you have no XP bootable media (or aren't sure you have) create a bootable XP Recovery CD of Console and do not forget.

    This is not the same as recovery disks that might have come with the acquisition of the system store.

    You can make a bootable Recovery Console CD by downloading an ISO file and burn it to a CD.

    The ISO bootable image file you need to download is called:

    xp_rec_con. ISO

    Download the ISO from here:

    http://www.mediafire.com/?ueyyzfymmig

    Use a new CD and this simple and free program to burn your ISO file and create your bootable CD:

    http://www.ImgBurn.com/

    When you install ImgBurn, DO NOT install the Ask toolbar.

    Here are some instructions for ImgBurn:

    http://Forum.ImgBurn.com/index.php?showtopic=61

    It would be a good idea to test your bootable CD on a computer running.

    You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

    When you start on the CD, follow the instructions:

    Press any key to boot from CD...

    Installing Windows... going to pronounce.

    Press 'R' to enter the Recovery Console.

    Select the installation that you want to access (usually 1: C:\WINDOWS)

    You may be asked to enter the password (usually empty).

    You should be in the folder C:\WINDOWS.  It's the same as the

    C:\Windows folder that you see in Solution Explorer.

    The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

    For a list of the commands in the Recovery Console, type help at the prompt of commands or read on here XP Recovery Console:

    http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

  • You are looking for a solution for Blue Screen of Death

    I am looking for a solution to a Blue Screen of Death with a Message Stop: 0x0000007F (0 x 0000008, 0x803d3130, 0 x 00000000, 0 x 00000000).

    I use a Lenovo T61 with Vista 32 bit...
    Thank you!!!

    It can help to look at the files minidump against accidents with a debugger.

    Can you zip the minidump in the C:\Windows\Minidump folder files and (provide link) available via Windows Live SkyDrive or similar site?

    The following link has information about the use of Windows Live SkyDrive:

    http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

    If you have problems to compress the minidump files copy the minidump files to another location such as a folder on the desktop

    In addition, you do not necessarily have compress the minidump files, you can download one at a time.

  • HP probook 4720 graph blue screen of death

    I have a HP probook 4720 s (product #: WT238EA #ACQ). I upgraded my 6 GB RAM.

    My problem. The other day, I was busy playing a game when the computer froze, then off while she turned on a small blue screen appeared briefly. I restarted the laptop and everything seemed fine, I left the computer for a few minutes and when I came back the screen was turned off completely but the computer was working normally. No key or anything would be to put the screen back on.

    After this event I tried to put the laptop on it would start everytime (HHD spin, CPU fan, HARD drive light flashing for a little and then stop, but the screen remains completely black with no blue backlight). I tried the hard reset and a number of other things like checking if the RAM has been correctly connected, the screen stays off.

    I decided to connect the laptop to an external monitor and I could finally display on the monitor, but still, it would display on the screen of the laptop. After loading the windows emblem the dreaded blue screen of death appears with a STOP error message 0 x 00000116 who, after some research, seems to be the graphics driver. After the start of the security system and roll back the standard graphics driver VGA adapter of the windows system 7 was then able to boot into normal mode. I tried to reinstall the HD 5470 graphics driver but the blue screen of death continues to be displayed. I completely rebooted the OS without result.

    I unplugged the screen of laptop computers to the motherboard without the graphics driver loaded, which did not cause a beep but on the monitor external when I plugged it. I tried the same thing with the loaded graphics driver, still no beeps were heard and when I plugged the external monitor blue screen appeared.

    Tests I had tried, I think there must be a problem with the graphics card itself as the blue screen of death poster only when the graphics card driver is loaded.

    Could you please say how you feel, I do, a help on this would be much appreciated. I have appolagize for the long message.

    Kind regards

    Byron

    Problem solved. The MOSFET chip had stopped working, a fast replacement and the screen and everything worked perfectly!

  • Blue screen of death (stop 0x0000007B) after April Windows Update on XP Home.

    My machine (Dell Dimension 3100 with XP Home) home is set for automatic recovery of Windows updates. I reload often, but when I was forced to start again last week, I got the blue screen of death. Apart from the general BSOD error message, I got the stop code:

    STOP 0x0000007B...

    I forgot the subsequent stop codes, but search recall I was doing on them indicated drivers disk or storage-related problem.

    I ran all sorts of Dell diagnostics on my hardware, get absolutely no problem. Scan of a viral infection was also negative. A colleague help out me suggested removing the updates of Windows of April, he did help and usefulness of the ERD. XP loaded and started after that, if I had to go through a process of slooow restart for most updates. My office also now charge many times slower - I suspect drivers and services can't find what they expect to find and take considerable time to make mistakes.

    My Dell has a range of Intel (RAID-1) matrix installed. I strongly suspect that this pilot was in trouble after the April update Windows Update.

    So, what should I do to prevent this from happening again? I don't know the specific fix involved. I have disabled the automatic updates for now.

    TIA

    Rick

    Complete sweep of Kaspersky AV, booted from the CD, turned up negative, so I doubt that it is an infection.

    I'm sorry, but this does not exclude the possibility of infection. See step # 3 in my previous response, or contact Ms. PCSafety for assistance.

    Or see http://msdn.microsoft.com/en-us/library/ff559218 (VS.85) .aspx and/or http://aumha.org/a/stop.php#0x7b for more troubleshooting ideas.

    Or if you let Windows Update to install an update for the driver (never a good idea), try a roll-back of pilot.

    ~ Robear Dyer (PA Bear) ~ MS MVP (that is to say, mail, security, Windows & Update Services) since 2002 ~ WARNING: MS MVPs represent or work for Microsoft

  • Blue Screen of Death and stop working after plugging my Razer Kraken Chroma 7.1 (windows 7)

    (Which mean that I speak French, sorry for my English)

    Hi, I have a problem. When I plug my headphones Razer Kraken 7.1 Chroma, awhile, they just stop working. I heard a noise and that they stop working. I must unplug and plug my headphones so I want them to work again. And this thing is happening very randomly! As for 5 minutes, I have déplug and reconnect but some times, it's job for 20 minutes without problem.

    Also, I feel that if I plug my headphones too fast after this problem, the blue screen of death appear.

    I uninstall and reinstall a lot of time, but don't change anything.

    I have 2 computer: this problems happens on my computer which has windows 7, but when I'm on my pc which has windows 10 all work.

    So thanks to you. Sorry for my English ^^

    Logitech Inc QuickCam LVcKap64.sys associates.  Yours is from 2007.  I would completely remove the software and install a new copy of the most recent driver available.

  • Qosmio F20 blue screen of death after stop

    Hello

    I get the blue screen of death after a stop on my laptop Qosmio F20.

    The error is IRQ_NOT_LESS_OR_EQUAL.

    I guess that's somehow connected to the tv tuner card.

    I tried to restore the system - not good. After the restoration for some time, it was OK. But then again appeared BSOD.

    Sometimes, it also appears when I connect USB hard drives or even when I insert the DVD disc.
    And for shure every time I stop to laptop.

    Anyone have any ideas?

    Hello

    This is my personal opinion;
    I think it's a memory problem!

    Why, because it of very difficult to reproduce this error message and it looks like this BSOD happens without the use of hardware or special software

    I have gogoled for this error message and I had a lot of success!
    I read in various forums on this issue, and especially a fault memory has been one reason why the BSOD appeared.

    But someone suggested to disabled the pagefile... Probably, you should check out these tips:
    http://joelmama.com/2006/10/16/Windows-XP-BSOD-error-IRQ_NOT_LESS_OR_EQUAL/

    Good luck

  • Windows 7 clean installation Blue Screen of Death (BSoD) on a loop of reboot

    Aloha everyone,
    I did an install customized windows 7 on a new Western Digital 1 TB sata hard drive, which has been formatted, partitioned, scandisk, and a ntfs c drive was created prior to installation.
    The installation ended safely.  I then install my screen reader, Window-Eyes, requiring a reboot.  After the reboot, I started to install critical updates to Windows.  On my fourth update and restarting, I got the blue screen of death, that of some people call a BSoD.  I rebooted and Windows itself restored to a previous state of good, of my just accept the default choice.  Then the rear computer works, but if I stop, restart I get the blue screen of death (BSod) is back, and the loop begins again, i.e. windows restores good condition that works well, until you stop, but on reboot - BSoD is BACK!
    I removed the automatic update option, I disabled ScanDisk, drivers updated, bluetooth devices, deactivated sideshow, etc., without any positive result.  I called Microsoft for assisstance and the technician acted like this isn't a known issue, but he assured me that he could solve the problem.  He took control of my computer remotely and do not tell me anything except that the computer would check and repair any problem on reboot, and if he did does not resolve the problem, I have to remember.  The computer has rebooted without the BSod, but I stopped to check if the loop went, and it is not!  To restart the BSOd was back.  It is to note that if I put the computer to sleep, I get a clean start, but stop, restart or hibernation, I get the blue screen of death (BSoD)!
    It is a Dell Dimension XPS 420 with a intel Q6600 processer, 3 GB of ddr2 memory, which came with OS Vista Home premium 32-bit.  The Vista system, the last time I got a BSoD has been for more than a year.

    After researching this problem on Google, it appears that there is a problem without a solution.
    I ran "which has crashed, you can get:
    http://www.resplendence.com/downloads

    The following accident report:
    Monday, December 21, 2009 23:23:44 your computer crashed
    This was probably caused by the following module:
    Wininit.exe
    Bug check code: 0xF4 (0x3, 0xFFFFFA800573B060, 0xFFFFFA800573B340, 0xFFFFF80002D91240)
    Error:
    CRITICAL_OBJECT_TERMINATION
    Empty the file: C:\Windows\Minidump\122109-16972-01.dmp
    file path: C:\Windows\system32\wininit.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: Application to Windows startup
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Monday, December 21, 2009 20:22:10 crashed your computer
    This was probably caused by the following module:
    Ntoskrnl.exe
    Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
    Error:
    PAGE_FAULT_IN_NONPAGED_AREA
    Empty the file: C:\Windows\Minidump\122109-33306-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Sunday, December 20, 2009 15:28:42 crashed your computer
    This was probably caused by the following module:
    Ntoskrnl.exe
    Verification of error code: 0 x 50 (1, 0xFFFFF80002ADC00C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
    Error:
    PAGE_FAULT_IN_NONPAGED_AREA
    Empty the file: C:\Windows\Minidump\122009-17565-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Thursday, December 17, 2009 12:27:45 AM your computer crashed
    This was probably caused by the following module:
    Ntoskrnl.exe
    Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
    Error:
    PAGE_FAULT_IN_NONPAGED_AREA
    Empty the file: C:\Windows\Minidump\121609-28111-01.dmp
    file path: C:\Windows\system32\ntoskrnl.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: NT Kernel System &
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Monday, December 14, 2009 20:59:21 crashed your computer
    This was probably caused by the following module:
    Wininit.exe
    Bug check code: 0xF4 (0x3, 0xFFFFFA80059A3060, 0xFFFFFA80059A3340, 0xFFFFF80002DC4240)
    Error:
    CRITICAL_OBJECT_TERMINATION
    Empty the file: C:\Windows\Minidump\121409-25506-01.dmp
    file path: C:\Windows\system32\wininit.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: Application to Windows startup
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Sunday, December 13, 2009 02:17:55 your computer crashed
    This was probably caused by the following module:
    Wininit.exe
    Bug check code: 0xF4 (0x3, 0xFFFFFA80058A4060, 0xFFFFFA80058A4340, 0xFFFFF80002D8A240)
    Error:
    CRITICAL_OBJECT_TERMINATION
    Empty the file: C:\Windows\Minidump\121209-24648-01.dmp
    file path: C:\Windows\system32\wininit.exe
    product:
    Microsoft® Windows® operating system
    company:
    Microsoft Corporation
    Description: Application to Windows startup
    The accident took place in a standard Microsoft module. Your system configuration can
    be incorrect, perhaps the culprit may be another driver on your system which cannot
    be identified at this time.
    Conclusion
    6 dumps were found and analysed. Note that it is not always possible to
    assert with certainty whether a reported driver is really responsible for crashing
    your system or that the cause is in another module. However, it is suggested
    looking for updates for the products that these drivers belong to and regularly
    Visit the Windows Update or activate the automatic updates for Windows. In the case of a piece of
    defective material is in trouble, a Google search on the bug control
    Errors, as well as the name of the model and brand of your computer can help you investigate
    This further.
    end of the crash report.
    A side comment:
    Them are 56 reported problems, and none of them have solutions. If I go through each problem report and check for solutions, about 80% of the times I ask myself to send to Microsoft for more information about the problem and I click on send, but I always get the following:
    [Window title]
    Incident reports

    [Main instruction]
    Problem connecting to the Windows error reporting service

    [Content]
    Some of the reports can not be uploaded to the Windows error reporting service. Please try again later.

    [Close] »
    I tried several times with the same result, that is, the details of the problem which has need of Microsoft is not be received.  To this end, the problem will not be found.
    Thanks much for any help.
    Manny
    P.S. I'll never upgrade a Windows operating system.  My recommendation for anyone who is planning to upgrade to Windows 7 is to try first on a dual boot using the free download.  If it works for you, consider yourself lucky and buy the upgrade.  If it does not, then remove Windows 7 and stay with your old system.

    Please check your RAM for errors (use memtest86 + to test). "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

  • Blue screen of death: stop error: 0X000000CE

    Hi, I think I got a bad virus on my computer that's all waste.  First of all, it all started when I clicked on a link, while the Christmas on Black Friday shopping. Then I got a download of unwanted software, called system difficulty, (the small icon of Windows) I could not use system restore to remove, whenever I tried to use it, it says cannot restore on this point. Tried several other points, but no joy. Can I get the dreaded blue screen of death with a stop error: 0x0000008e (0xc0000005, 0x804f8e80, 0xef76aa98, 0x00000000). Could sail in safe mode and tried to fix it with antivirus software, found 26, abducted, ran spybot search and destroy, found nothing. Still no joy. So today, I tried to start in safe mode, and it does not work in safe mode, guard reboot again and again. Then I hit F8 and turned restart turned off so I could see the Blue error screen that would flash for just a second, and now I have this stop error message: 0x000000ce (0xf88be6dc, 0 x 00000000, 0 x 00000000, 0xf88be6dc). I read forums on video and all drivers, but this happened just after I clicked on this link and got the virus with this unwanted software download. Anyone got any suggestions on how to solve this problem? Oh and I downloaded a program called error repair of my other computer and installed but it only scan my computer to find errors and then he wants to buy you the pack premium, so that did not help. It's my computer business running windows xp pro service pack 3. Wish it would have been on this cause she has the system recovery and it worked whenever I had a virus, I couldn't get rid of that. Thank you, Steve

    JoseIbarra is the expert resident on the Recovery Console and chkdsk/r. I'll track down his instructions. If the malware is responsible for the BSOD, I do not think that chkdsk /r will help, but it won't hurt. Or you might need to repair your boot.ini file.

    DEFINITELY get this brand XP reinstallation CD Dell! You can use it to perform a clean installation of XP or a repair installation of XP (chances are, you won't ever need to perform a repair installation, but it is nice to have this option) or to enter the Recovery Console to perform functions such as chkdsk/r.
    Chances are that your data does not fit on one CD! Depending on what you have, you might need to up to 100 CDs or more! Better to buy an external hard drive. Newegg.com has a very good selection of the most affordable. Here is an example:
    Creating a Ubuntu CD bootable 'live' (and then startup out of it, rather than on your hard drive) will allow you to copy your data to the external hard drive:
    There are also some other CD bootable antivirus (like Avira) which may help you:
    Here is a link to the instructions of Jose:

Maybe you are looking for

  • 12.3.2 iTunes does not merge the titles into the existing album

    I wanted to add a few tracks stolen in my singles vinyl as bonus tracks to an album from iTunes 12.3.2.35. I added album to a playlist and the titles of the albums OK. Yet somehow tracks have not been added to the appropriate albums. They stayed in o

  • First iteration of a loop problem

    I'm having a problem with the first iteration of a while loop. I want to save all the data a data acquisition over a period of time. In order to keep the unique 'small' file, I'm doing a VI that produce a new file every 10 min. about. But the first f

  • BlackBerry smartphones show theme?

    Ive download a theme and can see it in my application list. But how do I display on my phone?

  • Microsaft Agent 2.0 fix for Windows 7

    I recently installed Windows 7 on a computer running vista SP1 and also installed Microsoft Office XP (2002). I keep reciving the message that "Office Assistant requires Microsoft Agent 2.0 or later". I went on the site of MS on the fix and downloade

  • Masking and bug tracking

    If please see the video link and let me know if your system has done the same.First Pro CC masking bug - YouTubeTitle changed to research capacity by Kevin Monahan