If you choose to rely on the Dell diagnostics, then I'd suggest that you contact Dell for support.
I am only able to offer an opinion based on the information that you provide to me.
Admittedly, we do not do much work with tablets - but Windows remains that same.
On any Windows system - if you use more than about 15 to 20% of the RAM you will start to experience problems.
Why do you say that the BDA driver can't be the reason for the BSOD?
Here is the exact text from the WER section of MSINFO32 (I have highlighted the driver in
RED) This is what I mean by it "blames" the TVTuner driver.:
Code:
14.02.2014 11:52 Windows Error Reporting Fehlerbucket 0x1E_c0000005_R_[COLOR=#ff0000]AbilisBdaTuner[/COLOR]+1995, Typ 0
Ereignisname: BlueScreen
Antwort: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=0x1E_c0000005_R_AbilisBdaTuner+1995&State=1&ID=8a2e7cb0-739b-45fb-9499-8ed9f61109c8
CAB-Datei-ID: 8a2e7cb0-739b-45fb-9499-8ed9f61109c8
Problemsignatur:
P1: 1e
P2: c0000005
P3: b120b995
P4: 0
P5: 2c
P6: 6_3_9600
P7: 0_0
P8: 768_1
P9:
P10:
Angefügte Dateien:
C:\Windows\Minidump\021414-11750-01.dmp
C:\Users\marc\AppData\Local\Temp\WER-27718-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\marc\AppData\Local\Temp\WER7781.tmp.WERInternalMetadata.xml
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_e0693a64f988a8d2912a1a61c249768bb141587c_00000000_cab_0c3ca529
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 021414-11750-01
Berichtstatus: 0
Bucket mit Hash:
Here are the latest 2 crashes from the WER section of MSINFO32:
Code:
17.03.2014 18:00 Windows Error Reporting Fehlerbucket CLOCK_WATCHDOG_TIMEOUT_4_PROC, Typ 0
Ereignisname: BlueScreen
Antwort: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=CLOCK_WATCHDOG_TIMEOUT_4_PROC&State=1&ID=5ab32c2f-426f-42b6-9df5-7cccd0bbaa03
CAB-Datei-ID: 5ab32c2f-426f-42b6-9df5-7cccd0bbaa03
Problemsignatur:
P1: 101
P2: 30
P3: 0
P4: 829db120
P5: 3
P6: 6_3_9600
P7: 0_0
P8: 768_1
P9:
P10:
Angefügte Dateien:
C:\Windows\Minidump\031614-11281-01.dmp
C:\Users\marc\AppData\Local\Temp\WER-36625-0.sysdata.xml
C:\Users\marc\AppData\Local\Temp\WER9470.tmp.WERInternalMetadata.xml
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_101_24105e21bfa55f5221a59fcb50e6bbc9adc47ef_00000000_cab_04de45ef
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 031614-11281-01
Berichtstatus: 0
Bucket mit Hash:
16.03.2014 18:11 Windows Error Reporting Fehlerbucket CLOCK_WATCHDOG_TIMEOUT_4_PROC, Typ 0
Ereignisname: BlueScreen
Antwort: http://wer.microsoft.com/responses/resredir.aspx?sid=10&Bucket=CLOCK_WATCHDOG_TIMEOUT_4_PROC&State=1&ID=861eb869-3c6f-49c5-9672-4bf5ecd74a48
CAB-Datei-ID: 861eb869-3c6f-49c5-9672-4bf5ecd74a48
Problemsignatur:
P1: 101
P2: 30
P3: 0
P4: 825db120
P5: 3
P6: 6_3_9600
P7: 0_0
P8: 768_1
P9:
P10:
Angefügte Dateien:
C:\Windows\Minidump\031614-11812-01.dmp
C:\Users\marc\AppData\Local\Temp\WER-4160953-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\marc\AppData\Local\Temp\WER8848.tmp.WERInternalMetadata.xml
Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_101_9d8197503ccfe647355e2cab4bc1874758a675c_00000000_cab_0b0bae4e
Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 031614-11812-01
Berichtstatus: 0
Bucket mit Hash:
In general, .exe's do not cause BSOD's - because they operate in the user space - not the kernel space (where BSOD's come from).
The first screen shot that you show is very similar to BlueScreenView or WhoCrashed. Those programs have some serious limitations (I had discussed them with the maker of BlueScreenView several years ago) and cannot be counted on for accurate reporting.
This screen shot blames intelppm.sys - a driver (that works in the kernel space) for the processor (CPU). Unfortunately there are several exceptions that likely apply to this diagnosis:
- Windows protects this driver, so it's not likely to be corrupted.
- if the driver was corrupted, you would see many more problems other than just an occasional BSOD - as the drive controls the processor - which does the work for all programs.
- the most common cause of STOP 0x101 BSOD's is hardware, but a large proportion can also be traced to driver issues.
- as the Windows drivers are protected, the most likely driver issues are due to 3rd party (non-Windows) drivers
- How does this happen? Here's a possible scenario:
- Driver A writes to memory space owned by Driver B
- Driver A exits, leaving no trace of it's presence
- later, Driver B tries to access the memory space that Driver A wrote to
- Driver B finds unexpected data at that location, so it panics and crashes
- as nothing else was present, the debugger has nothing else to blame it on other than the driver that owns that memory space
The second screenshot is an application crash. It is in the user space and cannot cause a BSOD directly.
When doing BSOD analysis', I rarely look at more than the names of the application crashes.
There is a possibility that something else is causing skydrive.exe to crash - so that bears looking into after the BSOD's are fixed (and, coincidentally, it may even help to fix the skydrive.exe crashes).
Finally, here's how I do BSOD analysis:
Just FYI - here's how I do BSOD analysis':
- first I rule out 3rd party drivers (over 90% of BSOD's are due to this)
- then I rule out hardware (less than 10% of BSOD's are due to this)
- then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date).
Finally, it is possible that BitDefender (actually it's the drivers that we're concerned with) is a problem.
The "fix" is to remove it and see if the problem goes away.
But you'll have to use another antivirus/firewall while testing - so that you don't get infected.
