BSOD Kernel_data_inpage_error after reimaging computer

[cong]

Dear experts,

I have a less than 6 months old Asus N53SM laptop running Windows 7 home premium. Yesterday after I put it in sleep mode to pack it up to go to work, I heard a crunching noise coming from my laptop. When I got in to work, I turned on my laptop like I do everyday and long behold, I could not boot. It showed a black screen followed by error indicating that it could not boot from the hard drive and it was looking to boot from the CD-ROM. I also received a message that my registry was corrupt. My attempt to restore to a good configuration failed.

I called Asus support and they had me remove my power cable, battery and hold down the power button for 20 seconds but it still didn't work. I was still not able to boot from hard drive. The final resort they advised was to re-image with AI Recovery disks. After I spent all day doing that yesterday I managed to log into windows but I am faced with more BSOD. The latest is Kernel_data_inpage_error, Stop 0x0000007A.

Am I having a hardware or software issue? This is my first time with Asus computers. I love this laptop but I didn't have this kind of issues early on when I owned Sony VAIO's in the past.

Please help. I've uploaded the diagnostic files.

 

[cong]

WinDbg info:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800aa54a00, fffff80000b9c3d8, fffffa800e7d96d0}

Probably caused by : usbccgp.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: fffffa800aa54a00, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800e7d96d0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff880054a4000 usbccgp

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c388 fffff800`0333b6d2 : 00000000`0000009f 00000000`00000003 fffffa80`0aa54a00 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`032dbc3c : fffff800`00b9c4d8 fffff800`00b9c4d8 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`00b9c430 fffff800`032dbad6 : fffffa80`0bcc0168 fffffa80`0bcc0168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`032db9be : 00000020`7630fffb fffff800`00b9cb18 00000000`000da31c fffff800`03446608 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`032db7a7 : 00000006`f56f06c5 00000006`000da31c 00000006`f56f06d9 00000000`0000001c : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`032c8cca : fffff800`03443e80 fffff800`03451cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys

BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys

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