Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Windows 7 Computer completely freezing until force shutdown


  • Please log in to reply

#1
Flynatol

Flynatol

    New Member

  • Member
  • Pip
  • 7 posts
Hey,

Recently my computer has been freezing for no apparent reason until I have to force shut it down.
Normally a few seconds before it freezes it makes a little noise.
Heres my most recent crash recorded by Who crashed

System Information (local)
--------------------------------------------------------------------------------

computer name: DEEPTHOUGHT
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, N68-VS3 FX
CPU: AuthenticAMD AMD FX™-4100 Quad-Core Processor AMD586, level: 21
4 logical processors, active mask: 15
RAM: 8572362752 total
VM: 2147352576, free: 1988034560




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 30/11/2013 21:02:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113013-35000-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF88001012FA5)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF88001012FA5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


Thanks in advance,
-Flynn
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
The culprit seems to be the storport.sys which is the Microsoft Storage Port Driver.
Please check your Windows updates for all all important and optional updates to see if there is a updated driver available.
  • 0

#3
Flynatol

Flynatol

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Thanks for the help :D
also would it work if I got the file from another win 7 computer as I cant seem to find an update online?
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Did you check Windows Update page?
You can attempt a SFC AKA System File Checker to replace the faulty file.

SFC /Scannow Win7

Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.
  • 0

#5
Flynatol

Flynatol

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
:( I Couldn't find anything on the update page and The SFC didn't find a thing
  • 0

#6
Flynatol

Flynatol

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Also I looked at who crashed and noticed a few that looked like this
On Wed 15/05/2013 19:41:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051513-34772-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A3E0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008150038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
We can check the temps and voltages very easily by doing the following.

Please download and run Hardware Monitor
Installation (setup version only)
HWMonitor is a hardware monitoring program that reads PC systems main health sensors : voltages, temperatures, fans speed.
The program handles the most common sensor chips, like ITE® IT87 series, most Winbond® ICs, and others. In addition, it can read modern CPUs on-die core thermal sensors, as well has hard drives temperature via S.M.A.R.T, and video card GPU temperature. Please get a screenshot of the sensors window and post it in your next reply.






Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.
  • It is normally the key above your number pad between the F12 key and the Scroll Lock key
  • Now go to Start and then to All Programs
  • Scroll to Accessories and then click on Paint
  • In the Empty White Area click and hold the CTRL key and then click the V
  • Go to the File option at the top and click on Save as
  • Save as file type JPEG and save it to your Desktop
  • Attach it to your next reply

Posted Image
  • 0

#8
Flynatol

Flynatol

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Its Crashed again and its saying reboot and select proper boot device (So I cant even use it) I believe this is to do with the hard drive as I have had a heat problem with the hard drive but the cause was never found and after cleaning the bottom of it it worked fine.
Thanks,
-Flynn

Edited by Flynatol, 22 December 2013 - 08:06 AM.

  • 0

#9
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Is the drive being identified in the bios?
We need to check the HD but it may very well be a failed HD at this point.


Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (chose "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions
  • 0

#10
Flynatol

Flynatol

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
We changed the power leads from the cd drive and the hard drive and we also unplugged the hard drive and plugged it back in again now its working and hasn't frozen so far
  • 0

#11
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Still may be a failing HD so if you can run the diagnostics it will help. Could be just a faulty lead or bad connection but lets be sure. :thumbsup:
  • 0

#12
Flynatol

Flynatol

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
After the crash it did a massive check disk, is that the same sort of thing?
and also what am I meant to download :P
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Go back to post 9 for the hd diagnostics instructions.
The chkdsk ran on a error is not the same one as the one I need you to run. what I need you to run is a chkdsk \r which test 5 things where a normal chkdsk only checks 3.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP