Keyboard and mouse frozen. BSOD at random.

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 12
    Windows 7 Home Premium 64 bit
    Thread Starter
       #11

    I've found out that it only works with Ultimate or Enterprise while I have Home Premium.

    I've tried a tool called Vistalizator but that gave me a lot of problems, at one point my pc couldn't even boot up and I've spent the entire afternoon fixing it. I'm never using it again.

    Do you know if there's another way to change the language? If there's no other option I could run those logs into Google Translate.
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #12

    I need to get used to check first the Windows 7 version before suggesting to change the language

    I only know a way to change the language permanent, with a reinstallation (repair install, reinstallation or clean install) but I'm not sure if changing the language is possible in all reinstallation possibilities. There are a few reinstallation types,
    • A repair install, could be said that it is an in-place upgrade, you basically reinstall Windows keeping all programs and personal files, only settings that have been modified to the system are reverted to the default.
    • A reinstallation, this is an installation that reinstalls Windows without deleting everything (meaning you keep personal files, but programs are removed).
    • A clean reinstallation, this is an installation wherein first the whole hard drive is wiped before the installation part starts.
      My Computer


  3. Posts : 12
    Windows 7 Home Premium 64 bit
    Thread Starter
       #13

    Uhm, I think it would be easier for me to translate those logs. Which one do you want me to start first?
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #14

    I don't know, I can't tell which might be important and which not.
      My Computer


  5. Posts : 12
    Windows 7 Home Premium 64 bit
    Thread Starter
       #15

    Ok. I've translated most of the logs except eventlog.txt because there are more than 20.000 entries.
    So I've installed a copy of Windows 7 Ultimate (in English) as a virtual machine.

    I was able to export the event logs from my Home installation into Ultimate and they're in English. I saved the entire log as a .evtx file however I don't know how to run them into DM log collector.

    I can see them on my pc from the Event Viewer (Action > Open saved log > choose my .evtx file).

    Would it be ok if I send you the event logs as an .evtx files? Otherwise I don't know what else to do.
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #16

    The eventlog.txt is the most important one, we know it has a lot of entries which is why I usually say that it is too much to translate.

    The DM Log Collector collects the event logs, no need to add another copy of the event logs.
      My Computer


  7. Posts : 12
    Windows 7 Home Premium 64 bit
    Thread Starter
       #17

    The problem is that, if I understood right, DM log reads only the file in Event viewer > Windows Logs > System. This one is not in English.
    My evtx file is Under Event viewer > Saved Logs > seven_eng.evtx and DM can't analyze it. This one is in English.

    See pics attached.

    So eventslog.txt from DM would be useless to you since is not in English. That's why I was asking if it's ok to send my event logs as a separate evtx file instead.
      My Computer


  8. Posts : 7,050
    Windows 10 Pro
       #18

    We could modify the DM to collect saved logs, but easier is to zip those logs and upload the zip.

    My evtx file is Under Event viewer > Saved Logs > seven_eng.evtx and DM can't collect it.
    Correction made :)
      My Computer


  9. Posts : 12
    Windows 7 Home Premium 64 bit
    Thread Starter
       #19


    Here's the file. Hope it's ok.
      My Computer


  10. Posts : 7,050
    Windows 10 Pro
       #20

    Let's see if we can find anything by forcing drivers to BSOD by checking if they violate something



    Diagnostic Test

     DRIVER VERIFIER


       Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

       Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:24.
Find Us