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

Help please: Vista crash


  • Please log in to reply
5 replies to this topic

#1 host21

host21

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:03:40 PM

Posted 17 January 2010 - 06:40 PM

Ive utilized windows debugger but I have no clue whats the problem here.

Here is the outcome of the debugging. Thanks for your assistance.


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



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


Loading Dump File [C:\Windows\Minidump\Mini011710-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339
Machine Name:
Kernel base = 0x82c06000 PsLoadedModuleList = 0x82d1dc70
Debug session time: Sun Jan 17 23:29:40.607 2010 (GMT+1)
System Uptime: 0 days 2:30:17.008
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {c9950000, 0, 82c4b523, 0}


Could not read faulting driver name
Probably caused by : ntkrpamp.exe ( nt!KiFastCallEntry+12a )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: c9950000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 82c4b523, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 82d3d868
Unable to read MiSystemVaType memory at 82d1d420
c9950000

FAULTING_IP:
nt!RtlInitUnicodeString+1b
82c4b523 f266af repne scas word ptr es:[edi]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: Smc.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82c50c7a to 82c4b523

STACK_TEXT:
abd85d44 82c50c7a 045efb6c 00100080 045efb4c nt!RtlInitUnicodeString+0x1b
abd85d44 00000001 045efb6c 00100080 045efb4c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002847c8 00000000 00000000 00000000 00000000 0x1


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiFastCallEntry+12a
82c50c7a f6456c01 test byte ptr [ebp+6Ch],1

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiFastCallEntry+12a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a77feb3

FAILURE_BUCKET_ID: 0x50_nt!KiFastCallEntry+12a

BUCKET_ID: 0x50_nt!KiFastCallEntry+12a

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: c9950000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 82c4b523, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 82d3d868
Unable to read MiSystemVaType memory at 82d1d420
c9950000

FAULTING_IP:
nt!RtlInitUnicodeString+1b
82c4b523 f266af repne scas word ptr es:[edi]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: Smc.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82c50c7a to 82c4b523

STACK_TEXT:
abd85d44 82c50c7a 045efb6c 00100080 045efb4c nt!RtlInitUnicodeString+0x1b
abd85d44 00000001 045efb6c 00100080 045efb4c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002847c8 00000000 00000000 00000000 00000000 0x1


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiFastCallEntry+12a
82c50c7a f6456c01 test byte ptr [ebp+6Ch],1

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiFastCallEntry+12a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a77feb3

FAILURE_BUCKET_ID: 0x50_nt!KiFastCallEntry+12a

BUCKET_ID: 0x50_nt!KiFastCallEntry+12a

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

BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,610 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:07:40 AM

Posted 17 January 2010 - 07:56 PM

What's the situation?
Is the computer bootable, or you're stuck?

PAGE_FAULT_IN_NONPAGED_AREA usually means some RAM problem.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#3 host21

host21
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:03:40 PM

Posted 18 January 2010 - 03:15 AM

I was able to look it up.

Its the folder lock causing it to crash. I ve tried unistalling it but its giving me blue screen Winfl32.sys

Then also one of them is and did a sfc scan and it says found some corrupt files. I thinks its Hal.dll?

Thanks for the help.

#4 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,610 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:07:40 AM

Posted 18 January 2010 - 01:24 PM

So, what's your current status?

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#5 host21

host21
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Local time:03:40 PM

Posted 25 January 2010 - 05:07 PM

Sorry took a while. Its good now. No more blue screen. folderlock finally removed. thanks alot...

#6 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,610 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:07:40 AM

Posted 25 January 2010 - 05:15 PM

Cool :huh:

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users