mailing list archives
Re: nmap -P0 reboots Windows XP
From: Kris Katterjohn <kjak () ispwest com>
Date: Tue, 07 Mar 2006 19:03:23 -0600
Kris Katterjohn wrote:
If you disable auto-reboot on error, do you get a blue screen or error
On 3/7/06, Kris Katterjohn <kjak () ispwest com> wrote:
I didn't know you could do that. I googled it, turned it off and got a BSOD:
So I googled that and saw that it sometimes comes up because of hardware
failure. I installed some more RAM in that box last week, but haven't had any
problems with it. It's a lesser used box that dual-boots Windows and Linux,
but both have been used for normal things and have worked fine.
I took the RAM out, tried nmap about 20 times and Windows didn't reboot at
all. So the RAM was apparently the root of the problem, but winpcap/nmap was
the thing that caused it.
Now I'm off to see what I can do about this.....
Thanks a lot,
Okay, I know this probably isn't the place to discuss this, so if it gets to
be too many emails on this or something, I'll take it off the list. Or,
Fyodor, just ask whenever and I'll do it and try to just email some people.
I had a few people email me about memtest86 and memtest86+ (and thanks again
to those of you who did). 0 errors.
I mentioned this to Daniel Roethlisberger (who emailed me about memtest86+):
Both Windows and Linux see all the RAM. I had done tcpdump, nmap, and plenty
of other things on Linux on that box after the RAM was installed and before
the Windows problem. I didn't have any problems whatsoever. Windows seemed
fine before winpcap/nmap was installed on there. I don't actually think it was
winpcap or nmap broke it, but something Windows did. Or: winpcap/nmap did
something, but Windows messed it up. Does anybody have any idea what Windows
would do or cause to mess up when the RAM seems fine and Linux has no problem
New RAM: okay
Linux + new RAM: okay
Linux - new RAM: okay
Windows + new RAM: bad
Windows - new RAM: okay
Sent through the nmap-dev mailing list