Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
[SOLVED] BSOD when i running windows store
- Thread starter whamy
- Start date
Hi,
The attached DMP files are of the KERNEL_SECURITY_CHECK_FAILURE (139) bug check.
This bug check indicates that the kernel has detected the corruption of a critical data structure.
Unable to load image \SystemRoot\system32\DRIVERS\mobile_connect_cdc_ecm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mobile_connect_cdc_ecm.sys
*** ERROR: Module load completed but symbols could not be loaded for mobile_connect_cdc_ecm.sys
Probably caused by : mobile_connect_cdc_ecm.sys ( mobile_connect_cdc_ecm+1a20 )
^^ This files most often belongs to product CDC ECM Class Driver (x86). and were most often developed by company Mobile Connector.
-------------------------------
If we take a look at another *139 bug check you have:
Unable to load image \??\C:\Program Files\Common Files\Bitdefender\Bitdefender Firewall\bdfndisf6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bdfndisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfndisf6.sys
Probably caused by : bdfndisf6.sys ( bdfndisf6+2658 )
^^ BitDefender Firewall.
What's likely going on here is BitDefender is causing conflicts with the NETBIOS ports and your Mobile Connector. Please remove and replace BitDefender with Windows 8's built-in Windows Defender:
BitDefender removal - How to uninstall Bitdefender
Windows Defender (how to turn on after removing BD) - Windows Defender - Turn On or Off in Windows 8
-- In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
-------------------------------
If after the above you're still crashing, please enable Driver Verifier:
Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in %systemroot%\Minidump
Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users
Regards,
Patrick
The attached DMP files are of the KERNEL_SECURITY_CHECK_FAILURE (139) bug check.
This bug check indicates that the kernel has detected the corruption of a critical data structure.
Unable to load image \SystemRoot\system32\DRIVERS\mobile_connect_cdc_ecm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mobile_connect_cdc_ecm.sys
*** ERROR: Module load completed but symbols could not be loaded for mobile_connect_cdc_ecm.sys
Probably caused by : mobile_connect_cdc_ecm.sys ( mobile_connect_cdc_ecm+1a20 )
^^ This files most often belongs to product CDC ECM Class Driver (x86). and were most often developed by company Mobile Connector.
-------------------------------
If we take a look at another *139 bug check you have:
Unable to load image \??\C:\Program Files\Common Files\Bitdefender\Bitdefender Firewall\bdfndisf6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bdfndisf6.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfndisf6.sys
Probably caused by : bdfndisf6.sys ( bdfndisf6+2658 )
^^ BitDefender Firewall.
What's likely going on here is BitDefender is causing conflicts with the NETBIOS ports and your Mobile Connector. Please remove and replace BitDefender with Windows 8's built-in Windows Defender:
BitDefender removal - How to uninstall Bitdefender
Windows Defender (how to turn on after removing BD) - Windows Defender - Turn On or Off in Windows 8
-- In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
-------------------------------
If after the above you're still crashing, please enable Driver Verifier:
Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in %systemroot%\Minidump
Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users
Regards,
Patrick
Has Sysnative Forums helped you? Please consider donating to help us support the site!