Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Computer freezes


  • Please log in to reply
5 replies to this topic

#1 maayan1234

maayan1234

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:59 AM

Posted 15 January 2012 - 07:01 AM

hallo ,
my Computer freezes without any reason, it can happen after a few seconds and can happen after two days. it's not giving me any log file or blue screen to see what is the problem. requires reboot only.

i have Tested computer memory and 100% work in the Laboratory and everything was stable and without problem

I attached the log file from the HIJACKTHIS ,it's may be usefull
I'm really frustrated and using the computer with fear .

Thank you

Mod Edit: Removed HJT log, since that is a malware tool and there is no apparent reason to post such here in Win 7 forum. See Link near top of main forum webpage ~ Hamluis.

Edited by hamluis, 15 January 2012 - 11:24 AM.


BC AdBot (Login to Remove)

 


#2 noknojon

noknojon

  • Banned
  • 10,871 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:06:59 PM

Posted 15 January 2012 - 07:05 PM

Hi -
I know that you say there are no Blue screen or similar problems, but this may generate an error log for us -

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

Thank You -

#3 maayan1234

maayan1234
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:59 AM

Posted 16 January 2012 - 05:27 AM

this is what i got from the bluescreenview
i hope it will be helpful
thank you.
as you can see the Crash date isn't update for this days cause it has crashed yasterday and today and you cant see it in the log i attached.


==================================================
Dump File : 122811-19546-01.dmp
Crash Time : 28/12/2011 21:49:44
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`049938f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2aec
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+4b2aec
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122811-19546-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 112011-24585-01.dmp
Crash Time : 20/11/2011 21:19:14
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff980`6c957cc4
Parameter 2 : 00000000`00000001
Parameter 3 : fffff880`012e2648
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+80640
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+80640
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112011-24585-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 284,656
==================================================

==================================================
Dump File : 110511-25677-01.dmp
Crash Time : 05/11/2011 18:56:14
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`049678f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2aec
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+4b2aec
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\110511-25677-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 110411-25989-01.dmp
Crash Time : 04/11/2011 16:08:48
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04b41028
Parameter 3 : 00000000`f220008b
Parameter 4 : 00000000`0002010a
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+80640
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\110411-25989-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 282,984
==================================================

==================================================
Dump File : 110411-24117-01.dmp
Crash Time : 04/11/2011 00:29:54
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`049b48f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b2aec
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+4b2aec
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\110411-24117-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,870 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:59 AM

Posted 16 January 2012 - 10:13 AM

FWIW: Microsoft Answers Topic

Louis

#5 akwe-xavante

akwe-xavante

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:08:59 AM

Posted 17 January 2012 - 12:20 PM

First thing to do if i were you is backup backup backup everything on the hard thats important to you onto some other external medium.

My experience is that when something like this happens and theres no record in the windows log file it means that an error message could not be written to the log file on the hard drive.

This could be because the hard drive no longer exists on the system, it stopped working, it switched off, or information in the memory dissapeared.

An intermittent problem is always the worst to diagnose.

What make, model, size and age is your hard drive?

It is my experience that larger hard drives fail far more quickly than smaller ones. Laptop hard drives have a much shorter life than those fitted inside a desktop / tower.

Identify the make and model, visit the manufacturers website and download there diagnostcs tool, follow instructions on how to use it and use it to run tests on your hard drive.

If your hard drive fails tests this doesn't nessesarily mean that its faulty, it may mean that the tool lost communication with the drive.

Make sure that power is getting to the drive at all times and the communication cable is in good condition and fits snuggly

You could also run Scandisk or Checkdisk, same thing.

If you have a perminent problem the cause can be found easily, if you have an irregular problem it can be a nightmare.

Just because tests pass doesn't mean the item being tested is OK, it just means it passed those tests on that occasion. For something to fail it must be faulty at the very moment the test is being performed!

Edited by akwe-xavante, 17 January 2012 - 12:28 PM.


#6 maayan1234

maayan1234
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:03:59 AM

Posted 19 January 2012 - 05:15 AM

first of all thank you for the answer


First thing to do if i were you is backup backup backup everything on the hard thats important to you onto some other external medium.

My experience is that when something like this happens and theres no record in the windows log file it means that an error message could not be written to the log file on the hard drive.

This could be because the hard drive no longer exists on the system, it stopped working, it switched off, or information in the memory dissapeared.

An intermittent problem is always the worst to diagnose.

What make, model, size and age is your hard drive? i have western digital HD for 2 years

It is my experience that larger hard drives fail far more quickly than smaller ones. Laptop hard drives have a much shorter life than those fitted inside a desktop / tower.

Identify the make and model, visit the manufacturers website and download there diagnostcs tool, follow instructions on how to use it and use it to run tests on your hard drive. i updated the HD driver and run all the neccesary test and nothing up the all test goes ok

If your hard drive fails tests this doesn't nessesarily mean that its faulty, it may mean that the tool lost communication with the drive.

Make sure that power is getting to the drive at all times and the communication cable is in good condition and fits snuggly

You could also run Scandisk or Checkdisk, same thing. i made those test and againg it was ok

If you have a perminent problem the cause can be found easily, if you have an irregular problem it can be a nightmare.

Just because tests pass doesn't mean the item being tested is OK, it just means it passed those tests on that occasion. For something to fail it must be faulty at the very moment the test is being performed!


i have no idea what can it be ?? i try to Diagnose each part by disconnecting it and active the PC without it and nothing has changed.
ill try to run the computer on another HD and ill see what will happen

thanks again

Edited by maayan1234, 19 January 2012 - 05:17 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users