Windows 7 Content Freezing .. Where to go and what to do first?

[scortezmaster]

Hello. Bare with me. I'm not a computer geek so I don't know to do.

I just purchase a new computer from OfficeDepot. An HP Laptop g62 running Windows 7 Home Prem. Service pack 1.

My computer consistently freezes and locks up when searching online, typing in notepad, loading skype, etc... I get a "NOT RESPONDING' on programs at random times causing my computer to literally freezes for up to a min then UNFREEZE and continue as normal. In the past hour I'd say it has froze around 10 times?

This is seriously annoying and I dont know what to do? I figure I post this to get any lead on what I can do. I though it was a browser issue but I've tried every browser, IE, Chrome and Firefox, , but also software such as Skype or just clicking on a file to open.

I content PROGRAM NOT RESPONDING in the top task bar.

I read earlier on searching for program errors which I found tons of but I can't understand what they mean. I took a screen shot of this. Can anyone give me the first step on what to do? I know it's a general question but any direction will help.

I never had this issue with Windows vista on my older laptop. I never though this would be an issue with a new computer.

 

[Thorsen]

If this was just recently purchased, I would take back to Office Depot and demand a replacement. There are a few things that can cause lockups:


From Easy fixes:

System Settings for power options
HDD settings
RAM Settings

To the serious:
Heat
Device Failures
Drivers
Corrupted OS installation
CPU throttling due to heat

For the easy fixes, I would check the power settings and change them to disallow Harddrive (HDD) shutdown or change the min time to shut down HDD's

Also you can disallow Hibernate or sleep and turn off other things like turn off monitor

As for the RAM you can get CPU-Z to see what your CPU and RAM are running at: CPUID - System & hardware benchmark, monitoring, reporting

The SPD tab will tell you your RAM settings that they should be. post Screenshots or compare to the Memory Tab to see what your RAM is currently set to

Before getting into to many things though, I would seriously try to get it replaced.

 

[Thorsen]

If you want to try and troubleshoot the issue here we will need more info.

Please fill in your system specs here: http://www.sevenforums.com/profile.php?do=extra

What version of Windows are you using? Win7 32x or Win7 64x

The event viewer is a bit cryptic. The search Warning there is vague, but you can try and turn off search indexing in case your system is using to many resources to index your files (this can also cause slowdowns on less powerful computers): type "indexing Options" into the Start Menu Search Bar and see if you can pause it if it is running

For the heat issue since this is a laptop, you need to make sure you are not blocking any vents by using either a laptop lap board or using on a flat surface.

 

[scortezmaster]

Thanks for the reply Thorsen. I filled out all I could on the computer details for you. Im running Win 7 64

 

[scortezmaster]

I really hate to take it back but I guess I might have too. I'd like to solve it here If I could.

I did the indexing option however it didn't allow me to pause any of the fields. The pause button was greyed out.


Very ****ing annoying. As I was typing this on the browser in the form the web browser froze again. Im using firefox. A (Not responding) happens. The microsoft wheel is spinning and last around 1 min then it let's me continue. Just before this it happened 5 mins before.

 

[cluberti]

Is that machine a laptop, and does it have a scroll lock key?

 

[scortezmaster]

Yes sir it is a laptop. And no scroll lock key from what I see.

 

[cluberti]

You might want to check to make sure it isn't hidden behind one of the function keys - the last G62 I saw required you to press FN+F12 to emulate scroll lock.

 

[scortezmaster]

What's the big issue with a scroll lock key guys? 2 replies about that key must be something. Thanks in advance.

 

[cluberti]

Because it can be used to cause the machine to crash after a registry value is set (and the machine rebooted), and the resulting crash dump file would tell us why the machine was hung at the time the keystrokes are executed from the keyboard. So yes, it will do "something" .

 

[scortezmaster]

Ok I did a search online and found out that on my g62 the f12 is the scroll lock key button. They say to press fn + f12 to access it? So what does this mean now?

 

[scortezmaster]

So the keys can cause the lock up? But also when clicking on different things with the mouse it'll freeze up too. Just wanted to say that incase you think it's only the keys. Also the laptop never locks up completely where I have to force power off. If I let it alone, after a min or so it'll work again allowing me to type/or continue my task. However it still shouldn't do this at all so much. Look forward to your replies.

 

[cluberti]

No, scortezmaster. What I want you to do is follow the instructions here to allow you to crash your machine via the keyboard, making sure to reboot when finished to make sure the changes take. After you do this, the next time your system freezes up for any length of time, hold down the *right* CTRL key, and press FN+F12 (this will be difficult, but you can do it if you're clever with your fingers) *twice*. This will actually cause your machine to BSOD (this is intentional), and create a dump file in \Windows that will tell us (after analysis) why your machine was hung at the time of the crash.

 

[scortezmaster]

OK doing it. However on the instructions it says " Click the top box, labeled "Automatically manage....", and click the "OK" button.(twice)"

Do I CHECK IT OR UNCHECK the box? It was already checked?

No, scortezmaster. What I want you to do is follow the instructions here to allow you to crash your machine via the keyboard, making sure to reboot when finished to make sure the changes take. After you do this, the next time your system freezes up for any length of time, hold down the *right* CTRL key, and press FN+F12 (this will be difficult, but you can do it if you're clever with your fingers) *twice*. This will actually cause your machine to BSOD (this is intentional), and create a dump file in \Windows that will tell us (after analysis) why your machine was hung at the time of the crash.

 

[scortezmaster]

OK I've followed your directions cluberti. I 'checked' that 'automatically manage' and edited that file from a 2 to a 1 in the 'regedit' which I didn't know how but now do! I restarted the computer...

So I wait until it crashes then hit those keys. Then what? Where do I go to see what I did?

 

[Thorsen]

There is a link at the top of the page: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Follow that. It is the easiest way and gives us the info needed to tell whats going on

That small program will find the dump files and system error files and such and will create a folder. Just zip up the files in the folder and upload the .zip file and we will check it out.

 

[scortezmaster]

Here is the updated report I zipped up. I hope I did it right.

 

[cluberti]

There are no dump files, but you did run the report properly.

 

[scortezmaster]

Is there anyway I can know when dump files are created? Meaning. When the last time my computer froze I pressed "FN" + CTR (right side) + f12 twice. Actually multiple times in a row and nothing happened? I wasn't sure if it was doing anything. No sign was given to me or anything?

 

[Thorsen]

If done correctly, that should have caused a BSoD or blue screen of death

the input from the keyboard must have been locked up at the same time? or something else might have prevented it.

You also need to make sure that dump files are enabled: Set MiniDump


Windows 7:
Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
Click on 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 (64 kB)" in the dropdown box
Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

So when it happens again, your computer should record a .dmp file.