Windows 10: Opening this path causes BSOD

In win98/95 opening the path "C:\Con\Con" would cause blue screen of death... similarly if you open the path "\\.GLOBALROOT\Device\ConDrv\KernelConnect" in a browser on windows 10, BSOD will appear with the SYSTEM_SERVICE_EXCEPTION stopcode & condrv.sys will be the failed file..


detailed video: https://www.youtube.com/watch?v=JjebNlzX6us


not asking for a solution for myself, microsoft must fix this otherwise it can be used in malicious scripts to cause a BSOD loop


using the latest version of windows 10 home

:)

 

wdiwifi.sys and hal.sys cause BSOD IRQL_NOT_LESS_OR_EQUAL on Win 10

Hi Radney,

Tnx for reply.

So you suggest to run verifier on WiFi driver ?

What should I expect to get? will it create a report or cause a BSOD?

Do you suggest taking the following path in verifier?

Create standard setting -> select driver name from a list ->

than choose only the Intel Wifi driver OR only wdiwifi from microsoft OR both ?

Tnx

Guy

 

BAD_POOL_HEADER BSOD, Dump File attached


Hi Groggubus,

Welcome to the 10forums

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

Please follow this suggestion for the BSOD

1. Please open BitDefender and go to the modules,
2. Go to the firewall settings,
3. Uncheck 'Block port scans in the network',
4. Reboot your system <-- IMPORTANT

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD