Have you run memory diagnostic (Control Panel in classic mode -
Administrative Tools - Memory Diagnostic Tool) also
chkdsk c: /r
in a command prompt.
Then
sfc /scannow

--
..
--
"sands vs" <guest@unknown-email.com> wrote in message
news:8ca7a0d2a7841e33a9756b9e0d43b205@nntp-gateway.com...[color=blue]
>
> Hi guys,
>
> I hope this is in the right part i was not sure where to post..
>
> I have windows vista home premium, My laptop is a toshiba satalite a200
> psofoa.
>
> Im having this error message and windows crashing..
>
> I have reset up the computer from backup disks twice, no better, i have
> avast professional running and it picks up nothing, i have even tried
> updating my toshiba value added package drivers, all no better.
>
> Any ideas.
>
>
> *problem signature:
> *problem event name: bluescreen
> os version: 6.0.6000.2.0.0.768.3
> locale id: 3081
> *additional information about the problem:
> *bccode: 50
> bcp1: ffffffff
> bcp2: 00000000
> bcp3: a2c05e6a
> bcp4: 00000000
> os version: 6_0_6000
> service pack: 0_0
> product: 768_1
> *files that help describe the problem:
> *c:\windows\minidump\mini051309-01.dmp
> c:\users\ryzie\appdata\local\temp\wer-65879-0.sysdata.xml
> c:\users\ryzie\appdata\local\temp\wer697b.tmp.version.txt
> *read our privacy statement:
> *_'microsoft_online_crash_analysis'
> ([url]http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409[/url])
> _
>
>
> --
> sands vs[/color]

Type command in the Start Menu search box and choose Command Prompt, type in
command prompt

chkdsk c: /r

then

sfc /scannow

The first checks the disk surface and file system and the second repairs
corrupted files. If Chkdsk doesn't find anything then it may be a driver.

You may want to run the memory check overnight just to be certain. Also
unplug what you can (USB keys etc) to see if that helps.

From Windows Driver Devekopment Kit

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
The PAGE_FAULT_IN_NONPAGED_AREA bug check has value 0x00000050. This signals
that invalid system memory has been referenced.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Memory address referenced
2 0: Read
1: Write
3 Address that referenced memory (if known)
4 Reserved


If the guilty driver can be identified, its name is printed on the blue
screen and stored in PUNICODE_STRING parameter of KiBugCheckDriver.

Cause
Bug check 0x50 usually occurs after the installation of faulty hardware or
in the event of failure of installed hardware (usually related to defective
RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a bug-ridden system service.

Antivirus software can also trigger this error, as can a corrupted NTFS
volume.

Resolving the Problem
Resolving a faulty hardware problem: If hardware has been added to the
system recently, remove it to see if the error recurs. If existing hardware
has failed, remove or replace the faulty component. You should run hardware
diagnostics supplied by the system manufacturer. For details on these
procedures, see the owner's manual for your computer.

Resolving a bug-ridden system service problem: Disable the service and
confirm that this resolves the error. If so, contact the manufacturer of the
system service about a possible update. If the error occurs during system
startup, restart your computer, and press F8 at the character-mode menu that
displays the operating system choices. At the resulting Windows Advanced
Options menu, choose the Last Known Good Configuration option. This option
is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm
that this resolves the error. If it does, contact the manufacturer of the
program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and
repair disk errors. You must restart the system before the disk scan begins
on a system partition. If the hard disk is SCSI, check for problems between
the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages
that might help pinpoint the device or driver that is causing the error.
Disabling memory caching of the BIOS might also resolve it.

Comments
Typically, this address is in freed memory or is simply invalid.


--
..
--
"sands vs" <guest@unknown-email.com> wrote in message
news:3db1a47449f460a3dcdc4de832fcb1f6@nntp-gateway.com...[color=blue]
>
> ;1042403 Wrote:[color=green]
>> Have you run memory diagnostic (Control Panel in classic mode -
>> Administrative Tools - Memory Diagnostic Tool) also
>> chkdsk c: /r
>> in a command prompt.
>> Then
>> sfc /scannow
>>
>> --
>> ..
>> --
>> "sands vs" <guest@xxxxxx-email.com> wrote in message
>> news:8ca7a0d2a7841e33a9756b9e0d43b205@xxxxxx-gateway.com...> > >[color=darkred]
>> > >
>> > > Hi guys,
>> > >
>> > > I hope this is in the right part i was not sure where to post..
>> > >
>> > > I have windows vista home premium, My laptop is a toshiba satalite
>> > a200
>> > > psofoa.
>> > >
>> > > Im having this error message and windows crashing..
>> > >
>> > > I have reset up the computer from backup disks twice, no better, i
>> > have
>> > > avast professional running and it picks up nothing, i have even tried
>> > > updating my toshiba value added package drivers, all no better.
>> > >
>> > > Any ideas.
>> > >
>> > >
>> > > *problem signature:
>> > > *problem event name: bluescreen
>> > > os version: 6.0.6000.2.0.0.768.3
>> > > locale id: 3081
>> > > *additional information about the problem:
>> > > *bccode: 50
>> > > bcp1: ffffffff
>> > > bcp2: 00000000
>> > > bcp3: a2c05e6a
>> > > bcp4: 00000000
>> > > os version: 6_0_6000
>> > > service pack: 0_0
>> > > product: 768_1
>> > > *files that help describe the problem:
>> > > *c:\windows\minidump\mini051309-01.dmp
>> > > c:\users\ryzie\appdata\local\temp\wer-65879-0.sysdata.xml
>> > > c:\users\ryzie\appdata\local\temp\wer697b.tmp.version.txt
>> > > *read our privacy statement:
>> > > *_'microsoft_online_crash_analysis'
>> > > ('Microsoft Online Crash Analysis'
>> > ([url]http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409[/url]))
>> > > _
>> > >
>> > >
>> > > --
>> > > sands vs > >[/color][/color]
>
>
> Thanks heaps for your help, i ran the tool through control panel and it
> came up fine..
>
> *Im not sure what you mean by *
> *chkdsk c: /r*
> *in a command prompt.*
> *Then*
> *sfc /scannow*
>
>
> --
> sands vs[/color]

Instead of clicking Command Prompt, right click it and choose Run As
Administrator.

--
..
--
"sands vs" <guest@unknown-email.com> wrote in message
news:4509aaf6ea6eaf33bb0922b7bc8cfc5e@nntp-gateway.com...[color=blue]
>
> thanks for the info :)..
>
>
> I also was having other dramas so i would back the registry..
>
>
> But before i did this i went into the dos window and ...
> When i treid this is what i got..
>
>
> *I tried this but it came up with access denied you dont have
> sufficient privlidges. You will have to invoke this utility running in
> evaluated mode??*
>
>
> --
> sands vs[/color]

Yes that is correct. Hard drives monitor themselves and yours is failing.
Backup what you want off your drive as it may fail completely soon.


--
..
--
"sands vs" <guest@unknown-email.com> wrote in message
news:3a22fecd129a0a1eba4b6a520371f840@nntp-gateway.com...[color=blue]
>
> well i left it do the... chkdsk c: /r
>
> As described and it took about 15 hours and came up with the following
> message
>
> Smart failure predice on hard dick 0: hitachi hts541680T..... Warning
> immediately back up your data and replace your hard dick drive. A
> failure may be imminent..
>
>
> Does not sound positive ha ha ha.. so do i assume my hd is stuffed and
> dont bother running the second step then?
>
>
> --
> sands vs[/color]

I don't know about brand. I look at RPM and cache. A fast hard drive makes
lots of things zippier, like program loading. I use a 10,000 rpm drive but
7200 is also fast and better value for money. You probably have a 5400 rpm
currently.

--
..
--
"sands vs" <guest@unknown-email.com> wrote in message
news:c052a3258391a2030df7b163b2f0771b@nntp-gateway.com...[color=blue]
>
> Ah good, well at least it gives me an excuse to piss off the 67 gig hd
> and get a bigger one... ;) Are WD hard drive ok or is samsung better
> thats the brands im looking at..
>
> ;1043693 Wrote:[color=green]
>> Yes that is correct. Hard drives monitor themselves and yours is
>> failing.
>> Backup what you want off your drive as it may fail completely soon.
>>
>>
>> --
>> ..
>> --
>> "sands vs" <guest@xxxxxx-email.com> wrote in message
>> news:3a22fecd129a0a1eba4b6a520371f840@xxxxxx-gateway.com...> > >[color=darkred]
>> > >
>> > > well i left it do the... chkdsk c: /r
>> > >
>> > > As described and it took about 15 hours and came up with the
>> > following
>> > > message
>> > >
>> > > Smart failure predice on hard dick 0: hitachi hts541680T..... Warning
>> > > immediately back up your data and replace your hard dick drive. A
>> > > failure may be imminent..
>> > >
>> > >
>> > > Does not sound positive ha ha ha.. so do i assume my hd is stuffed
>> > and
>> > > dont bother running the second step then?
>> > >
>> > >
>> > > --
>> > > sands vs > >[/color][/color]
>
>
> --
> sands vs[/color]

sands vs wrote:[color=blue]
> Ah good, well at least it gives me an excuse to piss off the 67 gig hd
> and get a bigger one... ;) Are WD hard drive ok or is samsung better
> thats the brands im looking at..
>
> ;1043693 Wrote:[color=green]
>> Yes that is correct. Hard drives monitor themselves and yours is
>> failing.
>> Backup what you want off your drive as it may fail completely soon.
>>
>>
>> --
>> ..
>> --
>> "sands vs" <guest@xxxxxx-email.com> wrote in message
>> news:3a22fecd129a0a1eba4b6a520371f840@xxxxxx-gateway.com...> > >[color=darkred]
>>>> well i left it do the... chkdsk c: /r
>>>>
>>>> As described and it took about 15 hours and came up with the
>>> following
>>>> message
>>>>
>>>> Smart failure predice on hard dick 0: hitachi hts541680T..... Warning
>>>> immediately back up your data and replace your hard dick drive. A
>>>> failure may be imminent..
>>>>
>>>>
>>>> Does not sound positive ha ha ha.. so do i assume my hd is stuffed
>>> and
>>>> dont bother running the second step then?
>>>>
>>>>
>>>> --
>>>> sands vs > >[/color][/color]
>
>[/color]


I've had a lot of WD failures, many seemed to have bad controllers that
overheated, of course they may have addressed that problem - or not.

Seagate seem okay, try and mount it with as much airflow as you can,
while it's apart see if there's a place and connector for an extra fan.