Member Avatar for scdarkmarine

NOt sure if this is the right forum. Please redirect if not. Anyways here's my problem:

randomly and sometimes multiple times. When I start my computer up it goes to the blue screen with this error:

A problem has been detected and windows has been shut down to prevent damage to your computer
DRIVER_CORRUPTED_MMPOOL

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

anyways here's the technical info:
***STOP: 0x000000D0 (0x00000003, 0x00000002, 0x00000001, 0x80547ED87)
Beginning dump of physical memory. Physical memory dump complete. Contact your system administrator or technical support group for further assistance.
-----------------------------------------------
Once it finally loads... It says your settings have changed do you want to keep them. (From msconfig). I then notice that dumprep and mlzosp88.dll and some other dll i don't remember (unclicked them)

******mlzosp88.dll********** I Googled and is not there! or on microsoft's page.

  • 3 Contributors
  • 4 Replies
  • 542 Views
  • 19 Hours Discussion Span
  • Latest Post Latest Post by scdarkmarine

Dani AI

Generated

A kernel-mode component (driver or rootkit) corrupting kernel memory is the most likely cause of DRIVER_CORRUPTED_MMPOOL. The thread shows signs of a startup component that behaves like malware and a large number of infected files; the temporary success from booting with a previous configuration is consistent with a kernel driver or autorun module being the trigger. Deleting system files can make the machine bootable but often leaves the install fragile; safer isolation and repair is preferable.

Suggested sequence of remediation and triage:

  • Isolate the machine from networks.
  • Boot to Safe Mode or from a trusted rescue environment and collect a minidump for analysis if possible.
  • Use a startup-inspection tool (Autoruns/alternative) to disable suspicious autorun entries rather than immediately deleting files. Disabling makes it easier to reverse changes.
  • Run multiple up-to-date scanners (on-line/full-system plus an offline rescue ISO) and a rootkit scanner; some kernel-capable infections require an offline scan to remove completely.
  • Repair any removed or damaged system files with sfc /scannow (from an elevated prompt or recovery console) and check disk integrity with chkdsk /f.

Crash-dump and log analysis is useful for pinpointing the offending driver: a minidump is often sufficient and tools such as a debugger or crash-viewer will show which kernel module was involved. That aligns with ’s advice to post dumps for analysis. Also follow ’s suggestion to review Device Manager and consider System Restore points before attempting invasive fixes.

If automated cleanup fails or the infection count is very large, a staged approach—backup personal data, format, and clean install—is the most reliable way to guarantee a clean environment. Change all account passwords after recovery and reinstall drivers only from trusted vendor sites. Deleting kernel files without a plan risks a repair-install; disabling entries and using recovery tools is safer.

Recommended Answers

All 4 Replies

Member Avatar for joshSCH

hmm I've never heard of "mlzosp88.dll" either. Have you tried a system restore? Look in the device manager for yellow exclamation marks, and check if there are any driver problems with some of your hardware.

Did this error just happen all of a sudden? Or have you recently installed hardware?

Member Avatar for scdarkmarine

*********UPDATE found some more info*********
I just restarted my comp again (just now because I got explorer 7) i mainly use ozilla. Anyways... The MSCONFIG thing came up again!!


INFORMATION FROM MSCONFIG:

Both DLLS = mlzosp88 and jsdmio26

Command = %systemroot%\system32\Rundll32.exe "%systemroot%\system32\mlzosp88.dll", Start

Command = %systemroot%\system32\Rundll32.exe "%systemroot%\system32\jsdmio26.dll", Start

Both Locations =
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

MORE INFO:
Did a driver verify and more stuff that doesn't show up on google came up!!
mlzosp88.sys (description) = Kernal
jsdmio26.sys = Kernal
rllstl20.sys = Kernal <------- not on google

1 last thing I could find was when the microsoft scan finished it found ZLOB!!! and some other win stuff not infected it said though. Like 250+ infected files. Did adaware and spybot and nothing now hopefully that fixed it.

I don't know when the problem started... It's just random when it boots up like this... This is what I posted in another forum. See if it helps you to figure it out. I'm trying to get multiple oppinions before i have to wipe my computer!!! :(

Member Avatar for Nestea

analyze your startup entries with this tool:

> Did a driver verify and more stuff that do [...]
What program did you use?

you could try to post a .dmp file. If a minidump will make it, doubtful. but a complete memory dump would be to big to post.
like here: http://www.daniweb.com/techtalkforums/thread75437.html

and post a snippet with your startup entries.

Member Avatar for scdarkmarine

well I took a wild guess when my computer was blue screening CONSTANTLY NON-STOP. I just deleted those system files lol... Then I instead of booting safe mode booted with last good settings =)))). WORKED... Then my bro clicked debug when some error came up and idk lol.. Maybe this is the end of the SUPER trojan or whatever you want to call my problem...

Anyways I'll post back if it reoccurs..... GG for now haha.

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.