Windows 7 Computer Freezes Randomly

Page 1 of 8 123 ... LastLast

  1. Posts : 57
    Windows 7 Home Premium 64-Bit
       #1

    Windows 7 Computer Freezes Randomly


    Hello,
    Ive been searching for a problem thats bothered me for quiet a while and i just cant seem to fix it, My problem is that when im using my computer it will randomly freeze whether im watching youtube videos, browsing the net or just playing games (Starcraft 2, League of Legends) ive reinstalled windows 7, ive tried updating my drivers but it just wont go away, so when it freezes it just stays at the screen it froze at and the sound is like looping and it does not go to a bluescreen or reboot i have to hold the power down.

    Specs:
    Windows 7 Ultimate
    6GB DDR3 Memory
    AMD Athlon II X4 610e quad-core processor
    1TB HDD
    AMD Radeon HD 6570 1024MB
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Please provide us with your Event Viewer administrative logs by following these steps:


    Click Start Menu
    Type eventvwr into Search programs and files (do not hit enter)
    Right click eventvwr.exe and click Run as administrator
    Expand Custom Views
    Click Administrative Events
    Right click Administrative Events
    Save all Events in Custom View As...
    Save them in a folder where you will remember which folder and save as Errors.evtx
    Go to where you saved Errors.evtx
    Right click Errors.evtx -> send to -> compressed (zipped) folder
    Upload the .zip file here.
      My Computer


  3. Posts : 130
    Windows 7 Ultimate x64
       #3

    Follow these steps to fix computer freezes problem::

    Remove unused programs
    Install and run antispyware software
    Free up wasted space with Disk Cleanup tool
    Defragment your hard disk drive

    Disconnect unused network connections:

    Click Start, and then click My Computer.

    On the Tools menu, click Disconnect Network Drive.

    Select the network drives that you no longer need, and then click OK.

    ALSO

    Click Start - Run, type in %temp% and then click OK.

    Once that temp folder is open and you can view its contents, select and delete EVERYTHING that's inside it.

    It's all junk and is a good place for "nasties" to hide.

    If a few files resist being deleted, that's normal. Leave them alone and delete EVERYTHING else.

    Repeat the steps with c:\windows\temp
      My Computer


  4. Posts : 57
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #4

    Ok here is the event viewer ive already gone through this just says kernel power event 41 but here
      My Computer


  5. Posts : 57
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #5

    alishathomaz said:
    Follow these steps to fix computer freezes problem::

    Remove unused programs
    Install and run antispyware software
    Free up wasted space with Disk Cleanup tool
    Defragment your hard disk drive

    Disconnect unused network connections:

    Click Start, and then click My Computer.

    On the Tools menu, click Disconnect Network Drive.

    Select the network drives that you no longer need, and then click OK.

    ALSO

    Click Start - Run, type in %temp% and then click OK.

    Once that temp folder is open and you can view its contents, select and delete EVERYTHING that's inside it.

    It's all junk and is a good place for "nasties" to hide.

    If a few files resist being deleted, that's normal. Leave them alone and delete EVERYTHING else.

    Repeat the steps with c:\windows\temp
    Ok ive done that, any other tips?
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    iMarioo said:
    Ok here is the event viewer ive already gone through this just says kernel power event 41 but here
    All the Left 4 dead freezes were related to a memory exception (either the ram or a driver).



    These crashes were caused by memory corruption/exception (Cx05) probably a driver.
    Please run these two tests to verify your memory and find which driver is causing the problem.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have a Raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5-7 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.


    RAM - Test with Memtest86+






    Driver Verifer

    Using Driver Verifier is an iffy proposition.
    Most times it'll crash and it'll tell you what the driver is.
    But sometimes it'll crash and won't tell you the driver.
    Other times it'll crash before you can log in to Windows.
    If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
    Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like.
    From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    If you are using win 8 add these

    - Concurrency Stress Test
    - DDI compliance checking

    Reboot the system and wait for it to crash to the Blue Screen.
    Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    Thanks to JGriff2 & Usasma.
    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Driver Verifier

    Using Driver Verifier (Windows Drivers)
      My Computer


  7. Posts : 57
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #7

    zigzag3143 said:
    iMarioo said:
    Ok here is the event viewer ive already gone through this just says kernel power event 41 but here
    All the Left 4 dead freezes were related to a memory exception (either the ram or a driver).



    These crashes were caused by memory corruption/exception (Cx05) probably a driver.
    Please run these two tests to verify your memory and find which driver is causing the problem.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have a Raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5-7 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.


    RAM - Test with Memtest86+






    Driver Verifer

    Using Driver Verifier is an iffy proposition.
    Most times it'll crash and it'll tell you what the driver is.
    But sometimes it'll crash and won't tell you the driver.
    Other times it'll crash before you can log in to Windows.
    If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
    Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like.
    From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    If you are using win 8 add these

    - Concurrency Stress Test
    - DDI compliance checking

    Reboot the system and wait for it to crash to the Blue Screen.
    Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    Thanks to JGriff2 & Usasma.
    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Driver Verifier

    Using Driver Verifier (Windows Drivers)
    Thank you so much for taking time out of your life to help me. I am not overclocking, I dont know what Raid is i am going to run memtest tonight and where would the memory dumps be?

    *EDIT*

    Ok so i ran i followed the instructions given for the verifier. It proceeded to boot and bluescreen, i let it reboot a second time to see if it would error the same thing and yes it did, i dont know where the dumps would be but i think it probably is the file created in c:/windows/minidump so i took it tried to open it but permission is denied even though i am administrator. On the bluescreen it said something about The IO Manager and how i have to replace it with a working one.
    Last edited by iMarioo; 16 Apr 2012 at 05:00.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Please upload the DMPS to us.



    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    If you are overclocking STOP


    We could also use some system information, which you can get easily by running msinfo32.
    To do that go to start>run>type msinfo32>enter

    When it is finished running go to file>save>name it and upload to us here.


    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
      My Computer


  9. Posts : 57
    Windows 7 Home Premium 64-Bit
    Thread Starter
       #9

    zigzag3143 said:
    Please upload the DMPS to us.



    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    If you are overclocking STOP


    We could also use some system information, which you can get easily by running msinfo32.
    To do that go to start>run>type msinfo32>enter

    When it is finished running go to file>save>name it and upload to us here.


    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Yes ive enabled minidumps awhile ago, but my problem is access is denied when trying to open or zip up the DMP file.

    *EDIT*

    Its fine, here is the system info and dmp file.

    *EDIT-2*

    I used a program called bluescreen viewer to read the dump files, i looked up the drivers crashing the system and it turned out to be a daemon tools driver so i uninstalled daemontools but i just dont think thats it, before when i didnt have daemon tools it still froze.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    The one crash uploaded was driver verified and related to dtsoftbus01.sys. Make sure you turn verifier off because it can trigger false positive crashes.

    It may not have been just daemon. One thing of note AVG. It is sometimes a contributing factor.
      My Computer


 
Page 1 of 8 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 02:56.
Find Us