BSOD probably due to one/some/all Firefox/Flash Player/Laptop Speakers

I'll ask the forum owner to have a look.

May be worth checking antvirus settings....

It almost 10pm here, so I won't be able to look tonight. If someone doesn't get to it before tommorrow evening, I promise to look at the issue when I get home from work.

Now, I'm a bit more nervous. It crashed twice more. I was on a long phone call so I don't exactly remember what all was running. While I was on the call, it crashed and restarted. When the login screen came on, i entered the password and logged in. But all I got was the welcome screen, as the desktop just didn't appear. After a while due to the power saving setting the screen turned dark. I waited for a while, but as nothing happened, i forcibly shut it down using the power button. Not sure what is going wrong. Please have a look. I am uploading the 4 error logs to G-Drive and sharing it as the toolbar still doesn't work for me. https://drive.google.com/file/d/0B5S...ew?usp=sharing https://drive.google.com/file/d/0B5S...ew?usp=sharing https://drive.google.com/file/d/0B5S...ew?usp=sharing https://drive.google.com/file/d/0B5S...ew?usp=sharing

I'll try to help Golden while he is sleeping, here is what the dump file is saying

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {c02afdd4, c0000185, 83b47be0, abf75000}
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+2fa )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: c02afdd4, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 83b47be0, current process (virtual address for lock type 3, or PTE)
Arg4: abf75000, 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: There was error with disk hardware

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

If that passes, run Seatools for DOS SeaTools for DOS and Windows - How to Use