Lightning strike 0x000100704 et al.

[paramaibo]

Following a lightning strike, my OS has not wanted.to behave. I get bsods when I try to login & when I use "bootlogging", I manage to access task manager & kill applications & msconfig to perform bare knuckle boots. I perhaps installed an unadvised driver, but have since managed to roll it back.

I have timidly restored
The strange thing after the lightning event was that I was without internet, but still had a serviceable laptop, now the opposite is true. What gets me down is the surge in CPU use when I switch on.

 

[Snick]

Hi paramaibo,
Did you have your computer plugged into a surge protector? Sounds like you computer didn't get fried, that's a good thing and reparable.

Please, run DM Log Collector and post logs.
Nic

 

[westom]

Following a lightning strike, my OS has not wanted.to behave.

If lightning caused damage, then hardware is defective. Lightning does nothing to change software. Trying to fix a hardware problem with software will only cure symptoms.

Withholding facts means replies based in wild speculation. Even numbers and text (quoted exactly) in each BSOD is essential to any informed reply. Even that was withheld.

So many other facts say much. For example, if the computer comes from a more responsible manufacturer, the it cam with comprehensive hardware diagnostics - for free. Start by separating hardware from software. Only test one without the other. Exactly why comprehensive hardware diagnostics are first executed long before trying to fix anything.

Windows identifies a problem, records it in system (event) logs. Then works around that problem. Long before making any conclusions or changes, what facts with numbers are recorded in the logs?

 

[torchwood]

Hi

Both the other posts are valid, but i've got another factor to throw in

Are you still triple booting, saw your ealier posts.
The best way to discover if its purely hardware/software is a clean install
DONT forget to make a back-up first, most here use macrium

Roy

 

[Snick]

Torchwood

 

[paramaibo]

I agree that the above posts are valid, but my .I ve managed technology is backward: Win 7 and Lumia off an 8.1

 

[westom]

The best way to discover if its purely hardware/software is a clean install

Shotgunning is to fix something whether it is good or defective. 'Nuke 'n paving" simply destroys useful facts and numbers system (event) logs. Text and numbers from a BSOD also would have immediately identified that defect to but a few suspects. Done a trival time compared to all that data backups and then "nuke 'n paving".

Many who have no idea how a computer works must then shotgun. Keep fixing things until something works.

Assume a defect is in hardware. Software is perfectly good. "Nuke 'n paving" means software loaded in defective hardware can be defective. A problem only involving hardware now has defective hardware and software. Perspective. Increasing the number of suspects means a problem become exponentially more complex.

Two reasons why that solution is not useful

Third, lightning does not damage software. Shotgunning is simply replacing software that was not defective with software that may be defective.

Good diagnostic procedure always collects facts long before even disconnecting one plug. This problem demonstrates why informed consumers need that free, comprehensive hardware diagnostic. Another tool that identifies a defect long before fixing things only on speculation.

Useful information (that means numbers) would empower the fewer who actually know this stuff. Currently the informed cannot list suspects. So what remains is shotgunning - keep replacing good parts until something works. Takes longer. Typically costs more. Often only cures symptoms.

Meanwhile, if lightning was problematic, an informed solution also recommends what should have existed so that lightning need not cause future failures. Yes, lightning damage is directly traceable to human mistakes. Learned what that failure is goes a long way to identifying and correcting that human mistake.

But again, all this is only possible when necessary facts and numbers are first provided. Not destroyed by a "nuke 'n pave".

 

[Snick]

Don't agree with the assumption that software is perfectly good. Have you ever experienced a power failure/shutdown and then attempted to reboot, only to have windows issue an error? If there was a read/write operation in progress and L-strike occurred then, there's a high probability that a bit flip occurred, and resultant BSOD. I'm inclined towards OS damage, being that OP received BSOD when attempting to log on or enabling boot-logging.

paramaibo, can you run sfc /scannow? Do you have win7 DVD? If so, can you access setup.exe on the disk?

Nic

 

[mrjimphelps]

@paramaibo:

Here is something you can try, to test the hardware. It will be easy to do, and you don't need to delete anything off of your hard drive to do it. Create a Linux Live DVD, and boot the computer to the DVD. This will allow you to run Linux from the DVD. You can then try certain things, to see if there are hardware problems. If everything works fine in Linux, then it is likely that the problem is with Windows, which means that a clean install of Windows should fix the problem. If you have the same problems in Linux that you are currently having in Windows, then there are hardware problems which must be repaired.

To make a Linux Live DVD, go to one of the Linux sites (e.g. www.linuxmint.com) and download one of the current ISO files. (Make sure you get the correct one for your computer -- 32-bit vs 64-bit. If you aren't sure which is correct, go with 32-bit.) Once you have done that, insert a blank DVD and right click on the ISO file. Follow the prompts to create a DVD from the image file (the ISO file). Then reboot your computer to the DVD.

Good luck!

Jim

 

[westom]

Don't agree with the assumption that software is perfectly good. Have you ever experienced a power failure/shutdown and then attempted to reboot, only to have windows issue an error? If there was a read/write operation in progress and L-strike occurred then, there's a high probability that a bit flip occurred, and resultant BSOD.

Does not happen. Been doing this stuff (hardware and software) even when disk drives moved heads with motor oil. A power failure during a write once meant the written file was lost and the older version was lost. Decades ago, that changed. If power is lost during a disk write, then the file system falls back to the older (saved) version.

That is new data lost. It does nothing to subvert OS (read only) files. The system may do a data restore when power returns. So that is the perfectly good OS restoring old files. That is never a destroyed OS.

If power failure causes disk corruption, then a computer system was defective when purchased.

I was probably designing and repairing computers before you were even born. How many disk drives have you seen with heads moved by motor oil?

BSODs report failures that the OS cannot work around. Each BSOD provides text and numbers that point quite explicitly to a defect - typically hardware. One who does not understand the message simply posts it exactly so that the fewer who really know this stuff can provide informed advise.

Or one views system (event) logs to learn what is defective long before making any changes.

Anyone with basic computer knowledge wants and uses comprehensive hardware diagnostics to clearly identify a defect, again, long before making any changes. Most consumers do not even know what those are, in part, because so many peers also have limited computer knowledge.

If that computer manufactures is inferior, then one must download those diagnostics for individual parts. For example, best diagnostic for the entire dish drive system (not just the drive) is available for free from every disk drive manufacturer.

Others, who have no idea what that BSOD and other messages says, will only understand "nuke 'n pave". Also called shotgunning.

The informed never makes assumptions. Those denials are wild speculation that even contradicts how a filesystem must work. Denials due to insufficient information - that is posted again by one who learns this stuff before posting.

Every good solution never makes system changes until a defect is first defined. The Linus recommendation is another good example.

 

[Snick]

Nice dissertation @westom! Everyone is entitled to their opinion. Been wrong before, won't be the last. I'm 65 BTW & first computer was Tandy TD-80. Can't say I've ever seen disk drive with hydraulic head actuators. I'm assuming they were used in IBM mainframes early 60s.

In your expert opinion what is OPs next step? Always interested in furthering my understanding.

 

[axe0]

BSODs report failures that the OS cannot work around. Each BSOD provides text and numbers that point quite explicitly to a defect - typically hardware. One who does not understand the message simply posts it exactly so that the fewer who really know this stuff can provide informed advise.

I partially disagree.
Yes, a BSOD often does explicitly point to the cause, but there's a caveat. It quite often happens that although a BSOD seems to point to something, it in reality isn't the cause at all. Even BSOD Experts who have much more experience than I have fall for this.

 

[westom]

In your expert opinion what is OPs next step? Always interested in furthering my understanding.

Long before PCs existed, we would even replace integrated circuits on HP minicomputers to make them work again. A disk drive from another manufacturer (late 1960s) used motor oil for one HP system.

Long before anyone can recommend a fix, first relevant facts must be provided. Comprehensive diagnostic (from the manufacturer) will provide all answers immediately.

Numbers and text from the BSOD are necessary to have any informed assistance.

Facts from the system (event) logs are also needed since that is where the OS stores all discovered defects.

Even numbers from a meter (by requesting instructions) will accuse or exonerate many parts of that system.

Accomplishment is measured by a list of 'parts that are proven good without doubt' and 'parts that are clearly suspect'. Currently both lists are empty - nothing has been accomplished.

No informed solution is possible until facts are provided. Without those facts (and especially numbers), then the world's best technician can recommend nothing useful.