On to the MSINFO32 report.....
FIrst, if you look at the MSINFO32 report in another language, you'll find that it's laid out exactly the same.
Even for those languages that use the same word for Drives and for Disks - the layout is the same.
As such, youll need very little foreign language skills to interpret them.
If you do need help, web translators help - but the OP is actually the best translator :0)
First I look at the Components...Network...Adapters section to see info on the wireless USB wifi devices
Next I look at the Components...Storage...Drives section to see how full each partition is
15% is good, 10% is OK, down around 2-3% I start getting worried that the system will spit errors
Then I look at the Components...Storage...Disks section to see how many hard drives they have.
This is just a rough guess at seeing how stressed the PSU is. Most often if there are 3 or more disks, I'll ask for make/model/wattage/and age of the PSU
Anything that's borderline, I'll either suggest removing some power sucking stuff - or trying another PSU. FYI - I generally don't count USB drives, as they can only take 500 ma of current from the USB bus.
Next is Components...Problem Devices. Anything here needs to be looked into. FYI - disabling a device in Device Manager usually happens after the driver loads in Windows, so although the device is disabled, the driver is still in memory. In these cases I stress that the device needs to be enabled, then updated. If they want, then they can disable it again. A special circumstance is when you see a missing PS2 mouse and/or keyboard. If the OP is using a USB mouse and/or keyboard, then it's safe to ignore those errors. Also, FYI, in the early, pre-release versions of W10, every device would show up here - with a comment that it was working properly.
Next I look at Software Environment...Windows Error Reporting. I sort by the Details column and look for all sorts of errors throughout it. It is the place to look for BSOD's that haven't been seen otherwise in the reports.
Some of the things I look at are:
- AppHardBlock - these errors show that programs have been blocked, which makes you question how many incompatible programs are on the system. FYI - if you have an AppHardBlock, then the program it belongs to (not identified in the error) is probably not even able to be uninstalled.
- BEX entries - I believe these are related to BSOD's, but am not sure
- BlueScreen entries - blue screens. If you notice, the P1 seems to be the STOP error code (but again, I'm not sure about this)
- LiveKernelEvents - can be hardware or software. Again, the P1 seems to be the STOP error code (but it's a bit more difficult as the STOP 0x117 errors don't show BSOD's).
Also, if there's a bunch of these, I request a copy of the Admin event log - to see if I can find patterns to why it's happening.
- WindowsUpdateFailures - depends on the dates, but if there's a bunch of recent one's you have to suspect that the system is missing some updates
- FaultBucket 0x... This is the actual BSOD error code Often you'll find more BSOD's here than you will have memory dumps. Keep an eye on them and any pattern that you find.
- FaultBucket LKD.... This seems to be the equivalent of the FaultBucket 0x for the LiveKernelEvents - mostly STOP 0x117 and 0x141. These are mostly drivers that have crashed and recovered. If they hadn't recovered, then there would have been an actual BSOD with a different error (116 instead of 117)
- then check through the rest of the entries to see if there's anything significant.
FWIW - user mode programs cannot cause kernel mode driver crashes. This is the "bible" of those who work with kernel mode.
BUT, a miscrafted request from a user mode program can cause a problem with a kernel mode driver indirectly - so be careful.
We do not replace drivers - we uninstall the program that installed them, and then we install another copy that we presume is a good copy.
Next is the Software Environment...Startup Programs.
Look for items that cause problems - and those that are known BSOD causes (here's a list of some: http://www.carrona.org/drivers/bsod_drivers.php )
Next is the Software Environment...Program Groups.
Again, look for items that cause problems - and those that are known BSOD causes
The next thing we'll address will be the memory dumps. That'll be a long one, so I'll put it in the next post.