Nmap Development mailing list archives
FATAL Bad Memory Block.
From: Mark Huss <mark.huss () systemexperts com>
Date: Wed, 25 Nov 2015 09:41:12 -0500
Since updating to v7 , whenever I run nmap on my laptop I get somewhere
between 'a couple of' to 'large streams' of the error above, depending on
the options on the command line. In between all the error messages nmap
seems to be working ok and printing out the appropriate messages. I did a
site search and found no mention of this particular error.
Win7 x64 SP1 i7 2620M CPU 4G RAM(>2G available)
Nmap 7 seems to work fine on my larger box (Win7 x64 SP1 16GB RAM). Is 2GB
too little to run nmap in now?
Examples:
nmap -p 25 -Pn -v -v -v -Pn {IP} -- ( a couple of errors:)
Starting Nmap 7.00 ( https://nmap.org ) at 2015-11-25 09:25 Eastern Standard
Time
Initiating Parallel DNS resolution of 1 host. at 09:25
Completed Parallel DNS resolution of 1 host. at 09:25, 0.02s elapsed
DNS resolution of 1 IPs took 0.64s. Mode: Async [#: 5, OK: 1, NX: 0, DR: 0,
SF:0, TR: 1, CN: 0]
Initiating SYN Stealth Scan at 09:25
Scanning {host (IP)} [1 port]
FATAL Bad Memory Block.
FATAL Bad Memory Block.
Completed SYN Stealth Scan at 09:25, 2.15s elapsed (1 total ports)
Nmap scan report for {host (IP)}
Host is up, received user-set.
Scanned at 2015-11-25 09:25:42 Eastern Standard Time for 2s
PORT STATE SERVICE REASON
25/tcp filtered smtp no-response
Read data files from: C:\Program Files (x86)\Nmap
Nmap done: 1 IP address (1 host up) scanned in 2.95 seconds
Raw packets sent: 2 (88B) | Rcvd: 0 (0B)
nmap -p 25 -T4 -A -v -v -v -Pn {IP} -- LOTS of errors:
Starting Nmap 7.00 ( https://nmap.org ) at 2015-11-25 09:25 Eastern Standard
Time
[.]
Initiating OS detection (try #1) against { host (IP) }
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
Initiating Traceroute at 09:23
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
Completed Traceroute at 09:24, 9.14s elapsed
[.]
Mark Huss | | <mailto:mark.huss () systemexperts com>
mark.huss () systemexperts com
SystemEXPERTS | Leadership in Security & Compliance
Attachment:
smime.p7s
Description:
_______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- FATAL Bad Memory Block. Mark Huss (Nov 30)
- Re: FATAL Bad Memory Block. Daniel Miller (Nov 30)
- RE: FATAL Bad Memory Block. Mark Huss (Nov 30)
- Re: FATAL Bad Memory Block. Daniel Miller (Nov 30)
