Random BSOD times, errors: 0x0000001a and 0x0000004e

[NO37]

Dear forumers,

I would like to enlist your kind assistance in arresting my BSOD issue.
I have gotten this problem since I have bought my system back in 2011 but due to my problem I have stashed it away for 3 years. Now I have dusted my desktop off and started using it again, the BSOD is hampering my work.

What I have done:
1) Clean install of Windows 7 Ultimate x64
2) Updated my motherboard BIOS
3) Updated my Windows 7 to Service Pack 1 with all the latest updates including Defender updates.
4) Downloaded the latest drivers for all of my peripherals.
5) Ran MemTest86+ overnight with 18 total passes without errors.

So I would like to know if you could be kind to point out how to solve this BSOD once and for all. Attached is the zip file as per the SevenForum guide's instructions.

All help is welcome and appreciated!

 

[Arc]

Product ID:                00426-OEM-8992662-00006 ==> [COLOR=Red]HP OEM[/COLOR]
Original Install Date:     03-Feb-15, 2:27:26 PM
System Boot Time:          28-Mar-15, 12:44:38 PM
System Manufacturer:       Gigabyte Technology Co., Ltd. 
System Model:              H67MA-USB3-B3 ==> [COLOR=Red]Gigabyte retail motherboard[/COLOR]

HP OEM licensing on Gigabyte retail motherboard is only possible when the installation is counterfeit. And a counterfeit installation is subject to all sort of issues.

Get genuine windows, have a trouble free computer.

 

[NO37]

Hi Arc!

Thank you for your reply, after 3 days I assumed I was never going to get help.

Allow me to explain: I have my own copy of Windows 7 Professional and due to the BSOD occurrence I decided to try different copies of Windows 7 just to see if there was any difference. Yes, multiple copies of which a couple were from my friends as well - I did not rectify if any of those were genuine though.

On to the matter: After re-installing my personal Windows 7 Professional and while I was mid-way through installing NVidia GeForce driver, it hit another BSOD again. I appreciate your assistance to look through the attached file and try to see if there is a solution to my problem.

Thanks in advance!

 

[Arc]

Though there is no crash dump in the zip, but what you stated is very meaningful.

After re-installing my personal Windows 7 Professional and while I was mid-way through installing NVidia GeForce driver, it hit another BSOD again.

If it happens this way, that (apparently) means the graphics card is failing to take the driver. As your motherboard has the option of decent onboard graphics, use it for the time being. And apply the graphics card to any other computer (you have some good friends, they will let you do this I think). See how it goes there. Also Stress test the Graphics Card using Furmark on that computer, if the card does not cause any prima facie issue there.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

And let us know how your computer runs with onboard graphics.

Some more steps and tests will be needed depending on the resulting situation.

 

[NO37]

Hi Arc,

1) Please allow me more time to complete my Windows 7 to the latest updates. I have noticed that the Microsoft NET Framework has encountered numerous "Failed" updates, and I am attempting multiple times till it is fully updated.

2) I am very surprised the "Minidump" folder is no longer found within C:\Windows. ? I'm very sure that is the cause of the empty crash dump. Please advise.

3) While I am trying to follow your guide to the best I can, I am bypassing the method of removing my graphic card. Instead, I have enabled onboard graphics in order to run the Furmark stress tests. (Current output is now via motherboard DVI) If this method is not acceptable as troubleshooting, I will remove my graphic card as advised.

4) After that I will also run the same Furmark stress test on my ASUS GTX with onboard graphics disabled in order to eliminate all possibilities so we may be able to better conquer this issue. Once I get this done I will update this post.

NOTE: On my second attempt I have successfully installed NVidia's GeForce Experience and NVidia's driver that comes with it.

 

[Arc]

1. Get dotnet from any other reliable source. Download .NET Framework Version 4.5.2 - FileHippo.com
It is very often failure.

2. Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

3. No need to run stress test on the onboard graphics. It is a motherboard component, and its failure means lot more. Hopefully that is not the case for you.

4. Let us know the stress test results on the graphics card, if and when you can.

 

[NO37]

Hi Arc,

So far everything is good running with onboard graphics. All Windows update has been performed with no more new updates available, MSE is at its latest. I have done the merge for regedit as instructed for the BSOD crash dump. Also, no artifacts or errors were found on both onboard and graphic card stress tests and I have attached the results for your viewing. Till now the BSOD has not returned yet. I have switched back to using my graphic card as output to monitor.

I am beginning to suspect it could still be a hardware issue because my RAM, motherboard and graphic card is fine so far... The last BSOD I noted (that did not have the crash dump file record) was still a memory management "1A" fault code. This is frustrating...

I will continue to use my computer first and see if more BSOD comes up and will upload the dump file.

 

[Arc]

Well, everything seems to be good at this point.

It is not only the physical RAM but also any failing driver that may cause stop 0x1A BSODs. So if the computer BSODs again, let us check the files. Though I will expect that it will run free from any more errors.

 

[NO37]

Thank you for your patience in helping me out. I shall continue to use the computer first, and if the BSOD happens I will call out for assistance again. Hopefully all will be well from here onwards.

If in the next 2 weeks there are no more BSOD I will proceed with marking this thread as solved.

Thanks Arc!

 

[Arc]

Welcome, and all the best.

 

[NO37]

Hi Arc,

Just hit another BSOD.
Please have a look and see if you could help me out on this?

 

[Arc]

I know that you ran MemTest86+ overnight with 18 total passes without errors (from your original post) ... so searching for any possible driver corruption which may be passing any bad info to the memory.

Enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[NO37]

Hello Arc,

Following your advise I ran DV for a full week with normal use without BSOD. It was slightly laggy during load times but no serious impact on my usage.
But when I disabled DV, the BSOD emerged. It somehow never BSOD in DV mode.

I'm totally at a lost on how to solve my problem. Just minutes ago while running Borderlands 2 for some fun, the BSOD hit me again with "Memory Management".

Crash dump as attached. Please help...

 

[Arc]

Bit of strange to me, too.

Anyway, the crash dump loosely blames the video memory.

BugCheck 1A, {403, fffff680002ca4b0, d08000000ffaf86f, fffff680002b166a}

Probably caused by : dxgmms1.sys ( dxgmms1![COLOR=Red]VIDMM_PROCESS[/COLOR]_HEAP::Free+a2 )

Followup: MachineOwner
---------

Your motherboard supports Intel HD graphics. Can you remove the graphics card and apply the onboard graphics, at least as a test?

 

[NO37]

I will need to find a time when I have offloaded all my work and remove the card for the test...
Thank you and will update again soon.

 

[Arc]

No problem ... take the necessary time.