PC Review
Forums
Newsgroups
Windows XP
Windows XP Accessibility
Fatal Error
Forums
Newsgroups
Windows XP
Windows XP Accessibility
Fatal Error
![]() |
Fatal Error |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
I have recently had the following error message:
bccode: 1000007f bcp1: 00000008 Bcp2: bab40d70 bcp3: 00000000 bcp4: 00000000 osver: 5_1_2600 SP: 2_0 Product: 256_1 I have had the PC for over a year and had no problems. Have tried resetting the PC back to factory settings and used the restore option in windows. PC is fairly meaty and I have never had issues running any hardware or software, no software or hardware added recently except the windows updates. Any advice would be appriciated, really don't want to flatten it and re-build, especially if its a hardware problem. |
|
|
|
#2 |
|
Guest
Posts: n/a
|
"kotfw" wrote: > I have recently had the following error message: > bccode: 1000007f bcp1: 00000008 Bcp2: bab40d70 bcp3: 00000000 bcp4: 00000000 > osver: 5_1_2600 SP: 2_0 Product: 256_1 > I have had the PC for over a year and had no problems. Have tried resetting > the PC back to factory settings and used the restore option in windows. PC is > fairly meaty and I have never had issues running any hardware or software, no > software or hardware added recently except the windows updates. > > Any advice would be appriciated, really don't want to flatten it and > re-build, especially if its a hardware problem. This is likely caused by hardware malfunctioning or bad driver. Try to look in the Device Manager for the CD/DVD-ROM and see if it malfunctioning or a Bad RAM, also USB storage. You may have a bad RAM try to test your RAM by running Memtest by downloading this tool and unzip it and make a floppy or CD/DVD and run it on Reboot. http://www.memtest86.com/ You may need to reposition/reset the RAM sticks in their slots. Scan your computer fro malware and Viruses by whatever software you have. DMA Mode for ATA/ATAPI Devices in Windows XP http://www.microsoft.com/whdc/devic...ge/IDE-DMA.mspx How to enable 48-bit Logical Block Addressing support for ATAPI disk drives in Windows XP http://support.microsoft.com/kb/303013 Example on the error code: http://support.microsoft.com/kb/174232 Information about Event ID 51 http://support.microsoft.com/kb/244780/ How to troubleshoot event ID 9, event ID 11, and event ID 15 error messages http://support.microsoft.com/kb/154690/ To get more info about the Error in Event Viewer please double click the Error message(X) to get a pop-up window contain info about the causer and you can copy and paste this content in your next message. HTH. nass --- www.nasstec.co.uk |
|
|
|
#3 |
|
Guest
Posts: n/a
|
kotfw <kotfw@discussions.microsoft.com> wrote:
>I have recently had the following error message: >bccode: 1000007f bcp1: 00000008 Bcp2: bab40d70 bcp3: 00000000 bcp4: 00000000 >osver: 5_1_2600 SP: 2_0 Product: 256_1 >I have had the PC for over a year and had no problems. Have tried resetting >the PC back to factory settings and used the restore option in windows. PC is >fairly meaty and I have never had issues running any hardware or software, no >software or hardware added recently except the windows updates. > >Any advice would be appriciated, really don't want to flatten it and >re-build, especially if its a hardware problem. I agree with Nass - the most likely cause of your problem is hardware. Parameter 1 (bcp1) indicates that the specific error was a Double Fault. The following information is from http://msdn2.microsoft.com/en-us/library/ms795478.aspx "0x00000008, or Double Fault, is when an exception occurs while trying to call the handler for a prior exception. Normally, the two exceptions can be handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault: 1. A kernel stack overflow. This occurs when a guard page is hit, and then the kernel tries to push a trap frame. Since there is no stack left, a stack overflow results, causing the double fault. If you suspect this has occurred, use the !thread debugger extension to determine the stack limits, and then use the kb (Display Stack Backtrace) debugger command with a large parameter (for example, kb 100) to display the full stack. 2. A hardware problem. Good luck Ron Martell Duncan B.C. Canada -- Microsoft MVP (1997 - 2008) On-Line Help Computer Service http://onlinehelp.bc.ca Syberfix Remote Computer Repair "Anyone who thinks that they are too small to make a difference has never been in bed with a mosquito." |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

