BSOD when playing BF4, ntoskrnl.exe is the driver

I made an attachment. Please do not make me download a program that I am not familiar with. I am having a hard time here and this is very frustrating. I have a text file created by bluescreenview that has all of the information in there. Can someone look through it and help me out please? Thank you

That blue screen was due to me taking out my monitor's dvi cable when it was turned on and switching it. I had to uninstall all of my video drivers and reinstall them for it to work. But this problem is new. Is there seriously no way to help me unless I download that program?

JDobbsy1987 said:

Wait for a member of the BSOD team come along and see if they will assist, i suspect they will ask for you to follow the instructions.

It seems you are very security conscious which makes be believe you would therefore have an Anti-Virus you trust running, why not download the application and scan with your Anti-Virus for peace of mind before running it?

The reason why I am so security conscious is because I'm not that good with anti virus stuff and I don't want my computer breaking on me. I don't take any risks because I don't know how to fix most of this stuff. I don't even know how to scan programs with my anti virus. I just have it on always and I don't download things that I'm not familiar with. Those are my only defenses against stuff. I was Googling and some people said it could be due to a bad hard drive. My SSD did report that the volume was dirty and the last time it BSODed it didn't even go to a blue screen. It just restarted just like now. But this time when I type chkntfs in CMD it says it's not dirty. My SSD has a 5 year warranty and I got it in 2012.

Here's the dilemma, you are asking for help and providing the most basic of information. (A text file)

To properly analyze crashes we need the info that tool provides, all it does is gather the actual dump files and other logs and info necessary to give you the help you are seeking.

We are the top forum for windows 7 support, we do not cause harm to computers we fix them and we're damn good at it.

Any forum with any kind of reputation will be asking you for the same info we are asking for.

If you would instead like to have help based on what info you gave,

Your upload:

Code:

==================================================
Dump File         : 080214-10062-01.dmp
Crash Time        : 8/2/2014 5:59:48 PM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : 00000000`00000020
Parameter 2       : ffffffff`c000009d
Parameter 3       : fffffa80`08395078
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\080214-10062-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 296,497
Dump File Time    : 8/2/2014 6:00:36 PM
==================================================

The line in red above is the only thing useful you posted, the common but not limited to reasons for a Bugcheck 7A crash are the following,

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

You are basically asking us to guess which one of those it is and suggest a fix.

That's not how it's done, you give us info to analyze so we can narrow it down and give specific detailed instructions.

ok here's the zip file.

That was painless wasn't it. :)

Code:

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


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

I think you should check your cables to make sure they are good and connected securely.

Then check them again, the c000009d is usually a reference to defective cables, loose connections or the disk controller doesn't see the disk. (The emphasis should be on the cables or connections)

I also suggest you check all your drives,

I see two SSD's and two HDD's installed, A Crucial SSD, An OCZ SSD, A Seagate 1TB HDD and a Western Digital 2TB HDD, is that all the drives you have?

Please perform the following tests,

chkdsk /r

About your comment,

thready said:

The reason why I am so security conscious is because I'm not that good with anti virus stuff and I don't want my computer breaking on me.

You really should learn more about your antivirus, it is just a tool but a useless tool if you don't know how to use it,

I understand not wanting to "break your computer" but your computer is also a tool so learning how to use it is part of the journey.

Let us know the results of those cable checks and the chkdsk /r.

Here is DUMP file in BSOD help me.
Every day once I have BSOD screen....



==================================================
Dump File : 091114-11138-01.dmp
Crash Time : 11.9.2014. 23:46:12
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050033
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff800`02ee2da3
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091114-11138-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292.288
Dump File Time : 11.9.2014. 23:46:48
==================================================