Solved BSOD when watching youtube videos, error 0x000000d1

[kory360]

For about a few weeks ive been getting BSOD sometimes i get them a couple times a day and sometimes a can go several days without one but they always happen when im watching youtube videos or playing games. To be honest im not very good with this kind of stuff so I'm sorry if I'm leaving something out or missing something really obvious. Any help would really be greatly Appreciated.

View attachment 291867

 

[kory360]

Also I forgot to mention that sometimes after BSOD when my comp reboots there is no video or sound, my moniter doent even pick it up it goes straight to sleep like when there is nothing hooked up to it. Because of that i assumed it was a problem with my graphics card but I switched it with my old graphics card but it didnt solve anything. also not just youtube videos and videos cause it especially when on fullscreen.

 

[YoYo155]

Hello and welcome to SF .
The single dump uploaded is corrupted, unfortunately.
Most of the files are missing,

Please run the SFDT again and let it run its course it can take 15min at times to collect all the data necessary.
There should be eight files generated not including the dumps.

 

[kory360]

sorry about that hopefully i did it right this time.

View attachment 291878

 

[YoYo155]

Thanks .
Unfortunately no dumps other than the corrupt one.
Check in the minidump folder for any more files.

C:\Windows\minidump

 

[kory360]

There is only one file in my minidump, does that mean I have to wait for another BSOD and hope the minidump it creates isnt corrupted this time?

 

[YoYo155]

Yes, in the mean time make sure you have all of the prerequisites to generate a dump file.

• http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[kory360]

It is currently set up for Kernel memory dump should I change it to small memory dump?

 

[kory360]

also is there anything I can do to make sure the minidump isnt corrupted?

 

[YoYo155]

It is currently set up for Kernel memory dump should I change it to small memory dump?

Yes for now.

also is there anything I can do to make sure the minidump isnt corrupted?

No, not really.

 

[kory360]

I just checked the date on the dump file and it says its from like almost 2 months ago but ive had alot of BSOD sence then, will it not make a new file intell i delete the one already in there or something? I figured it would just make a new one for every crash.

 

[YoYo155]

It shouldn't be this way it should as you said generate a new one each crash, go through this check-list of prerequisites to be able to generate a dump file.

• BSODs but no Dump Files?
  

It might help if you free up some space in the C: partition.

 

[kory360]

Ok it;s been awhile but i somehow managed to get a new minidump(everytime i got a crash I didnt get one for some reason). Also some more info that may or may not be relevant, I seem to be getting only crashes now not BSOD, I dot really get crashes intell the evening never in the morning or afternoon, And my programs usually close like 5-10 seconds before a crash like ill get a message that my browser or skype have crashed and then boom whole comp crashes. For the record ive already run the memory diagnostic tool.

View attachment 293365

 

[YoYo155]

OK it's something but not much of it .

Enough to look at the arguments for this type of bugcheck and see that it is usually a driver fault.

BugCheck 1A, {[COLOR=DarkOrange][U]41790[/U][/COLOR], fffffa8003ff9300, [COLOR=Blue][U]ffff[/U][/COLOR], 0}

For those interested, this link summaries this topic perfectly.

• BSODTutorials: Debugging Stop 0x1A - MEMORY_MANAGEMENT

Our best bet at the moment is following the steps detailed in the quote below.

Your crash dumps are not showing any finite probable cause.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

If memtest comes free from errors, 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.

Post back with the results .

 

[kory360]

Ok so I ran the test and it appears that the problem was one of my sticks of ram so i removed it (I still have plenty). It's been about a week and i havent had a crash so i think the problem is solved, I'll spend the weekend trying to do the stuff that usually caused a crash just to make sure the problem is solved. If I go the weekend with no problems I'll go ahead and mark this as solved. Thank you YoYo155 I really appreciate all the help and support you gave me and now I know some things I should try if this ever happens again .

 

[YoYo155]

Thanks for the good news update .
Happy I could help.