BSOD, skjer tilfeldig.

Flimzes · 22. april 2008

Jeg får bsod innimellom, helt tilfeldig. Det som skjer er at ting slutter å reagere, men jeg kan flytte på musa og musikken spiller, og etter 5-10sek så kommer blåskjermen opp.

Dette er et helt nyformatert windows xp system, på en nesten helt ny bærbar pc. Alle nyeste drivere er instalert. Feilen skjer alltid i det jeg skifter mellom to programmer, enten med alt+tab, eller på startlinja. Men programmene er tilfeldige.

Dette kunne jeg få ut av feilrapporten som kom opp etter restart:

BCCode : 1000008e BCP1 : 80000004 BCP2 : 806ECAE1 BCP3 : A8BD6248

BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

Jeg har også minidump filene, men jeg vet ikke helt hva jeg skal gjøre med dem, i notepad får jeg bare opp masse krøll.

Systemet er en ThinkPad R61, med intel grafikk. Kan også nevne at den kom med vista, men det gikk ulidelig sakte og wlan driveren krasjet hele tiden.

Cubicle Dude · 22. april 2008

Om dette er noe til hjelp vet jeg ikke.

Sjekk ram i pcèn din. Har du 2 så lar du bare 1 stå i. Får du fremdeles BSOD så bytter du ram og sjekker da den andre.

Ellers så fant jeg denne:

http://www.governmentsecurity.org/archive/t12031.html

Troubleshooting Blue Screen of Death (BSoD) errors, or as Microsoft calls them, Stop messages, can be extremely frustrating due to the fact that, by default, Windows XP automatically restarts the computer as soon as a BSoD error occurs. There's not enough time for you to analyse, let alone read, the error code before the message disappears.

You could disable the Automatically Restart option in the Startup And Recovery dialog box, but doing so might lock your system into an unrecoverable error situation. As such, that's not an advisable solution.

Fortunately, Windows XP keeps a special log of all BSoD errors, called a Watchdog Event Log. Unlike a memory dump, whose creation is the result of a BSoD error, a Watchdog Event Log is a straight text file that is easier to read and understand.

Here's how you access a Watchdog Event Log:

1. Use Windows Explorer to access the C:\Windows\LogFiles\Watchdog folder.

2. Locate and right-click the most recently dated .WDL file.

3. Select the Open command from the context menu.

4. In the Windows dialog box, choose the Select The Program From A List option and click OK.

5. When you see the Open With dialog box, select Notepad and click OK

Sjekket dette opp mot min egen pc. Fant en log under system32....

Her er en pdf med endel info:

http://www.sun.com/desktop/products/sunpci/bsod.pdf

Endret 22. april 2008 av Master Chiun

fenderebest · 22. april 2008

Alle blåskjermer skal naturligvis feilsøkes med Windbg

Flimzes · 1. mai 2008

Microsoft ® Windows Debugger Version 6.8.0004.0 X86

Loading Dump File [C:\WINDOWS\Minidump\Mini042608-01.dmp]

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

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Executable search path is:

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** 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 3.3311) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Sat Apr 26 15:50:46.046 2008 (GMT+2)

System Uptime: 0 days 2:27:07.724

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** 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

..............................

*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.dll

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {80000004, 806ecae1, a7d5f1e0, 0}

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

*** WARNING: Unable to verify timestamp for pci.sys

*** ERROR: Module load completed but symbols could not be loaded for pci.sys

*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS

*** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS

*** WARNING: Unable to verify timestamp for igxpmp32.sys

*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 : pci.sys ( pci+ae0 )

Followup: MachineOwner

---------

fenderebest · 1. mai 2008

Du må sette Image path til srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Og deretter kan du skrive inn !analyze -v

Flimzes · 1. mai 2008

Microsoft ® Windows Debugger Version 6.8.0004.0 X86

Loading Dump File [C:\WINDOWS\Minidump\Mini042608-01.dmp]

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

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** 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 3.3311) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Sat Apr 26 15:50:46.046 2008 (GMT+2)

System Uptime: 0 days 2:27:07.724

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** 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

..............................

*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.dll

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {80000004, 806ecae1, a7d5f1e0, 0}

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

*** WARNING: Unable to verify timestamp for pci.sys

*** ERROR: Module load completed but symbols could not be loaded for pci.sys

*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS

*** ERROR: Module load completed but symbols could not be loaded for VIDEOPRT.SYS

*** WARNING: Unable to verify timestamp for igxpmp32.sys

*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 : pci.sys ( pci+ae0 )

Followup: MachineOwner

---------

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

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: 80000004, The exception code that was not handled

Arg2: 806ecae1, The address that the exception occurred at

Arg3: a7d5f1e0, Trap Frame

Arg4: 00000000

Debugging Details:

------------------

***** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

*** ***

*** 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 ***

*** ***

*************************************************************************

MODULE_NAME: pci

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47b0c13e

EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - No such interface supported

FAULTING_IP:

hal+8ae1

806ecae1 c20800 ret 8

TRAP_FRAME: a7d5f1e0 -- (.trap 0xffffffffa7d5f1e0)

ErrCode = 00000000

eax=80001090 ebx=00000090 ecx=00000090 edx=00000cf8 esi=806f1420 edi=a7d5f2dc

eip=806ecae1 esp=a7d5f254 ebp=a7d5f264 iopl=0 nv up ei ng nz na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286

hal+0x8ae1:

806ecae1 c20800 ret 8

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 806e9f0f to 806ecae1

STACK_TEXT:

STACK_COMMAND: kb

FOLLOWUP_IP:

pci+ae0

b9f68ae0 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: pci+ae0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: pci.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

---------

fenderebest · 1. mai 2008

Er det bestandig samme blåskjermen? Ellers kan jeg bare si at dette er en VELDIG uvanlig feilmelding---det jeg dog legger merke til er at du kjører Service Pack 3 og at siden den ikke er ferdig enda kan denne lage problemer.

Hadde du samme problemene under Sp2?

Flimzes · 1. mai 2008

Er det bestandig samme blåskjermen? Ellers kan jeg bare si at dette er en VELDIG uvanlig feilmelding---det jeg dog legger merke til er at du kjører Service Pack 3 og at siden den ikke er ferdig enda kan denne lage problemer.

Hadde du samme problemene under Sp2?

Ja og ja

EDIT: Probleme har ikke vist seg på en stund, men mitt bruk har vært det samme, så jeg vet ærlig talt ikke hva det kan være. Men i det siste så har jeg spilt trackmania, og av og til på batteri helt til maskinen har dødd (batteriet går mye fortere når man spiller trackmania :blush: ) Så den har ikke hatt så lang oppetid i det siste.

Endret 1. mai 2008 av Flimzes

fenderebest · 1. mai 2008

Vel, da ligger problemet i maskinvaren-det hadde vært en fordel å fått de symbolene til å fungere skikkelig for å kunne si noe mer konkret.

Disse må lastes ned fra en server så du må være oppkoblet til internett og passe på at en brannmur ikke blokkerer.

Flimzes · 1. mai 2008

Vel, da ligger problemet i maskinvaren-det hadde vært en fordel å fått de symbolene til å fungere skikkelig for å kunne si noe mer konkret.

Disse må lastes ned fra en server så du må være oppkoblet til internett og passe på at en brannmur ikke blokkerer.

Det ligger masse filer i c:\symbols mappa nå, så er nok ikke der problemet ligger...

fenderebest · 1. mai 2008

Problemet ligger når han skal hente:

Unable to load image ntoskrnl.exe, Win32 error 0n2

Sannsynligvis prøver han å hente den i fra Windows\system32 mappen men siden din versjon av ntoskrnl.exe allerede er i bruk så...

Kunne du ha prøvd å kopiere ut ntoskrnl.exe fra CD-en (ligger i i386 mappen) og deretter lagt den i c:\symbols og deretter peke image path til c:\symbols

Logg inn

BSOD, skjer tilfeldig.

Anbefalte innlegg

Flimzes

Lenke til kommentar

Videoannonse

Cubicle Dude

Lenke til kommentar

fenderebest

Lenke til kommentar

Flimzes

Lenke til kommentar

fenderebest

Lenke til kommentar

Flimzes

Lenke til kommentar

fenderebest

Lenke til kommentar

Flimzes

Lenke til kommentar

fenderebest

Lenke til kommentar

Flimzes

Lenke til kommentar

fenderebest

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Opprett konto

Logg inn

Hvem er aktive 0 medlemmer