W7 Freezes, and Then BlueScreens - Details In Post

Hi,

In the paperclip you will see my minidump file. I dont know what it contains as i cant open it. (Try and open it with wordpad if its possible, but it says access is denied) .

Well, a few days ago my W7 started to blue screen. It usually occurs when playing songs in WMP10 (but dont think its all the time).

The first BSOD i got was the KERNEL_DATA_INPAGE_ERROR and it did a physcial memory dump.

I then tried to reboot the PC and got UNMOUNTABLE_BOOT_VOLUME. I fixed this with W7, but my PC keeps locking up. (It usually locks up and then blue-screens) but sometimes it manages to unfreeze itself and carry on as normal.

This is quite frustrating as i cant find answers anywhere

Hopefully the Zip File works, zipped with 7-Zip

Thanks

James

AMD Athlon 64 3000+ 2.00GHz
Asus K8v Motherboard
Seagate 80GB HardDrive
Seagate Maxtor 80HardDrive
1.5GB Ram
Nvidia 7600GS

EDIT: I go to Zip it and it says ACCESS DENIED.

My System Specs are there above if that helps. Will try and edit them soon as possible. Any ideas

Hi James; Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.

You can make this easier by downloading Speccy.

Unfortunately, your attached zip file is empty. Try it again.

Can you drag the dmp files to your desktop and zip them from there?

There was a dmp file this time; but it is incomplete. We will work with what we have.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0527948, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: 530988c0, current process (virtual address for lock type 3, or PTE)
Arg4: a4f29000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82b0561a to 82b2dd10

STACK_TEXT:  
89703a94 82b0561a 0000007a c0527948 c000000e nt!KeBugCheckEx+0x1e
89703b08 82afd0e5 8581967c 89703b60 82b85300 nt!MiWaitForInPageComplete+0x2fd
89703b9c 82ad8e5f 82b85300 a4f29000 858195e8 nt!MiIssueHardFault+0x3b2
89703c20 82ab789f 00000000 a4f29000 00000000 nt!MmAccessFault+0x2656
89703c9c 82c8298e 8463d308 8463d308 8463d330 nt!MiDeleteSegmentPages+0x80
89703ccc 82a7cf39 8463d308 00000000 00000000 nt!MiSegmentDelete+0xec
89703d28 82a7ce51 84539920 00000000 00000000 nt!MiProcessDereferenceList+0xdb
89703d50 82c5f6bb 00000000 97ab880c 00000000 nt!MiDereferenceSegmentThread+0xc5
89703d90 82b110f9 82a7cd8a 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiWaitForInPageComplete+2fd
82b0561a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiWaitForInPageComplete+2fd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x7a_c000000e_nt!MiWaitForInPageComplete+2fd

BUCKET_ID:  0x7a_c000000e_nt!MiWaitForInPageComplete+2fd

Followup: MachineOwner

Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

You have some really old drivers. These drivers are dated way before Vista was released.

ac97via.sys Nov 22 2004 - is related to VIA Audio WDM Driver. Manufacturer: VIA Technologies, Inc. www.via.com.tw
ov519cmd.sys Aug 29 2002 - OmniVision USB Camera drivers are way obsolete for a 2009 Windows 7 installation
ov519vid.sys Feb 25 2003 - OmniVision USB Camera drivers are way obsolete for a 2009 Windows 7 installation

Update these drivers if possible or uninstall the programs/hardware to which they are related. Let's try this and see where you stand.

Have you tried to update them? Does you webcam appear in Device Manager? If you can't update them, you need to delete them. My old webcam doesn't work either with Win 7.

After you resolve the driver issue, download install, and run Malwarebytes. Let's make sure you don't any virus or malware. What antivirus do you use?