Re: Beginning dump of physical memory

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello, Groenie!

G> Hi
G> I am getting a blue screen when booting the pc up with error: "Beginning
G> dump of physical memory". When I reboot the error is goes away only to
G> appear again next time when booting up. Can anyone tell me how to fix
G> this?

Usually in the BSOD ( blue sceen of death ) there is information what driver failed with what exception.
Driver names end with *.sys. If you're lucky and the driver is 3d party device driver for some hardware you can uninstall it. OTOH if it is one of the system components then running windows installation in repair mode can fix the problem.

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com

Relevant Pages

  • Re: Code 39 - Missing processor driver/mono sound
    ... Perform the fix as described in the KB and then post back with any left over issuethat comes up. ... Reboot after doing the fix. ... missing processor driver, it's just talking about CD drives. ... have disconnected my Data drive, suspecting that this may be faulty, and so ...
    (microsoft.public.windowsxp.general)
  • Re: NIC issue or other?
    ... Had to reboot the server to fix it. ... The driver is built into the kernel. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: Squeeze boot takes 9 minutes; no sound and no 3D acceleration
    ... Booting takes 9 minutes to login screen. ... probably caused by manually installed NVidia drivers 3 years ago. ... decide what driver to use becasue squeeze ... have to decide what set to install: ...
    (Debian-User)
  • Re: Screen problem on booting
    ... On booting, all the ... In console mode, reset command doesn't fix the problem. ... I thought maybe it was a problem that occurred with whatever graphics driver ... I think that first video driver can be the problem... ...
    (freebsd-questions)
  • Re: Screen problem on booting
    ... On booting, all the ... In console mode, reset command doesn't fix the problem. ... I thought maybe it was a problem that occurred with whatever graphics driver ... I think that first video driver can be the problem... ...
    (freebsd-questions)