Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Regular BSOD; mostly 0x01a

10 May 2012   #1

W7 Prem x64
Regular BSOD; mostly 0x01a

HI Team,

I recently finished building this PC and I'm experiencing a ton of trouble after W7 install. Any help assistance you can provide will be greatly appreciated.

Please advise if you require further information.

My System SpecsSystem Spec
10 May 2012   #2

Win 8 Release candidate 8400

These crashes were caused by memory corruption probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+

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.

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these

- Concurrency Stress Test
- DDI compliance checking

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

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)
My System SpecsSystem Spec
11 May 2012   #3

W7 Prem x64

Firstly, thank you for your super quick response! For the last 4 hours I've been running the Memtest with varying RAM configurations and have discovered (I think) that 1 stick is bad.

- I first ran the test with all 4 sticks (so 16Gb total) and it started populating errors almost immediately.
- I then ran the test for a number of passes with just 1 stick in the #1 slot with no errors
- I then ran with 2 sticks in the 1 and 2 slots with no errors
- when I added the 3rd stick however I quickly got multiple errors so I tried the 3rd stick by itself in the 1 slot and it again failed.

I guess the easiest solution is to just run with 8GB RAM for now (16GB was overkill anyway) and see if the BSOD problems persist. I can't really run 3 sticks for 12GB right? They need to be in pairs?

Thanks again for the help, I'm about to run the driver verifier I'll report back if anything odd shows up.

EDIT: After following instructions for driver verifier and restarting I received BSOD before windows loads with the following info:

Stop: 0x0d5

Is that my sound driver?
My System SpecsSystem Spec

11 May 2012   #4

W7 Prem x64

All right I might just pause until I get further advice as I'm now worried I'm making things worse...

I found another thread in this forum with this info about latest BSOD:

First time I've ever had a BSOD . Screen shows RTKVHD64.sys. So I went to safe mode. Uninstalled Realtek sound driver. Deleted RTKVHD64.sys. Rebooted and let Win 7 reinstall the sound driver.

Now that I looked at the device manager. I noticed the following. (see picture)

I uninstalled the Realtek driver and install the driver from gigabytes site for my board. Seems ok.
So I followed the same steps and uninstalled the Realtek Audio drivers, downloaded and re-installed them from my mobo's download site. Upon restart BSOD again this time with:

My System SpecsSystem Spec
11 May 2012   #5

Windows 7 Home Premium 64 Bit

gdrv.sys is your Gigabyte Easy Saver power utility software. Remove the software. It is a known cause of crashes on some systems.
My System SpecsSystem Spec
11 May 2012   #6

W7 Prem x64

Edit: Ignore if you read before edit, was an issue with being in safe mode

OK attempt #2 :)

Cheer writhziden for your help. I couldn't find a programme "Gigabyte Easy Power Saver" but with some help from Google I decided none of the the Gigabyte applications that came on the mobo CD (EasyTune, Smart 6 etc.) were crucial so I went ahead and un-installed all of them.

With Disk Verifier running I am now in W7 with no immediate BSOD so I guess I just need to use it as normal now and leave it running for at least 36 hours as zigzag instructed and see if it crashes again.

Thanks again for your help, fingers crossed this time it's sorted for good.
My System SpecsSystem Spec
12 May 2012   #7

Windows 7 Home Premium 64 Bit

You're welcome. At least you are no longer crashing on startup, so that is a step in the right direction. Glad to see you removed the Gigabyte utilities. Motherboard utilities are not really necessary and cause problems from time to time, so we often recommend not installing them after doing a fresh install of Windows. It is good to have those off your system. :)

Let us know if you get further crashes. If not, post back in a few days how the system is responding.
My System SpecsSystem Spec

 Regular BSOD; mostly 0x01a

Thread Tools

Similar help and support threads
Thread Forum
BSOD Memory_Management 0x01a usually when waking from sleep
Hi, First time poster here really help someone can help. Getting memory_management BSODs intermittently, usually when waking computer from sleep and usually several days or even weeks apart. The computer is on 24/7 except for going to sleep once each day for several hours. These BSODs have...
BSOD Help and Support
Thanks for taking the time to help me out. I recently built a new rig (see tech specs in my account) and it's been running smoothly so far. However, I keep getting recurring, yet random, BSOD's with the same error codes - MEMORY_MANAGEMENT 0x000001A. There's no fluctuation in the error codes - it's...
BSOD Help and Support
BSOD While doing anything 0x24, 0x01A.
They are pretty consistent errors. I have BSOD'd 3 times today while doing things. I am beyond frustrated. I have already tried reseating the RAM and running some tests, but nothing seems to help. I have a registry fixing program, but that didn't help either. Is there anything anyone can do to...
BSOD Help and Support
Regular BSODS - During regular use and gaming
Hi, im new here and have abit of a dilemma. I'm not much of a computer wiz so please bear with me, I've been recently getting BSODs following getting a new hard drive and a new case for my computer. The hard drive replacement and transferring of parts to the new case was done at a professional...
BSOD Help and Support
BSOD after logging in [0x01a - dump attached]
For the last week or so, my computer has been emitting a lot of problems, many of which are BSOD. I narrowed down some of the hardware, and I suspect it's either with one of the hard drives or the memory (even though I ran MemTest. It didn't finish, but there were no errors so far). In the...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:12.
Twitter Facebook Google+