PC Review


Reply
Thread Tools Rating: Thread Rating: 7 votes, 3.29 average.

What does this error code mean? BCCode : 1000008e

 
 
=?Utf-8?B?cGhsZWJhcw==?=
Guest
Posts: n/a
 
      17th Feb 2005
My PC generated this error code after 'recovering' from a serious error.
BCCode:1000008e
BCP1:C0000005
BCP2:8056A536
BCP3B7E2CC40
BCP4:00000000
OSVer:5_1_2600 SP2_0
Product:768_1
It still crashes and recovers from the same error. Is it an OS error or
Software/Hardware.

Thanks
 
Reply With Quote
 
 
 
 
James Hahn
Guest
Posts: n/a
 
      17th Feb 2005
This one seems closest to your situation:
http://support.microsoft.com/?kbid=316424
Error Message: The System Has Recovered from a Serious Problem
--
"phlebas" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> My PC generated this error code after 'recovering' from a serious error.
> BCCode:1000008e
> BCP1:C0000005
> BCP2:8056A536
> BCP3B7E2CC40
> BCP4:00000000
> OSVer:5_1_2600 SP2_0
> Product:768_1
> It still crashes and recovers from the same error. Is it an OS error or
> Software/Hardware.
>
> Thanks



 
Reply With Quote
 
 
 
 
David Candy
Guest
Posts: n/a
 
      17th Feb 2005
0x1000008e is same as 0x8e

Driver Development Tools: Windows DDK

Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 The trap frame
4 Reserved


Cause
This is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:

a.. 0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.

b.. 0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system. • 0xC0000005: STATUS_ACCESS_VIOLATION

A memory access violation occurred.

For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows DDK.

Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame will supply additional information.

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility. First, make sure that any new hardware installed is listed on the Microsoft Windows Hardware Compatibility List (HCL).

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You can also use another hard disk with more free space for the installation. BIOS problems can be resolved by upgrading the system BIOS version.

Send feedback on this topic. / Built on Thursday, February 13, 2003

Memory Tester
============

http://oca.microsoft.com/en/windiag.asp

If it's not hardware
==============

Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.

You will be creating a crash dump file in c:\windows\minidump every blue screen.

Then

If you have the XP SP2 Security Update CD

Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS

Download
http://www.microsoft.com/whdc/devtoo...nstallx86.mspx

Load the crash dump file into windbg (File - Load Crash Dump and it's in c:\windows\minidump) and READ WHAT IT SAYS, then
Type
!Analyze -v
into Windbg's command line.
(this will hopefully tell you the faulty component)

If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash and one from your next crash after you turn verifier on. And only one per mail.

From Help (you want small memory dumps)
==================================
To specify what Windows does if the system stops unexpectedly

You must be logged on as an administrator or a member of the Administrators group in order to complete this procedure. If your computer is connected to a network, network policy settings might also prevent you from completing this procedure.

1.. Open System in Control Panel.
2.. On the Advanced tab, under Startup and Recovery, click Settings.
3.. Under System Failure, select the check boxes that correspond to the actions you want Windows to perform if a Stop error occurs:
a.. Write an event to the system log specifies that event information will be recorded in the system log.
b.. Send an administrative alert specifies that your system administrator will be notified.
c.. Automatically reboot specifies that Windows will automatically restart your computer.
4.. Under Write Debugging Information, choose the type of information you want Windows to record when the system stops unexpectedly:
a.. Small Memory Dump records the smallest amount of information that will help identify the problem. This option requires a paging file of at least 2 MB on the boot volume of your computer and specifies that Windows will create a new file each time the system stops unexpectedly. A history of these files is stored in the directory listed under Small Dump Directory.
b.. Kernel Memory Dump records only kernel memory, which speeds up the process of recording information in a log when the system stops unexpectedly. Depending on the amount of RAM in your computer, you must have 50 MB to 800 MB available for the paging file on the boot volume. The file is stored in the directory listed under Dump File.
c.. Complete Memory Dump records the entire contents of system memory when the system stops unexpectedly. If you choose this option you must have a paging file on the boot volume large enough to hold all of the physical RAM plus one megabyte (MB). The file is stored in the directory listed under Dump File.
Notes

a.. To open System, click Start, click Control Panel, and then double-click System.
b.. You must have at least a 2-MB paging file on the computer's boot volume if you select Write an event to the system log or Send an administrative alert.
c.. If you choose either Kernel Memory Dump or Complete Memory Dump and select the Overwrite any existing file check box, Windows always writes to the same file name. To save individual dump files, clear the Overwrite any existing file check box and change the file name after each Stop error.
d.. You can save some memory if you clear the Write an event to the system log and Send an administrative alert check boxes. The memory saved depends on the computer, but typically about 60 KB to 70 KB are required by these features.
e.. If you contact Microsoft Product Support Services about a Stop error, they might ask for the system-memory dump file generated by the Write Debugging Information option.
Related Topics



--
----------------------------------------------------------
http://www.microscum.com/mscommunity/
"phlebas" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> My PC generated this error code after 'recovering' from a serious error.
> BCCode:1000008e
> BCP1:C0000005
> BCP2:8056A536
> BCP3B7E2CC40
> BCP4:00000000
> OSVer:5_1_2600 SP2_0
> Product:768_1
> It still crashes and recovers from the same error. Is it an OS error or
> Software/Hardware.
>
> Thanks

 
Reply With Quote
 
=?Utf-8?B?cGhsZWJhcw==?=
Guest
Posts: n/a
 
      18th Feb 2005
Thanks for your response.
Phlebas

"James Hahn" wrote:

> This one seems closest to your situation:
> http://support.microsoft.com/?kbid=316424
> Error Message: The System Has Recovered from a Serious Problem
> --
> "phlebas" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > My PC generated this error code after 'recovering' from a serious error.
> > BCCode:1000008e
> > BCP1:C0000005
> > BCP2:8056A536
> > BCP3B7E2CC40
> > BCP4:00000000
> > OSVer:5_1_2600 SP2_0
> > Product:768_1
> > It still crashes and recovers from the same error. Is it an OS error or
> > Software/Hardware.
> >
> > Thanks

>
>
>

 
Reply With Quote
 
=?Utf-8?B?cGhsZWJhcw==?=
Guest
Posts: n/a
 
      18th Feb 2005
Thanks for your response. I worked through your advice and now seem to have a
fully functioning pc again. Windbg pointed to some ATI files, so I
reinstalled the drivers.
many thanks
Phlebas

"David Candy" wrote:

> 0x1000008e is same as 0x8e
>
> Driver Development Tools: Windows DDK
>
> Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
> The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.
>
> Parameters
> The following parameters are displayed on the blue screen.
>
> Parameter Description
> 1 The exception code that was not handled
> 2 The address at which the exception occurred
> 3 The trap frame
> 4 Reserved
>
>
> Cause
> This is a very common bug check. To interpret it, you must identify which exception was generated.
>
> Common exception codes include:
>
> a.. 0x80000002: STATUS_DATATYPE_MISALIGNMENT
> An unaligned data reference was encountered.
>
> b.. 0x80000003: STATUS_BREAKPOINT
> A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system. • 0xC0000005: STATUS_ACCESS_VIOLATION
>
> A memory access violation occurred.
>
> For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows DDK.
>
> Resolving the Problem
> If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.
>
> If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.
>
> If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.
>
> If exception code 0x80000002 occurs, the trap frame will supply additional information.
>
> If the specific cause of the exception is unknown, the following should be considered:
>
> Hardware incompatibility. First, make sure that any new hardware installed is listed on the Microsoft Windows Hardware Compatibility List (HCL).
>
> Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
>
> If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.
>
> If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.
>
> Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer.
>
> The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk. Check for and delete any unneeded temporary files, Internet cache files, application backup files, and .chk files containing saved file fragments from disk scans. You can also use another hard disk with more free space for the installation. BIOS problems can be resolved by upgrading the system BIOS version.
>
> Send feedback on this topic. / Built on Thursday, February 13, 2003
>
> Memory Tester
> ============
>
> http://oca.microsoft.com/en/windiag.asp
>
> If it's not hardware
> ==============
>
> Type verifier in Start Run, follow the wizard but choose All Drivers. This will slow down your computer and cause more blue screen crashes but will pinpoint what is causing the crash (if the original error message didn't). Once you fix it you rerun verifier and turn it off.
>
> You will be creating a crash dump file in c:\windows\minidump every blue screen.
>
> Then
>
> If you have the XP SP2 Security Update CD
>
> Install symbols from <CD Drive Letter>:\SUPPORT\SYMBOLS
>
> Download
> http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
>
> Load the crash dump file into windbg (File - Load Crash Dump and it's in c:\windows\minidump) and READ WHAT IT SAYS, then
> Type
> !Analyze -v
> into Windbg's command line.
> (this will hopefully tell you the faulty component)
>
> If the above is too technical then email the crash dump files to davidc @ mvps.org. Don't send me lots of them. Just the one from your last crash and one from your next crash after you turn verifier on. And only one per mail.
>
> From Help (you want small memory dumps)
> ==================================
> To specify what Windows does if the system stops unexpectedly
>
> You must be logged on as an administrator or a member of the Administrators group in order to complete this procedure. If your computer is connected to a network, network policy settings might also prevent you from completing this procedure.
>
> 1.. Open System in Control Panel.
> 2.. On the Advanced tab, under Startup and Recovery, click Settings.
> 3.. Under System Failure, select the check boxes that correspond to the actions you want Windows to perform if a Stop error occurs:
> a.. Write an event to the system log specifies that event information will be recorded in the system log.
> b.. Send an administrative alert specifies that your system administrator will be notified.
> c.. Automatically reboot specifies that Windows will automatically restart your computer.
> 4.. Under Write Debugging Information, choose the type of information you want Windows to record when the system stops unexpectedly:
> a.. Small Memory Dump records the smallest amount of information that will help identify the problem. This option requires a paging file of at least 2 MB on the boot volume of your computer and specifies that Windows will create a new file each time the system stops unexpectedly. A history of these files is stored in the directory listed under Small Dump Directory.
> b.. Kernel Memory Dump records only kernel memory, which speeds up the process of recording information in a log when the system stops unexpectedly. Depending on the amount of RAM in your computer, you must have 50 MB to 800 MB available for the paging file on the boot volume. The file is stored in the directory listed under Dump File.
> c.. Complete Memory Dump records the entire contents of system memory when the system stops unexpectedly. If you choose this option you must have a paging file on the boot volume large enough to hold all of the physical RAM plus one megabyte (MB). The file is stored in the directory listed under Dump File.
> Notes
>
> a.. To open System, click Start, click Control Panel, and then double-click System.
> b.. You must have at least a 2-MB paging file on the computer's boot volume if you select Write an event to the system log or Send an administrative alert.
> c.. If you choose either Kernel Memory Dump or Complete Memory Dump and select the Overwrite any existing file check box, Windows always writes to the same file name. To save individual dump files, clear the Overwrite any existing file check box and change the file name after each Stop error.
> d.. You can save some memory if you clear the Write an event to the system log and Send an administrative alert check boxes. The memory saved depends on the computer, but typically about 60 KB to 70 KB are required by these features.
> e.. If you contact Microsoft Product Support Services about a Stop error, they might ask for the system-memory dump file generated by the Write Debugging Information option.
> Related Topics
>
>
>
> --
> ----------------------------------------------------------
> http://www.microscum.com/mscommunity/
> "phlebas" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> > My PC generated this error code after 'recovering' from a serious error.
> > BCCode:1000008e
> > BCP1:C0000005
> > BCP2:8056A536
> > BCP3B7E2CC40
> > BCP4:00000000
> > OSVer:5_1_2600 SP2_0
> > Product:768_1
> > It still crashes and recovers from the same error. Is it an OS error or
> > Software/Hardware.
> >
> > Thanks

>

 
Reply With Quote
 
New Member
Join Date: Oct 2006
Posts: 1
 
      26th Oct 2006
I have the same problem with my computer, and i did everything that I read here, but I cant understand where my problem is.
I have a new computer with :
Abit IL8
Corsair TWIN2X 1GB DDR2 667MHz
Pentium D 945+ 3.4GHz
ASUS Nvidia 7600GT Silent

I ruled out hardware problems because I have no problems while using Ubuntu. By the way I'm using the normal Windows XP Pro SP2 (Not the 64bit one) and i already had 5 restarts this week. Hardware is updated and bios is updated 2.
I would be very much obliged if annyone can help.
This is the minidump generated (any idea where the problem is):

Quote:
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8054afd2, The address that the exception occurred at
Arg3: a7460ad4, Trap Frame
Arg4: 00000000

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!ExAllocatePoolWithTag+66a
8054afd2 894804 mov dword ptr [eax+4],ecx

TRAP_FRAME: a7460ad4 -- (.trap ffffffffa7460ad4)
ErrCode = 00000002
eax=00000000 ebx=867ee0a0 ecx=867ee240 edx=00000028 esi=e1a5bcc8 edi=000001ff
eip=8054afd2 esp=a7460b48 ebp=a7460b9c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExAllocatePoolWithTag+0x66a:
8054afd2 894804 mov dword ptr [eax+4],ecx ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: fifa07.exe

LAST_CONTROL_TRANSFER: from bf802b6a to 8054afd2

STACK_TEXT:
a7460b9c bf802b6a 00000001 00000001 32206844 nt!ExAllocatePoolWithTag+0x66a
a7460bbc bf8a15a1 00000134 32206844 00000000 win32k!HeavyAllocPool+0x74
a7460bd8 bf9c4b19 00000001 00000124 32206844 win32k!EngAllocMem+0x33
a7460bec bf9c4e6b 00000124 00000002 00000001 dxg!DdAllocateObject+0x21
a7460c0c bf9c6b89 00000124 00000002 00000001 dxg!DdHmgAlloc+0x21
a7460c4c bf9cd751 e427b860 00000000 a7460c74 dxg!peDdOpenNewSurfaceObject+0x6d
a7460d44 8054060c 0f200019 00000000 0012f328 dxg!DxDdCreateSurfaceObject+0x9d
a7460d44 7c90eb94 0f200019 00000000 0012f328 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f2b4 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HeavyAllocPool+74
bf802b6a 8bd0 mov edx,eax

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

SYMBOL_NAME: win32k!HeavyAllocPool+74

FAILURE_BUCKET_ID: 0x8E_win32k!HeavyAllocPool+74

BUCKET_ID: 0x8E_win32k!HeavyAllocPool+74

Followup: MachineOwner
 
Reply With Quote
 
Member
billybobbbuddy's Avatar
Join Date: Nov 2007
Location: SouthEast Ohio
Posts: 70
 
      7th May 2008
I had the same situation happen to me. I was surfing the web one morning and my computer just shut down and started right back up with a bunch of error codes similar to the ones mentioned. I checked my drivers under device manager as well and everything was working fine. So, what now? I am also going to run my A.V. & A. Spyware as well and see what happens. I have to be honest though, this is the first time this has happened to my computer since I bought it new a year ago! I have had no real problems since!
 
Reply With Quote
 
New Member
Join Date: Oct 2008
Posts: 1
 
      26th Oct 2008
I too have suffered this problem for a while and I'm still trying to find a solution.
My comp has an AMD anthlon 64 and 1.5 gb of ram (a 1gb and a 512mb) the mobo recognises the ram to be running at single channel . Also when i was upgrading my comp I found that the ram slots weren't labelled correctly. By this i mean that the slots were labelled in what i would call a conventional manner - 1234 - but for some reason mine only works if i put 1 in slot 1 and 1 in slot 3 so this to me means that the mobo recongises the slot 3 as 2 and 2 as 3 so the slots should be labelled 1324. If that makes any sense at all. I have also read that this problem could be caused by faulty drivers which might be the old printer driveres i left on there after i changed printer - but they have since been deleted. I'm trying desperately not to reformat my computer as i have currently nearly 90 programs on my computer and i sure as hell don't want to have reinstall all of those as well as drivers - it would take me a few years The third and final issue that i have read about that could be a cause is antivirus. I use adaware every 2 weeks to check for bugs, i have nod 32 and zone alarm. All of these i update regulary. Despite all this Windows thinks that my antivirus software is either "turned off or out of date"

Sorry if i have confused anyone and I'm happy to answer any questions.
Any help would be greatly appreciated.
 
Reply With Quote
 
New Member
Join Date: Jan 2009
Posts: 1
 
      6th Jan 2009
I had the same situation happen to me. My Computer is reboots randomly with appearing a blue screen just for a secend, when it boots back , the error message is:


The system has recovered from a serious error.
A log of this error has been created
Please tell Microsoft about this problem.

Error Signature

BCCode : 1000008e BCP1 : C0000005 BCP2 : 805C50E2 BCP3 : AAC72C4C
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

The Following Files will be includes in the error report:
> Mini010609-01.dmp
> sysdata.xml

I have to be honest, this is the first time this has happened to my computer since I bought it 2 year ago! I have had no real problems since!

First time its happend when I am trying to install a softwere in my old Computer
With Mother board and processer (1GHz)
with 256 of RAM
But 80GB HARD is same old

After that Just before 1 month I replace my computer with the
Mother Board(Pentium 4),
Processer (with 3.0 GHz)
and 512 RAM

But now when I attempt to Install Audio and video drivers, execatly the same error is created after some time and sometimes on time.
To resolve that error:
> I have made the new partition of the Hard Disk many times
> Change CD-ROM
> Applying different Windows and different CDs of Windows

But the problem is still here. Any one there who solve my problem please

My e-mail Address:
(E-Mail Removed)

Thanks!
 
Reply With Quote
 
New Member
Join Date: Dec 2011
Posts: 1
 
      25th Dec 2011
I guess that this issue has been resolved but for anyone with the same problem that has been led here by Google let me tell you my story. I kept getting the blue screen and at times the pc would restart for me to sign in and then go to blue screen again for it to restart again this went on for some time until I was willing to discard said PC. I didn't know if this was a hardware or a software problem. It used to happen sometimes when I picked the laptop up so I thought there might be a loose connection somewhere. I then remebered that I used to get a message that said that the 'ATI graphics driver had stopped but has now recovered'. So I thought as a last resort I would have a look, went into Device Manager clicked on Display adapters right clicked on ATI Radeon Xpress series went to properties then clicked driver, clicked on uninstal clicked ok and restarted the lapstop. When it resarted it opened in Safe mode, I restarted again and voila problem now resolved. May not help everyone with this problem but worth a shot.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
BCCode : 1000008e Amarjeet Windows XP General 5 26th Nov 2008 01:50 AM
BCCode:1000008e blue screen of death during shut down and then it reboots david Windows Vista General Discussion 2 28th Aug 2007 09:50 PM
What does this error code mean? BCCode : 1000008e and more adiomri Support 3 18th Sep 2006 06:16 PM
Errors BCCode : 1000008e BCP1 : C0000005 BCP2 : BFBC8AB8 =?Utf-8?B?TGluZyBXYW5nIENoaXU=?= Windows XP Help 0 29th Jun 2004 07:17 PM
Does anyone know what BcCode 1000008e is about? Patrick Windows XP General 2 9th Apr 2004 07:49 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 08:37 PM.