VirtualBox

Opened 10 years ago

Closed 9 years ago

#13167 closed defect (fixed)

Windows 8.1 crashes with kernel_data_inpage_error

Reported by: Jan Rüegg Owned by:
Component: other Version: VirtualBox 4.3.12
Keywords: Cc:
Guest type: Windows Host type: Linux

Description

I get a lot of crashes when running Windows 8.1 64-bit within a linux host environment...

The machine gets a bluescreen and I have to reset the virtual machine. Otherwise, everything works fine.

Its running 64-bit on 64-bit host.

Attachments (2)

Win8-2014-07-04-14-11-46.log (90.0 KB ) - added by Jan Rüegg 10 years ago.
Logfile up to the crash
Win8.vbox (69.1 KB ) - added by Jan Rüegg 10 years ago.
Virtual machine configuration

Download all attachments as: .zip

Change History (8)

by Jan Rüegg, 10 years ago

Logfile up to the crash

by Jan Rüegg, 10 years ago

Attachment: Win8.vbox added

Virtual machine configuration

comment:1 by Jan Rüegg, 10 years ago

This is the crash dump analysis:

On Thu 03.07.2014 10:53:19 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\070314-17734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0) 
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009C, 0xFFFFE0003AA500D8, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

According to this website: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559211%28v=vs.85%29.aspx

0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
Last edited 10 years ago by Jan Rüegg (previous) (diff)

comment:2 by Frank Mehnert, 10 years ago

priority: blockercritical

comment:3 by Jan Rüegg, 10 years ago

I suspected this only happens when running with multiple processors enabled. However, the problem also appears when started with only 1 processor exposed to the host (instead of four)...

comment:4 by Frank Mehnert, 9 years ago

Still reproducible with VBox 4.3.20?

comment:5 by Jan Rüegg, 9 years ago

I don'tknow, not using it currently...

comment:6 by Frank Mehnert, 9 years ago

Resolution: fixed
Status: newclosed

Then please reopen if necessary.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use