Random BSOD.....

[NecroticisM666]

Good day guys!

There are times that a random BSOD happens to my laptop running Windows 7 x64bit and I don't know why. So I want to seek your help to diagnose and solve it. My laptop currently has a dual boot OS comprising of Windows Vista and Win7 so I wonder if that's where the problem is coming from..can you help me guys? Thanks in advance!

Here's the debug files:

View attachment 325918

 

[HarriePateman]

OKay so i have had a look at your DMP files and it is quite interesting:

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

[COLOR="Red"]KERNEL_DATA_INPAGE_ERROR (7a)[/COLOR]
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 [COLOR="red"]0xC0000185[/COLOR],
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: fffff6fc0001e158, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 0000000030ce1860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80003c2bc50, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: [COLOR="red"]There was error with disk hardware[/COLOR]

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [COLOR="red"]CODE_CORRUPTION[/COLOR]

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

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

[COLOR="red"]KERNEL_DATA_INPAGE_ERROR (7a)[/COLOR]
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 [COLOR="red"]0xC0000185[/COLOR],
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: fffff6fc806170c0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000001f9cb880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff900c2e18ff8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - [COLOR="red"]The I/O device reported an I/O error.[/COLOR]

DISK_HARDWARE_ERROR: [COLOR="Red"]There was error with disk hardware[/COLOR]

BUGCHECK_STR:  [COLOR="red"]0x7a_c0000185[/COLOR]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

As we can see both of the DMP Files are pointing toward some form of memory corruption.

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR

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

Open an elevated command prompt and enter: CHKDSK C: /F /R then press ENTER to repair corrupt sectors, if there are any.
NOTE!!: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop. You can check the log of chkdsk by going to Event Viewer >> Windows Logs >> Application. Under the Source column locate Wininit entries.

Run Memtest86+ overnight, after your computer has been off for about an hour . Let it run for at least 7 passes / 6-8 hours. If errors appear you can stop that particular test.
Note!! Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Test RAM sticks individually. When you find a good one then test it in all slots. Post back with the results.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[NecroticisM666]

Thanks for the input HarriePateman, will do this tonight and post the results/outcome when it's finished. Thank you.

 

[HarriePateman]

No worries.