Windows 10: New tablet, new BSODs (-:

How could it be different? Freshly installed Windows 10, and tablet has random BSODs during connected standby. Hope someone can help, thanks a lot already.

:)

 

BSOD on new tablet

You could of course try a different SD.

But at first you should simply remove the card, to see if the crashes stop.

 

BSOD on new tablet

seems like something is blocking the sdbus.

So what do you have in your SD card reader?

Can you remove the card?

031717-24140-01.dmp was a

DRIVER_POWER_STATE_FAILURE (9f)

A driver has failed to complete a power IRP within a specific time.

Arguments:

Arg1: 00000003, A device object has been blocking an Irp for too long a time

Arg2: 8be98bb0, Physical Device Object of the stack

Arg3: 84bfeb20, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: 96607608, The blocked IRP

FAILURE_BUCKET_ID: 0x9F_3_sdbus_DEV_80860F14_IMAGE_ACPI.sys

!devstack 8be98bb0

!DevObj !DrvObj !DevExt ObjectName

919f7028 \Driver\sdbus 919f70e0 InfoMask field not found for _OBJECT_HEADER at 919f7010

> 8be98bb0 \Driver\ACPI 8be15da0 Cannot read info offset from nt!ObpInfoMaskToOffset

1: kd> !irp 96607608

Irp is active with 5 stacks 3 is current (= 0x966076c0)

No Mdl: No System Buffer: Thread 00000000: Irp stack trace.

cmd flg cl Device File Completion-Context

[N/A(0), N/A(0)]

0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000

[N/A(0), N/A(0)]

0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000

>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]

0 e1 8be98bb0 00000000 86c94122-919f7028 Success Error Cancel pending

\Driver\ACPI sdbus!SdbusFdoDevicePowerUpIrpCompletion

Args: 00000000 00000001 00000001 00000000

 

Hi muffle,

It is a problem with the wifi driver, check if there are driver updates available.
Code: 0: kd> lmvm rtwlans Browse full module list start end module name fffff800`a27e0000 fffff800`a2cc6000 rtwlans T (no symbols) Loaded symbol image file: rtwlans.sys Image path: \SystemRoot\System32\drivers\rtwlans.sys Image name: rtwlans.sys Browse all global symbols functions data Timestamp: Thu Jan 14 09:36:13 2016 (56975DFD) CheckSum: 004D3CCD ImageSize: 004E6000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

[/quote] Hey axe0! thank you again so much for the fast and accurate help A few questions:

Are both dump files from the same event, triggered by rtwlans.sys ?

Do you have any tips how I could solve this, without a driver update? Because I don't think there is an update to the driver, unfortunately. I read somewhere before, that the Realtek chip has a bug or problems with energy management and there is a fix, through mostly for bad wifi bandwidth to set a value in registry bLeisurePs from 2 to 0. Could this maybe fix the bluescreen too?

Also, in Windows 10, there is an optin to turn off Wifi while in connected standby, and turn it on again when the tablet wakes up, could this help too, or could it make things worse, because the moment the driver unloads/loads triggering the bluescreen maybe with high chance?

 

The other doesn't show much more than a bit of memory corruption.

I don't know, I usually don't deal with Realtek wifi driver issues on tablets.

You could try it.

 

Memory corruption? So the RAM is damaged? Which could have triggered the wifi bluescreen too?

 

Memory corruption does not mean RAM damaged.

Memory corruption has a wide range of causes, because the mechanism of the memory is very complicated.
Memory corruption has generally speaking the following causes

• Drivers
• RAM,
• Hard drive
• GPU

If one would go more in-depth in the analysis you could state that pretty much everything in a system could cause memory corruption for various reasons, the CPU, cabling, PSU, motherboard, etc.
Fortunately it often doesn't get that far, because in many cases we can find out what possibly could've caused the corruption what would lead back to the list above.
If it does go that far you could talk about unknown hardware failure, because it is difficult to diagnose.

 

I've deactivated the wifi driver to test if that helps, but still get bluescreens mostly already a minute or so after tablet enters standby mode. Would be nice if you could look another time on those crahes or the last one at least. I also did a 6 hours memtes86 test without any errors.

 

The last one I showed, caused by the network driver....

Run the DM Log Collector again and upload a new zip, the current upload is nothing anymore when new crashes occur.

 

Erm, I did that the moment I posted that. Look first post, there are 2 files.

 

Please upload in your new post instead of in the OP, prevents mistakes like I made *Smile

Either of the new is caused by the wifi driver, though all/most of them are caused by memory corruption looking at the overview.
Various of crashes, only a few blame the wifi driver, some have different stacks, good indications towards a possible faulty memory.
If it is possible, run MemTest86+





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

I said before in that post (-: that I already did a 6h memtest. No errors. The tablet is stable in normal usage, it just freezes/reboots in standby. Mostly already after a few minutes. I also did a 1h prime95 memory test, stable. Though one freeze I also had before the moment I connected a USB stick.

 

6h doesn't say anything, you need 8 passes at minimum with MemTest86+ & a photo of the result is requested.

That I'm aware there are 3 memory tests, the built-in, memtest86 & memtest86+. With the built-in it is just finishing and waiting, with memtest86 it could go incredibly fast but not memtest86 is not as proper as memtest86+.
Per diagnostics test it differs of the speed for finishing and result, because each test uses a different algorithm for testing.


Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.How to fill in your system specs:

 

The "old" original memtest86 was advanced ( PassMark MemTest86 - Version History ) since they parted a few years ago, where memtest86+ is dead since 2013. 6h is enough because it was not done with memtest86+ I did it with the original licensed memtest86 ( MemTest86 - Offical Site of the x86 Memory Testing Tool ) and the 6h means very high chance of proof because it's not xxx cycles like memtest86+ it includes way more single passes of different test algorithms in one 100% test cycle. I also did the "build in" Windows one btw before, no errors too.

Could it be maybe related to the c-state problem with some Intel CPUs? I read about it before, for example here:

Skylake hard locks seeminly when IDLE / CStates ON |Intel Communities

Also please don't get mad at me or anything if I sound cheeky here and there. I totally am happy you're trying to help.