1 files changed, 52 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1355644 b/results/classifier/118/graphic/1355644
new file mode 100644
index 000000000..88b19478e
--- /dev/null
+++ b/results/classifier/118/graphic/1355644
@@ -0,0 +1,52 @@
+graphic: 0.805
+x86: 0.735
+device: 0.544
+semantic: 0.465
+performance: 0.381
+ppc: 0.360
+architecture: 0.319
+boot: 0.296
+user-level: 0.292
+permissions: 0.268
+network: 0.246
+socket: 0.235
+register: 0.234
+debug: 0.229
+PID: 0.212
+vnc: 0.196
+risc-v: 0.185
+files: 0.180
+mistranslation: 0.179
+peripherals: 0.174
+arm: 0.162
+kernel: 0.156
+VMM: 0.127
+hypervisor: 0.123
+virtual: 0.121
+TCG: 0.093
+i386: 0.075
+assembly: 0.038
+KVM: 0.036
+
+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.]
+