Likelihood of BSOD Data Corruption?

[bebop460]

I've always thought that a BSOD doesn't necessarily cause corruption, and usually after running CHK DSK and SFC/scannow afterwards, you're good to go. Am I correct in that?

It's something I've always wondered, especially as I just got a (plug and play) BSOD and debating a reinstall.

Here's what happened, if you're curious: My dog tripped over my usb extension cable, which caused my mouse (M95) and DS4 controller to disconnect. I plugged it back in, and the LED started stroking out, disconnecting and reconnecting. I switched cables, the OS reinstalled the driver, I then went to fix the DS4, which was supposedly connected to DS4Windows, yet the lights were off. I switched controller profiles, and the OS attempted to reinstall the xbox 360 controller driver, then I got a PNP BSOD (0XCA).

 

[BadAsAl]

BSOD can be caused by a lot of things. In your case, since the cause of your problems was a physical drop of your controller, it is likely something broke on the DS4. That can definitely cause a BSOD. Only way to know is to try the DS4 on another computer or try a different DS4.

 

[bebop460]

Nothing dropped, he just bumped the cables which caused the devices to disconnect. Both work now. The BSOD and having to reinstall the drivers was quite a freak occurrence.

Not sure what the odds are of data corruption.

 

[nikoskostantopoulow]

"The dreaded ‘Blue Screen of Death’ can also result in drive errors."

https://www.pcrepairmansblog.com/hdd-regenerator-review/

I had BSOD due to CPU overclocking resulting on data corruption on my SSD and me reinstalling the Windows.
I'd say it has to do with how lucky you are.

 

[howtobeironic]

As BadAsAl suggested BSOD's both can and may cause damage because their reasons and consequences.
So, a BSOD may have been caused by a kernel driver being corrupted because your drive is going bad, and you'll see damage after BSOD.
Maybe (low odds though) the drive was on an important spot and got interrupted. You cannot tell if it caused or it was the result.
Also, if you're done please mark a best answer.

 

[Gam3r01]

As BadAsAl suggested BSOD's both can and may cause damage because their reasons and consequences.
So, a BSOD may have been caused by a kernel driver being corrupted because your drive is going bad, and you'll see damage after BSOD.
Maybe (low odds though) the drive was on an important spot and got interrupted. You cannot tell if it caused or it was the result.
Also, if you're done please mark a best answer.

First, dont beg for BAs, let them come naturally.
Second, this thread is over 3.5 years old at this point, I encourage you to check the dates before posting.

 

[howtobeironic]

As BadAsAl suggested BSOD's both can and may cause damage because their reasons and consequences.
So, a BSOD may have been caused by a kernel driver being corrupted because your drive is going bad, and you'll see damage after BSOD.
Maybe (low odds though) the drive was on an important spot and got interrupted. You cannot tell if it caused or it was the result.
Also, if you're done please mark a best answer.

First, dont beg for BAs, let them come naturally.
Second, this thread is over 3.5 years old at this point, I encourage you to check the dates before posting.

Not begging for the BA's, I just wanted this to close out, either. Also BadAsAl should get it if that's the case.
I rarely check dates, just found it sifting through the win7 mainpage. Thanks for your warning.