• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 456
  • Last Modified:

Blue screen on windows xp laptop

Hi there,

A customer has an HP NX9010 laptop which now and then gets a blue screen en restarts.
I have been searching on this forum and came across a few interesting posts, but could not find the solution for this particular code.
Hope someone can help me out and maybe have a look in the mini-dumps; i can e-mail them to you instantly, just leave a message.

System log on laptop: (in dutch, but the code stays the same of course...)
"Type gebeurtenis:    Fout

Bron van gebeurtenis:        System Error

Categorie van gebeurtenis:  (102)

Gebeurtenis-ID:       1003

Datum:                   19-04-2006

Tijd:             14:34:42

Gebruiker:               n.v.t.

Computer:     PC

Beschrijving:

Foutcode; 1000008e, parameter1: c000001d, parameter2: 804f0646, parameter3: f03f6bb0, parameter4: 00000000.

 

Zie Help en ondersteuning op http://go.microsoft.com/fwlink/events.asp voor meer informatie.

Gegevens:

0000: 53 79 73 74 65 6d 20 45   System E

0008: 72 72 6f 72 20 20 45 72   rror  Er

0010: 72 6f 72 20 63 6f 64 65   ror code

0018: 20 31 30 30 30 30 30 38    1000008

0020: 65 20 20 50 61 72 61 6d   e  Param

0028: 65 74 65 72 73 20 63 30   eters c0

0030: 30 30 30 30 31 64 2c 20   00001d,

0038: 38 30 34 66 30 36 34 36   804f0646

0040: 2c 20 66 30 33 66 36 62   , f03f6b

0048: 62 30 2c 20 30 30 30 30   b0, 0000

0050: 30 30 30 30               0000    

 

 

Type gebeurtenis:    Informatie

Bron van gebeurtenis:        Save Dump

Categorie van gebeurtenis:  Geen

Gebeurtenis-ID:       1001

Datum:                   21-04-2006

Tijd:             9:18:00

Gebruiker:               n.v.t.

Computer:     PC

Beschrijving:

De computer is opnieuw gestart na een foutencontrole. Foutencontrole: 0x1000008e (0xc0000005, 0x805678f7, 0xf0c56918, 0x00000000). Er is een dump opgeslagen in: C:\WINDOWS\Minidump\Mini042106-01.dmp."

0
global-e
Asked:
global-e
  • 7
  • 6
  • 3
  • +3
1 Solution
 
JoeCommented:
Do you have the Windows cd? Maybe you can try and do a windows repair, and if the repair install fails then I would suspect that this may be a hardware issue.

Joe
0
 
mediamaxCommented:
global,

0x8E particularly happens with device drivers or virtual drivers. I am sure youu must be also seeing a file name on the stop code screen. Please post the filename to arrive at the root cause.

0
 
Irwin SantosComputer Integration SpecialistCommented:
what STOP ERROR do you get?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
venom96737Commented:
0
 
global-eAuthor Commented:
Mediamax, thanks for your answer!

I am monitoring the laptop remotely via vnc, so i can't really tell  about the blue screen.
However, i can send you the minidumps generated by the blue screen.

If that doesn't do, i will ask the user to look closely when the blue screen happens again.

Cheers,
Robert
0
 
global-eAuthor Commented:
irwinpks , thx.

The stop error is in the post:

 0x1000008e (0xc0000005, 0x805678f7, 0xf0c56918, 0x00000000).
0
 
Irwin SantosComputer Integration SpecialistCommented:
http://support.microsoft.com/kb/893239/en-us

 Apply the service pack to fix..

Else, temporarily remove the CD-ROM drive
0
 
venom96737Commented:
The minidumps would be very helpful to finding the root of the problem.
0
 
global-eAuthor Commented:
THx,

SP2 allready has been installed as well as all possible essential windows updates.
I even had a look at the optional windows updates...

Robert
0
 
global-eAuthor Commented:
Is it possible to upload the minidumps  ?? or should i e-mail them ?

Robert
0
 
mediamaxCommented:
gloabal,

does this system runs on a nvidia based video card??? If so, most probably its an issue with a Video driver file nv4_disp.dll. In such case, i suggest to update forceware from nvidia site.

good luck
0
 
venom96737Commented:
you can just paste them on here at the point the error occured
0
 
venom96737Commented:
also you can check event viewer to see if it points to any of the driver as the cause.
0
 
mediamaxCommented:
Global,  

I just had a check on system specs of  HP NX9010. Look slike it goes with ATI cards as default. Do confirm the same. If its ATI then issue might be with atidvag.dll. Needs an updated driver from ATI site
0
 
global-eAuthor Commented:
Thanks a lot!

The output of a few minidumps: (i used windbg to openen the minidump, but i am not sure if that went 100 % OK; if someone knows about a better debug app., please let me know)

Hope someone is able to see the problem:

1.

"Microsoft (R) Windows Debugger  Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File []
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri Apr 21 09:13:44.260 2006 (GMT+2)
System Uptime: 0 days 0:02:49.296
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 805678f7, f0c56918, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+908f7 )

Followup: MachineOwner
---------

2.

"Microsoft (R) Windows Debugger  Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File []
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Fri Apr 14 08:41:58.109 2006 (GMT+2)
System Uptime: 0 days 0:01:06.703
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...........................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 804e655e, f0a5ebc8, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+f55e )

Followup: MachineOwner
---------"
0
 
venom96737Commented:
you not pointing it at the ntosknl file what was the command used to get this anlysis
0
 
venom96737Commented:
you also did not use the correct symbols path
0
 
cpc2004Commented:
Attach your minidumps at  public webspace. You can use  a free service like rapidshare to attach the minidumps and post the url of the mimidumps at this thread. http://www.rapidshare.de/

1000008e, parameter1: c000001d <-- Illegal instruction (ie misaligned instruction) and this is the sign of hardware error. Probably it is faulty ram. Run memtest to stress the ram. Refer the following cases
0
 
global-eAuthor Commented:
Thanks cpc2004.

i uploaded a zip file with a few minidumps to:
http://rapidshare.de/files/18815530/Minidump.zip.html

I am also busy to download the windows symbol package to be able to read dump files better.

Thanks in advance
0
 
JoeCommented:
Good free software to run hardware tests on your machine.

http://www.ultimatebootcd.com/
0
 
cpc2004Commented:
3 minidumps are crashed with code corruption.  It is no need to memtest as I'm very sure that it is faulty ram. Re-seat the ram to another memory slot. If it is still crashes, replace the ram.


Mini031406-01.dmp BugCheck 1000000A, {fffffff0, 2, 0, 804ef082}
Probably caused by : ntoskrnl.exe ( nt!CcAcquireByteRangeForWrite+384 )

Mini041106-01.dmp BugCheck 19, {20, e194e160, e194e1d8, c0f0401}
Probably caused by : ntoskrnl.exe ( nt!ExFreePoolWithTag+2be )

Mini041406-01.dmp BugCheck 1000008E, {c000001d, 804e655e, f0a5ebc8, 0}
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
Probably caused by : memory_corruption

Mini041806-01.dmp BugCheck 10000050, {e889bc74, 1, 805d609f, 2}
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
Probably caused by : memory_corruption

Mini041906-01.dmp BugCheck 1000008E, {c000001d, 804f0646, f03f6bb0, 0}
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
Probably caused by : memory_corruption

Mini042106-01.dmp BugCheck 1000008E, {c0000005, 805678f7, f0c56918, 0}
Probably caused by : ntoskrnl.exe ( nt!CmpCacheLookup+7f )
0
 
global-eAuthor Commented:
cpc2004, thanks.

I couldn't stand though to run memtest on the laptop and strange enough, it didn't find any errors.

However, i asked the customer to put the memory in another slot; luckily this customer is quite good with pc's, so they will give it a try; laptop is out of guarantee anyway.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 6
  • 3
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now