Random BSOD ( Win 7) Complete details!

[FlickDota]

A problem has been detected and windows has been shut down to prevent damage to your computer.

If this is the first time you've been this stp[ error screen.
Restart your computer. If this screen appears again follow this steps:

Check to be sure you have adequate disk space. If a driver is identified in the stop message disable the driver or check with the manufacturer for drver updates. Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable bios memory opt such as catching or shadowing. If you need to use safe mode to remove or siable components.l Restart your pc.

Technical information

*** STOP : 0x0000007e (0xFFFFFFFFC000001D, 0xFFFFF9900109893C, 0xFFFFF88002FB9538,0xFFFFF88002FB8D90)

*** ataport.SYS - Address FFFFF8800109B93C base at FFFFF8800107D000 , Datestamp 51fef9b5

Collecting data for crash dump...
Initializing disk for crash dump...
Begnning dump of ph memory..
Dumping ph memory to disk : 100
Phy memory dump complete..
Contact your system admin or tech support grup.


Can someone help me. I get this BSOD everytime i play / Watch / Or surf.


Thank you in advance!

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[FlickDota]

Ok here first file are the files i get after using DM logger

 

[FlickDota]

And after getting that BSOD. My pc randomly restarts. :/

 

[Boozad]

Hi FlickDota,

Unfortunately the file you provided is incomplete, and we need more information to analyze your logs properly. Follow Blue Screen of Death (BSOD) Posting Instructions, let the tool run until it has completely finished and then upload the new logs.

 

[Boozad]

While we're waiting for the new logs I'll give you a couple of suggestions based on what's been provided so far.

First off it looks as if there is a problem with your HDD.

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

:ar: Download and run SeaTools to check the health of your drive.

:ar: Run chckdsk to check the drive for system file errors and bad sectors. http://www.sevenforums.com/tutorials/433-disk-check.html

Secondly, your latest dump shows memory corruption.

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff8800109b93c, fffff88002fb9538, fffff88002fb8d90}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

:ar: Followup: memory_corruption

Download MemTest86+, this will check your RAM for errors. Run MemTest86+ for at least 8 passes, preferably overnight. We're looking for zero errors here.

Post back with your results.

 

[FlickDota]

Hello there. Sorry for late reply. So i use the SF DIAGNOSTIC TOOL NOW and here it is.

Btw after that BSOD. Suddenly my pc randomly restarts.

 

[Boozad]

Thanks for the logs, I'll take a look through them now. Did you see the steps provided in my previous post?

 

[FlickDota]

Im doing the Seatool things now. I will upload results after. Thank you for your fast reply.

 

[FlickDota]

I already did that Seatools. But it fails

 

[Boozad]

Run the chckdsk.

 

[FlickDota]

Bump

 

[Boozad]

Bump? I gave you three steps, first failed so I reiterated the second step and you ignore it?

 

[FlickDota]

Oh i havent seen this second page. Btw i already run chkdsk 2x. It says 0 bad sectors / and Volume is clear.

Have you seen any errors so far?

 

[Boozad]

Did you run MemTest86+?