Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Daily BSODs - all F4 stop error - ntoskrnl.exe


  • Please log in to reply
5 replies to this topic

#1 CMCarlin

CMCarlin

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:02:25 AM

Posted 07 March 2014 - 12:14 PM

Hi All,

 

I have a BSOD at least once a day. Occasionally I can go a few days without one if I remember to shut down my computer at night. If I forget, I almost always wake up to a crashed computer.

 

It will also crash on my once in awhile while playing a game (I am almost always playing a game while at the computer thoough). The screen gets distorted with random colors, then crashes.

 

 

Here is my speccy: http://speccy.piriform.com/results/zIdiCau4vvaqrw27XpOf3dX

 

 

here is my bluescreenview export: https://dl.dropboxusercontent.com/u/11031481/Crash%20List.htm

 

 

 

here is a past thread where I had constant random crashes and the community here helped me resolve many of them by helping me install certain hotfixes and driver updates:

 

http://www.bleepingcomputer.com/forums/t/492680/new-pc-loving-it-except-that-it-randomly-hangs-on-sleep-or-gives-me-a-bsod/

 

 

I post that simply for reference so that one may see what I've already done.

 

 

I want to see if I can go without buying a new HDD. I will even resort to a whole new fresh install, but hopefully it won't come to that.

 

 

PLease help.

 

Sincerely,

DailyBSOD cmcarlin



BC AdBot (Login to Remove)

 


#2 zingo156

zingo156

  • BC Advisor
  • 3,345 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:25 AM

Posted 07 March 2014 - 12:17 PM

Please download and run who crashed:

 

We need to analyze your operating system's crash dump files to further diagnose what could possibly be crashing your computer system.

Please download Who Crashed? and save it to your desktop.

Double click whocrashedSetup.exe and choose Run

On Windows Vista, 7, 8 and 8.1 machines, when User Account Control asks if you wish to install this program, say YES to install the program on your computer.

Program can also be installed by right click and choosing Run As An Administrator.

On the next screen choose Next and accept the agreement.

Install the program in it's default location C:\Program Files\WhoCrashed (If your primary drive is different from C:, choose your primary drive.)

Choose Next and allow program to create a Start Menu Folder called WhoCrashed and click Next.

Allow program to create desktop icon and click Next.

Now Click Install.

Once the program is installed on your computer system, look for the WhoCrashed icon.png desktop Icon and double click it.

Accept the User Account Control request and the program will open on your screen and should look something like this.

whocrashed.png

Next, Click the Analyze button. analyze.png

An Information Window should appear on your screen prompting you to scroll down your screen.

If a report was generated we would like to have a look at this report.

To do this, click File analyze.png and then choose Export.

Save as WhoCrashedOutput.htm to your desktop.

Open WhoCrashedOutput.htm and copy and paste all of the contents from System Information (local) and Crash Dump Analysis and the Conclusion into your next reply.
 


If I am helping you with a problem and I have not responded within 48 hours please send me a PM.

#3 CMCarlin

CMCarlin
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:02:25 AM

Posted 07 March 2014 - 02:18 PM

thanks! here is the report

 

https://dl.dropboxusercontent.com/u/11031481/WhoCrashedOutput.htm



#4 zingo156

zingo156

  • BC Advisor
  • 3,345 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:25 AM

Posted 07 March 2014 - 03:05 PM

That is a fairly non specific error you can read about it here: http://msdn.microsoft.com/en-us/library/windows/hardware/ff560372%28v=vs.85%29.aspx

 

My first recommendation would be to remove any over clocks if you have them on any device, cpu, ram, video card, etc.

 

The next thing I would recommend is running memtest86 if you have not already done so: this is a flash drive self installer version (Backup flash drive before using it will format the drive) Download - Auto-installer for USB Key (Win 9x/2k/xp/7)

Here is a burnable version for disc: Download - Pre-Compiled Bootable ISO (.zip) do not extract, just burn to a disc.

 

Run at least 2 passes and let me know if there are any errors and record the numbers written in the error line.

 

If there are no errors, I would like you to download and run prime 95 and see if you have any crashes you can get that here: http://files.extremeoverclocking.com/file.php?f=205 let it run for around 20-30 minutes.

 

If prime 95 passes lets try to stress your video card and record the temperature while doing so by running furmark: http://www.ozone3d.net/benchmarks/fur/ run this test for around 15-20 minutes and report your maximum temperature here.

 

You may also have a power related issue, if both prime 95 and furmark pass, you might try running both of them at the same time to put a greater load on the psu, a failing psu will likely cause more crashes under a larger load.

 

I also noticed you have an ocz vertex ssd, I have seen many of these drives with problems... Is the ocz the current OS hard drive?

 

The bsod code you are getting can be tied to a failing drive. I read through your other thread, it seems the hitachi passed a diagnostic test?

If the hitachi passed a hard drive test and it is not currently the os disk, you might want to consider creating a small 50gb partition on that drive and install windows on it and then see if it solves your crashes.


If I am helping you with a problem and I have not responded within 48 hours please send me a PM.

#5 CMCarlin

CMCarlin
  • Topic Starter

  • Members
  • 38 posts
  • OFFLINE
  •  
  • Local time:02:25 AM

Posted 05 May 2014 - 12:04 PM

update:

 

my games started to hang quite a bit while loading and playing them. I had them installed on my 2nd (non-ssd) drive, but something told me it was still my SSD that was failing.

 

So I bought a regular 1tb hdd and installed windows, removing my ssd. I can put up with the slower boot times because I've had zero problems since then.

 

I even installed some games back onto the 2nd HDD and all is well, which tells me that it was, in fact, my SSD that was starting to fail (after a couple of crashes the system had to do a check disk because there were some problems. this was another symptom which told me it was my SSD).

 

so anyway, I am very happy with my new HDD. I partitioned it out. I am able to back  up my important data. All is well.



#6 zingo156

zingo156

  • BC Advisor
  • 3,345 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:25 AM

Posted 05 May 2014 - 12:37 PM

Glad to hear. It sounds like that vertex drive may have some bad blocks or in/out problems of some sort. You can run hard drive tests on some ssd's I have never tried it on a vertex drive since most of those drives I saw had completely failed.

 

I have run mhdd on my very old SSD which is an intel 32gb SLC drive. When I had BSOD related to the drive, I found 2 bad blocks that I was able to remap and disable using MHDD. The ssd has been fine since, it is a media center drive and quite a bit of caching is done to the drive.

 

It might be worth running MHDD on the drive (unless you inted to rma the drive then don't waste the time). I am posting instructions below. I would recommend disconnecting the other drives and flash drives when running this test so you are 100% certain you are running the test on the ssd. The instructions are long and require you to change the sata operation in bios to IDE, compatibility, or ATA. Also I am not 100% if the test will work on your vertex drive but I assume if it appears in the list in MHDD you could run the test on it and possibly remap bad blocks or erase delayed sectors. IF YOU CHOOSE TO ERASE DELAYS: backup all data on the drive first (before enabling erase delays). You might want to read the whole post including advanced user features before running the test if you intend to remap etc.

 

Instructions for MHDD:

 

If a hard drive has a smart status warning or the drive is questionable this test may be of use NOTE this test does not work with AHCI or Raid sata operation. It must be done with IDE, ATA, or compatibility mode:

 

Before running this test it would be a good idea to backup any data that you cannot afford to lose. This test uses the hard drive at 100%. If the drive is failing or has problems it is possible for the drive to fail suddenly especially during heavy use as this test will do. It is unlikely but still I recommend backing files up to be safe. Here are the instructions to run the test:

 

The first step will be to burn MHDD to a disc as an image (cd preferably). MHDD Can be found here: http://hddguru.com/software/2005.10.02-MHDD/  Click the Last version of MHDD, CDROM iso-image download and burn this file directly to a disc.

 

TO CHANGE SATA OPERATION: (You may need to use your keyboard arrow keys and enter key if you can not click to change settings).

After burning the disc, restart the laptop and start tapping f2 or f1 or delete right away to get into the bios. There you should see System Configuration, expand that by clicking the + button (or using your arrow keys and enter key). In that list there should be something called Sata operation. (Sata Operation may also be by itself in that first screen list)

Click on sata operation and take note of the current setting to the right it will probably be set to AHCI it will need to be switched back to this after MHDD is done running. Select ATA, compatibility or ide mode and then click apply. Save and exit the bios, or if apply was the only option you can use Ctrl+Alt+Delete to restart.

COMMON BOOT MENU/BIOS keys: https://support.fixmestick.com/hc/en-us/articles/201577043-How-to-get-to-your-Boot-Menu-or-your-BIOS-settings

 

Now with the burned disc in the drive after a restart, start tapping (F12 Dell, Toshiba, Lenovo), (F9 HP), or (Esc HP, Samsung, Sony) on the keyboard (or change your boot options to boot to cd/dvd first). This will bring up the boot options menu. Select cd/dvd/cd-rw drive and hit enter.

If this worked correctly and booted to mhdd you should see a screen that says Microsoft windows 98 startup menu. You can let the timer run out or just hit enter on option (2 . Start computer without SCSI support).

 

Now you should see a screen with numbers, most of these will not have any device listed behind them but one number should for example on my dell computer number 6 has WDC WD1600BEVT-75A23T0… and at the end a number in white which is the size of the drive.

Example: If your drive is a 500gb I would expect that number in white to be somewhere around 500,107,862,016 or close to. Find the correct drive to test then on the keyboard type the number in front of the drive (in my case it was 6) and then hit enter.

 

Now you should have a screen with MHDD> and a blinking cursor.

Now hit F4 on the keyboard 2 times and this will start scanning the hard drive.

You should be able to see the computer start scanning, each block represents 255 sectors (130560 bytes) on the hard drive. What we are looking for will show up on the right side of the screen.

There is a list on the right which shows numbers:

<3

<10

<50

<150ms

Etc…

 

Anything below the <150ms is a slow sector or a problem sector. Slow sectors <500 or >500 will slow down the computer. If there are a lot of these one after another (several 1000 or more) the drive should probably be replaced. Also if you have any at the end that were marked as UNC this means the drive has uncorrectable errors and the hard drive should probably be replaced.

Basically if you have any sectors that are below <150 (green) let me know and if possible the total number of them.

 

If all of the sectors were ok and fell within the range of:

<3

<10

<50

<150ms

Then the hard drive is ok, if there are only a few that are slow <500 or >500 the hard drive should be ok to use.

 

NOTE: that if there are many slow sectors one after another or you start having error after error the drive is in bad shape and I recommend ending the test. To end the test hit the Esc key.

 

After you are done testing you will need to go back into the bios by restarting the computer and tapping F2, F1, Delete (or whatever key gets you into bios). Go back to Sata Operation and change it back to the default which probably was AHCI.

Then restart and the computer should boot again.

(If you are getting a blue screen and the computer restarts go back into the bios and confirm that Sata Operation is set to what it was before changing it to IDE, ATA, or compatibility).

 

ADVANCED USERS: (USE AT YOUR OWN RISK)

There are options for fixing drives: erase delays and re-map bad blocks, enabling re-map is ok to do for most drives, no data should be lost. DO NOT erase delays if you have not backed up all of your data! These options are available from the F4 menu (only pushing F4 one time from the MHDD> blinking cursor screen.) Use your arrow keys to move up and down to highlight the option and hit enter to open and change the setting. Another useful key to hit at the MHDD blinking cursor screen is F8, this will bring up a drives S.M.A.R.T information.

 

What re-map does: This option if enabled moves available data from a bad block to a good block and disables the bad block by telling the controller to add it to a black list (list of blocks that the drive will not write to). This is a good option for drives that have available free space that have many bad blocks that can cause many problems including: BSOD bug check 0X7A etc. During a scan with re-map enabled a BLUE block after a bad block indicates succesful re-map.

 

What erase delays does: This option if enabled will erase blocks (and add them to the black list) that are slower than <500ms, if you have a lot of slow sectors greater than 20% of the total blocks, this is not recommended. If you erase delays on an OS drive or drive with any data, your OS may no longer load, your data may become corrupted. I only recommend this option on a drive that you intend to format and then re-use. Erasing delays can speed up a drive. The logic: 500ms = half a second. Each time windows tries to write or read from that block it takes half a second. Having a file written in 1000 slow blocks at 500ms (each block) would cause that file to take 8.7 minutes to read. 1000 blocks = 124.5 Megabytes. During a scan with erase delays enabled a white W indicates an erased slow sector. Slow sectors >500ms can significantly slow down write/reads depending on the actual read/write time for the block.

 

Frequently asked questions MHDD> http://forum.hddguru.com/viewtopic.php?t=5


If I am helping you with a problem and I have not responded within 48 hours please send me a PM.




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users