Solved BSOD and Stop Errors Becoming More Frequent

[BorisTheAnimal]

I would also suggest that you run this:

Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[BStuart96]

I've updated my specs with the Hard Drive info.

I'll try the driver verifier after the Error Scan has completed.

Thanks again.

 

[BStuart96]

I can't complete a full error scan without a crash, but it got to about 750/1000GB without any errors.

I don't have any disks right now to write on a restore point. Would it be too dangerous to do the driver verifier without?

 

[BorisTheAnimal]

Well you could also put it on a different hard drive disk if you have one.

 

[axe0]

Driver verifier will only stress the drivers, but you need to get a new disk a.s.a.p. and backup your stuff from the hard drive you posted the benchmark results of in post 17

 

[BStuart96]

Backup is fine, I've got everything on the KnowHow Cloud.

Are there any similar size Hard Drives that you'd recommend?

Is that what you think is causing the BSODs or is it just something else I need to take care of?

 

[axe0]

I have seen the 0xF4 being caused a lot by failing hard drives due to problems with accessing the data (Input/Output Errors)

There are a few hard drives I can recommend that are similar to the specs of your hard drive or better, but the size is 2TB to 6TB.

 

[BStuart96]

Okay that's great thanks.

Yeah that'd be fine, I could do with a bit more space.

 

[BorisTheAnimal]

Well bigger drives are becoming more cheap, one thing that most would recommend is going for SSD with OS but if you wan't a hard drive for mainly storage a Seagate Barracuda 2tb will be okay.

And yes the most probable cause is a faulty hard drive, now that you have said that you couldn't test the drive 100% without getting a BSOD.

 

[axe0]

I found the Seagate Desktop HDD ST2000DM001 2TB, you might like it.

 

[BStuart96]

Okay that's great, thanks a lot guys. I'll get a hard drive ordered and give it a while to see if the problems are fixed, then I'll come back and mark this as solved!

 

[BStuart96]

Hey there, I received my new Hard Drive today and as I was in the middle of Downloading my data onto it, I had another crash. I got a Chrome.exe - Application error and had to shut it down. Is there anything else you think it could be?

 

[axe0]

In Chrome please try disabling hardware acceleration if it is turned on

1. In the right upper corner click on View attachment 380046
2. In the menu choose 'settings'
3. In the settings scroll down and click 'Show advanced settings'
4. Scroll all the way down to the bottom.
5. Under the part 'System' you can find 'Use hardware acceleration when available'
6. If it is checked, uncheck it

Hardware acceleration uses the hardware to execute functionality faster then with software.
I suspect this may be a problem if it is enabled.

 

[BStuart96]

Okay that's done, I'll give it some time and get back to you with some more info if there's another problem, thanks.

 

[BStuart96]

No luck, just had another BSOD now, but no minidump file was created, any other ideas?

 

[axe0]

Please search 'services.msc' and search for a service called "Windows Error Reporting Service"
Make sure the startup type is manual.

Please make sure the page file is at least the size of your physical memory
Virtual Memory Paging File - Change

 

[BStuart96]

Just had another BSOD, but a different one this time, it may have been because I changed the dump file to a Kernel dump, to see if that would create one (it didn't).

The BSOD read like this:

KERNEL_DATA_INPAGE_ERROR

Technical Information:

Stop: 0x0000007A (0xFFFFF6FC4000ADE0, 0xFFFFFFFFC000000E, 0x0000000066817860, 0xFFFFF880015BCBA0)

rdyboost.sys - Address FFFFF880015BCBA0 base at FFFFF88001590000, Datestamp 4ce7982e

 

[BStuart96]

The startup type was already manual, and I'm pretty sure the page file is big enough.

 

[axe0]

Do the crashes happen when the failing hard drive is connected?

 

[BStuart96]

No, it's the new Hard Drive. Is it possible that it's my SSD Drive?