opstart problemen xp

[asdena]

ja cd staat als 1... nee hij vraagt niks

[Gast]

ja zit nu op mn laptop...ff in het nederlands nu...wat moet ik doen?

een laptop is nogal lastig.

Heb je nergens een 2de vaste pc? zodat je de harde schijf daar in kan steken als 2de hd.

Dan kan je opstarten met je 1ste en kan je de 2de 'bewerken'

[asdena]

ja zou kunnen maar heb dat nog nooit gedaan dus geen idee hoe dat moet

[asdena]

misschien dat dit meer duidelijkheid brengt ..als ik opstart in veilige modus vraagt hij druk esc om zonder sptd.sys zoiets daarna krijg ik een blauw scherm met daarom

0x00000d3(0x865c580,0x0000001,0x804e2e41)

[be_dup]

0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED

http://aumha.org/a/stop.htm

nu nog uitzoeken wat het precies is en betekend...

[be_dup]

dit vond ik nog in het engels:

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.

If you can't start after enabling verifier

choose Last Known Good Configuration at the Failed Boot menu (which will

start without verifier).

You will be creating a crash dump file in c:\windows\minidump every blue screen. Make sure you are set to record minidumps (Small Memory Dumps) - type it in Help to see how.

Then

If you have the XP SP2 Security Update CD (else see

http://www.microsoft.com/whdc/Â*devtools/debugging/symbolpkg.mÂ*spx

)

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

Download

http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

Load the crash dump file into windbg

and read what it says. You may need to tell it where the symbols are. Read it.

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 david @ mvps.org. Don't send me lots of them. Just the one from your last crash after you turn verifier on. And only one per mail.

You can look up specific details here

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/BCIntro_ea8b9fd0-2d81-4a04-a7ed-c1c6a80bd501.xml.asp

If it indicates faulty memory might be the cause you can get a memory tester

here

http://oca.microsoft.com/en/wiÂ*ndiag.asp

If it mentions a core windows system file, meaning it a MS fix is required,

upload a minidump to

http://oca.microsoft.com

Also try typing the main error code in Help while online (ie,

Stop 0x50

and also try in the 8 digit form

stop 0x00000050)

and if there are too many hits use a filename if available. Generally memory

addresses are different for each computer (as each computer has a different

mix of drivers) so parameters that are memory addresses aren't that useful for searching, but NTStatus codes are (plus you can look them up here http://cvs.sourceforge.net/viewcvs.py/mingw/w32api/include/ddk/ntstatus.h?rev=1.2).

If this doesn't work try

Get your XP CD and install Windows Support Tools.

Type in start run after installing and rebooting

pstat > "%userprofile%\desktop\driverlÂ*ist.txt"

The last table in this file is a list of loaded drivers. Other things apart

from hardware uses drivers. Post the list of drivers (the last table only -

REPEAT THE LAST TABLE O N L Y ) or match the fault address to the driver.

This will allow you to match memory addresses to a driver.

http://phorums.com.au/archive/index.php/t-146313.html

[Sarah]

Dit onderwerp bevindt zich in het ARCHIEF. U kan NIET reageren in het archief.

Het onderwerp is ofwel opgelost of er was geen activiteit na 1 maand.

Hebt u een gelijkaardig probleem? post een nieuw onderwerp in:

Windows - Pc helpforum