RE: Flushing DLLs follow-up
From: Frank Heyne (fh@rcs.urz.tu-dresden.de)Date: 10/24/01
- Previous message: DE VILLIERS IAN: "RE: Flushing DLLs follow-up"
- Maybe in reply to: H C: "Flushing DLLs follow-up"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Message-ID: <20011024065546.2325.qmail@securityfocus.com> From: Frank Heyne <fh@rcs.urz.tu-dresden.de> To: DE VILLIERS IAN <ian.devilliers@bmw.co.za>, "'forensics@securityfocus.com'" <forensics@securityfocus.com>, "'focus-ms@securityfocus.com'" <focus-ms@securityfocus.com> Date: Wed, 24 Oct 2001 08:55:39 +0200 Subject: RE: Flushing DLLs follow-up
On 24 Oct 01, at 8:21, DE VILLIERS IAN wrote:
> I used a reasonably effective although probably unorthodox way of dumping
> the memory to disk - check that your crash recovery options dump the
> complete RAM to disk and cause a blue screen.
How do you cause a blue screen on a fully patched system? Is it possible
when you are logged on as a normal user or do you need to run under admin
account to do this?
Greetings
Frank Heyne
- Previous message: DE VILLIERS IAN: "RE: Flushing DLLs follow-up"
- Maybe in reply to: H C: "Flushing DLLs follow-up"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
