Windows Vista Blue screen of death error [INVALID_PROCESS_ATTACH_ATTEMPT]

hello

all of a sudden ysterday when i was in school w/ my laptop and when it tried to connect to the school network i got the bsod

i thot it might have been a lil error or something with their server, so i tried to log in my laptop when i got home and as soon as it tried to establish a connection with my router i got the bsod again

this is error 0x00000005 INVALID_PROCESS_ATTACH_ATTEMPT

this is a fairly new laptop as well. it runs windows vista and all and it ****** me off how every time i try to get online anywhere, i get the bsod

i tried using a restore point but that did no good.

any suggestions guys?

 

thank you

i read ur thread but the problem is i cannot connect to the internet with my laptop. with the files i am downloading i am doing so with my pc and transferring then with a usb flash drive.

is it necessary for my laptop to be connected to the internet? if so can u please tell me of a way to solve this?

 

i got the files on my laptop and now that i;ve opened debugwiz and its asking me to select a dump file to analyze, i cant find the dump file

any idea where it might be?

 

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16514.x86fre.vista_gdr.070627-1500
Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0
Debug session time: Tue Nov 6 11:10:07.138 2007 (GMT-5)
System Uptime: 0 days 0:05:01.826
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd300c). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 5, {83324d90, 902a1020, 0, 1}

*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for 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 ***
*** ***
*************************************************************************
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details
Page a0 not present in the dump file. Type ".hh dbgerr004" for details

 

You can try going to the Startup Options menu and selecting Safe Mode with Networking (tap the F8 key rapidly just before you would normally see the Windows loading screen). If the internet connection works there, the problem would be drivers or maybe a background program (trying to connect to the internet?).

If you can connect, you can run the debugger.

Check in the debugger that the symbol path is C:\Symbols, not C:\Windows (etc). If you cannot connect to the internet, you can go to that website http://msdl.microsoft.com/download/symbols on your PC, you will be redirected, but you will find you can download a full set of symbols to transfer to the laptop and save to the C:\Symbols folder.

I would go to the laptop manufacturer's website and get the major drivers.

Matt