Windows 10: Multiple daily BSOD since Upgrade to Win10

Please update the WD SCSI Architecture Model WDM driver, the driver from 2008 is known to cause trouble.
You may find drivers here

 

It looks like something is causing a deadlock, but it is yet unknown what exactly.

 

flibbittygibbit, please make it sure that fast startup is disabled. Let us see this screenshot with this button unchecked .....

Attachment 36100
We can proceed any further only after making the above sure. Otherwise the efforts will go goalless.

 

See if this will help with what Arc suggested

[youtube]hmDmaKLbi4Y[/youtube]

 

Hi, I saw no WD driver from 2008 in the device manager or one with that name, but I did jsut download and update the WD SES Device driver from their site, although I don't think it actually updated from the one that was already installed. Any other ideas?

 

I believe that turning off hibernation as I previously reported I had done also disables fast startup. Any other ideas?

 

Well, I have hibernate turned off .....

Attachment 36146
But fast startup enabled.

Attachment 36147
So I cannot comment on what you have done there.

You are having two different BSODs, 0xDE and 0x133. The fast startup thing is having some bearing on that stop 0x133, so you understand why I am suggesting it. And, before minimizing the 0x133 BSOD, it will be hard to say whether the stop 0xDE is an independent one or not.

 

Not sure what to say. All i read was that if you disable hibernation, fast start is disabled too. maybe it is different if you disable via cmd like I did, but no trace of hibernation anywhere or fast start.

Also, after 7 new BSOD in an hour, I started digging some more to try to get DISM to work. I finally found a resource, on this forum actually, (DISM - Repair Windows 10 Image - Windows 10 Forums) to mount the iso and select the source using:

Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /limitaccess

with the red as your mounted image install.wim full path

I was successful at that, and it made corrections, the next SFC scan also made corrections successfully this time. subsequent 2x SFC scan said no errors, so maybe this is resolved???...only time will tell.

I'd appreciate any more input you or anyone else might have in regards to the review of the DMP file error reports as to what was actually causing this, but I have my fingers crossed that this is now resolved - after 7 BSOD in a hour, now nothing for an hour and counting since the repair was successful. If any more goofiness occurs, I'll be sure to report it here. Thanks to everyone that contributed!
Jason

 

And just when I thought this was done, and I could do something productive, another BSOD. This time another 0xDE. Any other ideas to try?

 

Please disable fast boot, use the tool again and upload the zip file.

 

The 0xDE is mainly a memory related issue. It is either the RAM is failing or any driver is passing bad info to the memory.
Code: POOL_CORRUPTION_IN_FILE_AREA (de) A driver corrupted pool memory used for holding pages destined for disk. This was discovered by the memory manager when dereferencing the file.[/quote] The crash dumps are not showing any failing driver there, even in the deepest seh. But that is not enough to nullify the possibility of a bugging out driver.

Do two tests.

Test your RAM modules for possible errors. How to Test and Diagnose RAM Issues with Memtest86+Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Report us the result. A camera snap of the memtest86+ screen before closing the program will be good.

If it does not show any error, enable Driver Verifier to monitor the drivers. Driver Verifier - Enable and DisableRun 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.

EDIT: Can you tell me what is this device?
Code: [Memory Device (Type 17) - Length 27 - Handle 0033h] Physical Memory Array Handle 0031h Memory Error Info Handle [Not Provided] Total Width 8 bits Data Width 8 bits Size 4096KB Form Factor 01h - Other Device Set [None] Device Locator Bank Locator Memory Type 09h - FLASH Type Detail 1000h - Non-Volatile Speed 33MHz Manufacturer MXIC Serial Number Asset Tag Number Part Number 25L3205[/quote]

 

Hi Axe0,
Fast boot is disabled. I uploaded a screen shot showing this earlier. I have attached the new report.
Thanks!
Jason

The crash dumps are not showing any failing driver there, even in the deepest search. But that is not enough to nullify the possibility of a bugging out driver.

Do two tests.

Test your RAM modules for possible errors. How to Test and Diagnose RAM Issues with Memtest86+Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Report us the result. A camera snap of the memtest86+ screen before closing the program will be good.

If it does not show any error, enable Driver Verifier to monitor the drivers. Driver Verifier - Enable and DisableRun 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.[/quote]


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.

EDIT: Can you tell me what is this device?
Code: [Memory Device (Type 17) - Length 27 - Handle 0033h] Physical Memory Array Handle 0031h Memory Error Info Handle [Not Provided] Total Width 8 bits Data Width 8 bits Size 4096KB Form Factor 01h - Other Device Set [None] Device Locator Bank Locator Memory Type 09h - FLASH Type Detail 1000h - Non-Volatile Speed 33MHz Manufacturer MXIC Serial Number Asset Tag Number Part Number 25L3205[/quote] Hi Arc,
I will run the memtest. I ran the windows version previously that does 2 passes, and no issues, but I'll try this also.

Driver Verifier - this was already done and was included in the earlier dmp upload.

That part seems to be a memory chip by manufacturer MXIC. I found this on google, but have no further info on what hardware it might be associated with.

Thanks!
Jason

 

Hi,
Memtest came back with 120 errors after several partial passes. Seems like I have some bad memory and will have to replace it. Hopefully that does the trick. Thanks for everyone that helped me today! Unless you all can think of something else, I would say you've found the problem.
Thanks!
Jason

 

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

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: It is a RAM, a bad RAM.

But if you have got a result like that: It is a motherboard issue. The particular slot is bad.

If it is a bad RAM, you need to change the RAM. Take the other existing (good) RAM to the shop and get one of the exactly same specification. The best is, get a totally new RAM KIT.

If it is a bad slot, it is a motherboard issue. But changing the motherboard needs a preparation for most of us; so dont populate that slot for the time being.

 

Hi Arc,
Thanks for the tips. I thought about doing that testing, but it's triple channel memory, so if one is bad, then I'd end up buying a new kit anyhow, Also, I remembered I had some older 1GB ram chips that I swapped out on this machine years ago for 2 GB sticks to double the ram. They tested fine, and machine has been running since my last update with no further issues. I will most likely not end up testing the faulty ram, since that is so time consuming, and it's obvious it's not the board or controller now, and I can pick up a new 12GB kit for relatively cheap. Thanks for all of your help and suggestions! Thanks to Axe0 and essenbe also for contributing to solving this issue! I really appreciate everyone's time and patience, all to help a complete stranger! Take care!
Jason