BSOD caused by driver (ntoskrnl.exe) /adress (ntoskrnl.exe+72a40)

[winkawak]

Got my first blue screen of death tonight, had 2 firefox opened one watching youtube video another browsing internet. After bsod it restarted i login but just black screen with cursor, ctrl alt delete worked so i shut my computer down. Boot up normally after, check my minidump file, bsod cause by ntoskrnl.exe. Did little search on google find has to do with ram and hard drive.

Downloaded wd data life guard diagnostic for my mechanic drive which is healthy but my ssd on shows failed end to end error rate(value/threshold/worst is all 0) in SMART statue. Im not sure if i can trust this wd diagnostic on my crucial ssd, there are alot of unknown in SMART statue too. Theres no ssd diagnotic for crucial, there is a firmware not sure if it helps. So i downloaded and ran crystaldiskinfo on my ssd, health statues says good, it doesnt say end to end error rate like wd. Instead same ID B4 line says "unused reserve nand blocks" instead. Is my ssd good? i havent ran a test on my ram yet.
This is almost 3 month old build
Asrock x99x killer
i7 5820k
gtx 970
850w
crucial 2x4gb
crucial 256gb ssd
wd blue 1tb

Heres info of bsod with bluescreenview
Bug Check String- IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug Check Code - 0x0000004a
Parameter 1- 00000000`7709dc4a
Parameter 2- 00000000`00000002
Parameter 3- 00000000`00000000
Parameter 4- fffff880`08167b60
Caused By Driver- ntoskrnl.exe
Caused By Address- ntoskrnl.exe+72a40
File Description- NT Kernel & System

 

[Boozad]

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[winkawak]

Sry, here it is.

 

[winkawak]

bump, plz help

 

[Boozad]

Right, firstly you can't be bothered to read the instructions emblazoned across the top of the forum to post your issue correctly. Secondly, I had been at work for four hours when you posted your dumps so obviously I couldn't look at them, I still hadn't finished work when you bumped your thread.
There are plenty of people needing help who have the patience to wait for the free help offered here. If you don't have the patience to wait then I won't have the patience to help you.

With that said, there are no dump files in your logs to analyse.

1. Open Advanced System Settings
2. Click on Settings in Startup & Recovery
3. Make sure both boxes indicated below are checked
4. In the dropdown box ensure you're set to record Small Memory Dumps

 

[winkawak]

Sry, here it is.

==================================================
Dump File : 042215-9297-01.dmp
Crash Time : 4/22/2015 2:43:36 AM
Bug Check String : IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug Check Code : 0x0000004a
Parameter 1 : 00000000`7709dc4a
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`08167b60
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72a40
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+72a40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Users\Jiakai\Desktop\042215-9297-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 7601
Dump File Size : 358,568
Dump File Time : 4/22/2015 2:44:14 AM
==================================================

I also attached the dump file .log since it wont let me upload in .dmp. You have to change it to .dmp.

 

[Boozad]

What am I meant do with that?

 

[winkawak]

Im new to this, you say you wanted the dump file i attached it the post above.

 

[Boozad]

That's not a dump file. I've shown you in post #5 how to set your computer up to record dump files. When you get a new BSOD, run the DM Log Collector Tool as explained in Blue Screen of Death (BSOD) Posting Instructions and upload the new logs.

 

[winkawak]

That's not a dump file. I've shown you in post #5 how to set your computer up to record dump files. When you get a new BSOD, run the DM Log Collector Tool as explained Blue Screen of Death (BSOD) Posting Instructions and upload the new logs.

So attached file in post #7 is not dump? I changed it to .log so i can upload but you have to change it to.dmp when you download it. I havent had a new bsod yet, is the logs and dmp file not enough?

 

[Boozad]

What you've put in post #7 is a bunch of text and a log file that I'm apparently supposed to magic into a dump file. If what you had posted was sufficient I wouldn't be asking you to do it again. I've given you detailed instructions on what to do, please follow them.

 

[winkawak]

What you've put in post #7 is a bunch of text and a log file that I'm apparently supposed to magic into a dump file. If what you had posted was sufficient I wouldn't be asking you to do it again. I've given you detailed instructions on what to do, please follow them.

That attached file it is dmp file, uploading does not support dmp file so i changed it to .log but you can change it back to .dmp just change the extension. Im sorry youre very rude from the begining to the end, for someone whos helping out others you also have no patience. Im new to this and I have try provide all the info that i got from bsod, instead of explaining things to me you decide to talk down on me every step through the way.

 

[Boozad]

I've told you exactly what to do and you've ignored it. I'm done.

 

[essenbe]

Run the BSOD Posting instructions. http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html. It will create a Zip folder on your Desktop. Don't open it, just upload it with your next post.

Also, open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[winkawak]

I've told you exactly what to do and you've ignored it. I'm done.

How and when did i ignored you ? Im done with you.

Run the BSOD Posting instructions. http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html. It will create a Zip folder on your Desktop. Don't open it, just upload it with your next post.

Also, open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scan now. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Will report back shortly tonight or tomorrow, need to use my computer to study tonight.

 

[essenbe]

The dump file lists

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 000000007709dc4a, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff88008167b60, 0
Debugging Details:
------------------
[COLOR=red]PROCESS_NAME:  vsserv.exe
[/COLOR]

That is your Bit Defender Anti Virus.

 

[winkawak]

The dump file lists

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 000000007709dc4a, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff88008167b60, 0
Debugging Details:
------------------
[COLOR=red]PROCESS_NAME:  vsserv.exe
[/COLOR]

That is your Bit Defender Anti Virus.

My bsod is caused by my anti virus?
i thought ntoskrnl.exe was ram or hdd related?

 

[essenbe]

A BSOD is never caused by ntoskrnl unless it has been corrupted or altered. ntoskrnl.exe is the Kernel of the Windows operating system.

 

[winkawak]

A BSOD is never caused by ntoskrnl unless it has been corrupted or altered. ntoskrnl.exe is the Kernel of the Windows operating system.

What can i do to prevent bitdefender from bsod my pc again?
why does bsod report say ntoskrnl.exe driver?
btw can you teach how you find the culprit of bsod?

 

[essenbe]

Upload the BSOD Posting instructions. http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

You can't debug with Blue Screen View. It can't do it. You need to have the right software and a lot of knowledge of Hardware, Operating systems, Drivers, software and how they all interact with each other.

This was for first BSOD. Just wait and see if you get any more is what I would do.