Tech Support Guy banner
  • Please post in our Community Feedback thread for help with the new forum software! If you are having trouble logging in, please Contact Us for assistance.
Status
Not open for further replies.
1 - 2 of 2 Posts

·
Registered
Joined
·
23 Posts
Discussion Starter · #1 ·
Hi All,
well i have a problem with my windows vista just freezing up the after about 3 Min's it will go to a blue screen do a mini dump then restart.
Could someone please have a look at the mini dump and let me know what i need to fix.
Thanks for your help!
Regards
Andrew
 

Attachments

·
Registered
Joined
·
45,855 Posts
The bugchecks are mostly pointing to an issue with the disk hardware. Cables may need to be reset -- and chkdsk should certainly be run; you may have bad blocks or sectors on the drive.

Have a look also in the Event Viewer (run eventvwr.msc) and look at the System log for "NTFS" errors.

After running chkdsk, examine and repost the log that will be available in the Event Viewer > Applications Log > Wininit entry. Double click it to read the description.

All but the oldest that I have examined are the same as this >>

BugCheck 7A, {fffff880093149c0, ffffffffc000000e, 2f4b9860, fffff960001bf220}

Probably caused by : win32k.sys ( win32k!xxxButtonEvent+9cb )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Debug session time: Mon Aug 17 01:11:45.200 2009 (GMT-7)

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: fffff880093149c0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000002f4b9860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff960001bf220, 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

---------------------------------------------------------------------
Debug session time: Tue Aug 4 05:28:45.118 2009 (GMT-7)

BugCheck 9F, {3, fffffa80018b91c0, fffffa80018b91c0, fffffa80062cdc10}

Probably caused by : acpi.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80018b91c0, Physical Device Object of the stack
Arg3: fffffa80018b91c0, Functional Device Object of the stack
Arg4: fffffa80062cdc10, The blocked IRP
 
1 - 2 of 2 Posts
Status
Not open for further replies.
Top