#223 closed defect (invalid)
Strange Windows 2003 guest BSOD
| Reported by: | rr | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 1.3.8 |
| Keywords: | bsod, windows 2003, crash | Cc: | |
| Guest type: | other | Host type: | other |
Description
A strange guest os crash occurred which I am unable to reproduce. The machine probably was idle.
Attached a windows 2003 server memory dump bugcheck and parts of the release log.
Host os was debian etch/Linux 2.6.18-3-k7
Attachments (5)
Change History (7)
by , 17 years ago
| Attachment: | w2003-bugcheck.txt added |
|---|
by , 17 years ago
| Attachment: | vbox-releaselog.txt added |
|---|
Virtualbox release log at the time of crash
by , 17 years ago
| Attachment: | w2k3-bugcheck.txt added |
|---|
Bugcheck of a new crash, fresh guest OS reinstall, was not idling
follow-up: 2 comment:1 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
The reporter has switched to different host hardware and the problem hasn't occurred since then. He wrote that the new system has "same distro, same kernel, same cpu type (Athlon XP) but different models, different mobo, different ram, different disks". Actually the kernel is slightly different (failing host 2.6.18-3-k7, working host 2.6.18-4-k7). The model difference is XP 1600+ (failing) versus XP 2000+ (working). The CPUID of the XP 1600+ has two additional flags, APIC and MP, but those shouldn't be visible inside the guest anyway (APIC can be enabled, though).
comment:2 by , 17 years ago
Replying to klaus:
The reporter has switched to different host hardware and the problem hasn't occurred since then. He wrote that the new system has "same distro, same kernel, same cpu type (Athlon XP) but different models, different mobo, different ram, different disks". Actually the kernel is slightly different (failing host 2.6.18-3-k7, working host 2.6.18-4-k7). The model difference is XP 1600+ (failing) versus XP 2000+ (working). The CPUID of the XP 1600+ has two additional flags, APIC and MP, but those shouldn't be visible inside the guest anyway (APIC can be enabled, though).
I actually found a hardware problem on the host (memtest86 test5 found errors)
windows 2003 kernel dump bugcheck