Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD while connecting to work VPN while at home.


  • Please log in to reply
2 replies to this topic

#1 TheLightedPath

TheLightedPath

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:02:47 PM

Posted 16 August 2010 - 08:58 AM

I have a guy at work whom his computer keeps bluescreening while at home trying to connect to our VPN. I for the life of me cannot figure out what it is. I have reinstalled network drivers, chipsets you name it and still having an issue. Tried to read the minidump file and this is what spits out. Any Ideas?

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Mini081410-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\windows\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Aug 14 13:14:23.109 2010 (GMT-4)
System Uptime: 0 days 4:34:32.465
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
...............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 0, 86df1930}

GetUlongFromAddress: unable to read from 805637f0
GetUlongFromAddress: unable to read from 805637f0
Probably caused by : ntoskrnl.exe ( nt!_woutput+414 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 00000000, Memory contents of the pool block
Arg4: 86df1930, Address of the block of pool being deallocated

Debugging Details:
------------------

GetUlongFromAddress: unable to read from 805637f0
GetUlongFromAddress: unable to read from 805637f0

POOL_ADDRESS: 86df1930

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: lsass.exe

LAST_CONTROL_TRANSFER: from 00000000 to 804f9f43

STACK_TEXT:
a1783590 00000000 00000000 86e46af0 00000000 nt!_woutput+0x414


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!_woutput+414
804f9f43 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!_woutput+414

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4bd6e0e8

FAILURE_BUCKET_ID: 0xc2_7_nt!_woutput+414

BUCKET_ID: 0xc2_7_nt!_woutput+414

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

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,254 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:47 PM

Posted 16 August 2010 - 10:21 AM

None that I can see.

Lsass errors with thie message seemed to occur frequently with Win 2000...but I don't see much for XP errors. Also seems to be related frequently to print function.

Have you checked Event Viewer for possible clues?

The obvious thing would be to uninstall the network drivers this person is using and reinstall them, IMO.

No one else at your worksite has this problem?

Louis

#3 TheLightedPath

TheLightedPath
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:02:47 PM

Posted 16 August 2010 - 10:28 AM

I have checked the Event Viewer it looks to be clean. The computer is a brand new Elitebook Workstation we bought for him cause his old XPS had died. No one else is having these problems however I did just think that when I reinstalled the driver i was throught he firewall ill try without it see if it messed up.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users