Random BSOD's

[Chileinbox]

Hi guys, first, I'm sorry if my english is not that good, but I'll work around.

Well, I was having some random BSOD's, after a lot of trials e error, i was able to reduce the quantity of BSOD's to just one. The classical:

SYSTEM_SERVICE_EXCEPTION

and the driver that seems to be causing the problem are:

ntoskrnl.exe

This BSOD occurs really randomly, it's not particularly when I'm gaming, or when I'm doing simple stuff, it simply happens.

Cn you guys gimme a hand? I've seen lots of cases solved in this forum, you guys are really my last hope, and Brazilians Forums are not that well organized.

Thanks to all!

OBS: also, no matter what I do, i've already tried severals Hard drives, but at some point of use they click a bit, and then the click disappears, and randomly comes back.

For example, this HD is already 3 weeks withou clicking, but it might click tomorrow, or tonight, who knows?

 

[essenbe]

Chileinbox, I will see if I can help. I just need a couple of things. Please fill out your system specs as detailed as possible. Sometimes we need to look up a part, so manufacturer and model Number will help a lot, and please put them in your system specs at the bottom left of your last post and be sure to click save at the bottom of the page. Please add things like the PSU, Case and CPU cooler as well as anything kept attached to the machine. These are the instructions I usually give. I know you have filled out a lot of them, but I thought it may help you some.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

Aslo please run http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html use option 2 and click the Grab All button and give it a little time.

Open a 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.

 

[Chileinbox]

Spoiler

Chileinbox, I will see if I can help. I just need a couple of things. Please fill out your system specs as detailed as possible. Sometimes we need to look up a part, so manufacturer and model Number will help a lot, and please put them in your system specs at the bottom left of your last post and be sure to click save at the bottom of the page. Please add things like the PSU, Case and CPU cooler as well as anything kept attached to the machine. These are the instructions I usually give. I know you have filled out a lot of them, but I thought it may help you some.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

Aslo please run http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html use option 2 and click the Grab All button and give it a little time.

Open a 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.

Thanks for the help, man.

I took the time to fill my system specs as detailed as possible, some periferical i could not gather all the information, suck as Keyboard and mouse, i'm sorry.

I have uploaded the RAR to this thread, hope i dit it correctly.

And right now I'm doing the CMD stuff.

Edit:

No integrity violation found.

 

[essenbe]

See if the CMD gives any clue. For your info, ntoskrnl.exe is not a driver. It is the Windows Kernel, or basically the Windows core, which cannot cause a BSOD. None of your dump files are giving any information and almost all are different bug checks. As for your hard drives, I doubt anything other than your PSU over volting can cause hard drives to go bad. I'm going to ask you to run the worst, but most obvious test first. Your first BSOD was a general hardware fault, and almost all mention memory, even though that could be a driver instead of memory.

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​

 

[Chileinbox]

I said "driver", because i used Blue screen viewer, to see more clearly the dump file that was generated after the BSOD. And they name it as a driver.

About Memtest, i already ran it 2 months ago if I'm not wrong, but I surely will run it tonight, just gotta finish some college work.

 

[essenbe]

No problem, Whenever you are ready.

 

[Chileinbox]

I ran Memtest last night, 10 Hours, no errors found.