1 files changed, 51 insertions, 0 deletions
diff --git a/results/classifier/111/review/1355644 b/results/classifier/111/review/1355644
new file mode 100644
index 00000000..05377fa3
--- /dev/null
+++ b/results/classifier/111/review/1355644
@@ -0,0 +1,51 @@
+semantic: 0.201
+graphic: 0.162
+device: 0.113
+other: 0.100
+boot: 0.053
+performance: 0.052
+socket: 0.050
+vnc: 0.047
+debug: 0.046
+PID: 0.044
+network: 0.039
+files: 0.037
+permissions: 0.034
+KVM: 0.021
+debug: 0.673
+performance: 0.058
+boot: 0.050
+PID: 0.035
+other: 0.034
+files: 0.030
+device: 0.022
+network: 0.020
+semantic: 0.019
+socket: 0.019
+KVM: 0.012
+graphic: 0.012
+vnc: 0.010
+permissions: 0.007
+
+windows7 reboot bluesreen 0x0000005c
+
+I have met sevaral blue screen with 0x0000005c(0x0000010b,0x00000003,0x00000000,0x00000000) after windows7 reboot.
+It always happens just before the windows iron animation appears.
+
+my qemu version is qemu-2.1.0
+my guest os is windows7 32bits sp1
+
+my qemu commandline is 
+./x86_64-softmmu/qemu-system-x86_64 -m 2048 -hda system.inst -spice port=5940,disable-ticketing -monitor stdio --enable-kvm
+
+This bug  doesn't happen always，and i don‘t know how to reproduce it.
+
+But i have a special way to produce such a bluescreen.
+I set nmi dump on and set windows to collect dump file and set auto reboot after system fail on. 
+Then i send a nmi to guest, and then after collecting dump file , windows will auto reboot and then such a blue screen happens.
+And this can be  reproduced always.
+
+Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+