Member Avatar for Techno22

Frequently at start up I get a message saying;

A problem has been detected and Windows has been shut down
to protect your computer.

Stop OX00009088(OXABA2EBA8, OXABA2EBAC, OXABA2EBAO, OXABA2EBA4).

Physical memory dump failed with status OXCODOO9C.

Contact your system admin.

I have to say that, unfortunately, all of those numbers mean absolutely nothing
to me, and I would appreciate any help I can get.
Incidentally, laptop seems to work fine in between times.

  • 7 Contributors
  • 11 Replies
  • 411 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by Techno22

Dani AI

Generated

Intermittent startup BSODs that include a "Physical memory dump failed" message generally mean Windows could not write the crash dump when the system failed. That failure often points at disk/paging-file problems or bad RAM rather than a single corrupted OS file. Because the laptop runs normally between crashes (as reported), a staged diagnostic approach is best: capture dumps when possible (as recommended), but if dumps fail to save then prioritize disk and memory checks first. ’s minidump approach is still a good next step once dump writing is restored.

Quick prioritized checklist:

  1. Back up important files before further testing.
  2. Verify system drive free space and that the pagefile is enabled and system‑managed on the boot drive (Windows needs a valid pagefile to write many dump types).
  3. Check and repair the disk: from an elevated prompt run chkdsk C: /r and allow it to run at next boot.
  4. Verify system integrity with sfc /scannow.
  5. Run memory testing: Windows Memory Diagnostic and a multi‑pass Memtest86+ boot (bad RAM often causes intermittent startup BSODs).
  6. Reseat RAM modules and, if possible, test modules one at a time or swap with known‑good sticks.
  7. Inspect Event Viewer for disk I/O or bugcheck entries (record any stop codes and module names).
  8. If a third‑party updater (SlimDrivers) was used, prefer OEM or Windows Update drivers—roll back recent driver installs or use System Restore to a point before the updater.
  9. Run vendor hardware diagnostics and consider a BIOS/firmware update if recommended by Toshiba.

If the crash stops after these checks, continue periodic backups and occasional diagnostics. If it recurs and minidumps become available, use a dump viewer (as suggested) or WinDbg for deeper analysis and act on any failing component (drive or RAM) identified; a repair install or clean OS reinstall should be last resort.

Recommended Answers

All 11 Replies

Member Avatar for JorgeM

These BSODs are sometimes challanging to troubleshoot. They can be caused due to failing hardware, or a problem with a driver.

Have you recently installed anything in your computer that you recall began causing this issue?

Member Avatar for Techno22

Nothing installed recently.
All drivers are up to date according to Slim Drivers programme.
That free programme would be one of the last things that I installed
and it would have updated drivers at the time.
I would not know now which drivers were updated.
I could uninstall Slim Drivers but, as you know, that probably would
not do anything for changes made to the drivers.

Member Avatar for caperjack

this option/program i find easier ,you may not get any info because of the memory dump failure ,but worth a try ..download link at the bootom of the page
If you follow these directions you should end up with a few BSOD events recorded and a place for us to start looking -

Please download BlueScreenView http://www.nirsoft.net/utils/blue_screen_view.html (in zip file)•Extract (right-click > Extract all) the contents of bluescreenview.zip.

•Double-click on the BlueScreenView.exe file, to run the program. (No installation is required.)

•When scanning is done (usually complete by the time the interface appears), go ...

•Edit > Select All

•File > Save Selected Items, and save the report to your Desktop as BSOD.txt.

•Close the BlueScreenView window... ... ...

•Open BSOD.txt using Notepad and go ... .... ..

•Edit > Select All

•Edit > Copy, and then paste the entire contents of the text file into your next reply.

Edited by caperjack
Member Avatar for Techno22

Sincere apologies to JorgeM and to caperjack for delay in getting back which
has been caused by an illness in the family.
Grateful thanks for your replies.
Will return to this at the earliest opportunity.
Thanks again.

Member Avatar for johhny-marshal

That Message shown on the blue screen of Windows is generated when some file of the Windows gets corrupted or the Windows itself gets crashed.

Member Avatar for Techno22

Again, apologies for delay in getting back.
The problem has not happened for nearly a month now.
Should it be safe to trust?
Thanks.

Member Avatar for jean122

If its not returning, for a few months.
its ok, you should not be worried.
if its returning I recommend reinstall windows or upgrade to windows 7

Gr Jeannot

Member Avatar for 3knur8

if nothing was recently installed, and all the drivers were 'up to date', then it could have been caused by a windows update. sometimes your hardware uses windows update to download and install the newest drivers. there could have been a problem with compatibility with one of the drivers through the update.

Member Avatar for Rajneshwar

Try Safe Mode/Check for Hardware(disconnect each to check this)

Member Avatar for Techno22

This really does seem to have sorted itself.
I will be holding on to caperjacks recommendations
in case the problem raises its head again.
Grateful thanks to all who replied to this, and sincere apologies to those who were
affected by my delay in getting back.
It was unavoidable and I very much appreciate your patience.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.