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

Diagnosis the Cause of Multiple Freezeups.


  • Please log in to reply
7 replies to this topic

#1 DrSatanDracula

DrSatanDracula

  • Members
  • 72 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York City
  • Local time:08:36 AM

Posted 15 October 2014 - 07:04 AM

Note: The topic should read diagnosis FOR the cause of multiple freezeups.

 

Dear everyone,

 

I've been having a problem with multiple freezeups for the last two weeks that have been troublesome, to say the least. As a precaution, I've backed up my data.

 

I am coming to you folks for assistance as you are remarkably more helpful than the people at HP, who are essentially worker drones who read off a list of things. They also seem intent on trying to violate their warranties in order to screw their customers, and I shall not be purchasing (and suggest no one else purchases) anything from them.

 

Now, I had thought I had finally resolved the issue after running a long (8 hour) chkdisk that resolved multiple problems, but just now (10 minutes ago) it froze.

 

The freeze ups seem to be random. I might be playing a game on Steam, or working on the internet, or speaking on an instant messenger, or any other number of things with no special rhyme or reason. The one thing that is consistent is that my HD indicator light goes a steady yellow (non-wavering) and my computer freezes. I can do nothing but move my mouse, which doesn't freeze, which is also very odd.

 

Save for in one instance, I have had no BSOD message since the crashes have become frequent. When the BSOD occurred, I was having multiple freeze ups right at the start of windows, within say 60 seconds. Usually they occur once per day at most, or once every two days, or once every three days - but have been consistent enough to be problematic.  A windows startup repair found nothing wrong. 

 

The diagnostic programs for my HD and for my memory have shown no problems.

 

I am at a loss for what is the exact cause of my problems and I would appreciate any help in diagnosing so so I can go armed to HP with some specific information as to what it might be, so they might actually have to live up to their warranties.

 

My system specs are:

 

The results of the chddisk (which was performed AFTER this recent BSOD) are as followed:

 

 

 

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                        

CHKDSK is verifying files (stage 1 of 3)...
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1326c759 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x22b617 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 2274839.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x127f8e28 for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31c272 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3261042.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xe030f14 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31c7ac is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3262380.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xe030d4c for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x31c899 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3262617.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x127f8e2a for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x321dcd is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3284429.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xeb2c8f0 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34025b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408475.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x74a3939 for possibly 0x3 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x340266 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408486.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f71cf for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x340294 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408532.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f7386 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x340299 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408537.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f71f3 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3402a2 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408546.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x109eebf4 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3402c2 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408578.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xf657e20 for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3402fe is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408638.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f71ec for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34038e is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408782.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f70cb for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3403d9 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408857.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f71ab for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3403f3 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408883.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x14519acd for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3403f4 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3408884.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f71c0 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x3425bb is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3417531.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f7254 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34e31f is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3466015.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x149f71db for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34e342 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3466050.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x187ac910 for possibly 0x10 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34f262 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3469922.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1265a0c0 for possibly 0xc clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34f474 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3470452.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x6aee658 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34f4b5 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3470517.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x706fa2a for possibly 0x2 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34f4b8 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3470520.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xeb35394 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34f51c is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3470620.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xeb2d918 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34f60b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3470859.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x1265a0cc for possibly 0x4 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x34f663 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 3470947.
  3502848 file records processed.                                          File verification completed.
  2210 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              44 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
The file reference 0x100000034f0b7 of index entry GUR5002.tmp of index $I30
with parent 0x470 is not the same as 0x200000034f0b7.
Deleting index entry GUR5002.tmp in index $I30 of file 1136.
The VCN 0x26470 of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0x26471 of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0x26473 of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0x26472 of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The VCN 0xffffffffffffffff of index $I30 in file 0x5b4 is already in use.
Correcting error in index $I30 for file 1460.
The index bitmap $I30 in file 0x5b4 is incorrect.
Correcting error in index $I30 for file 1460.
The two index entries of length 0x78 and 0x70 are either identical
or appear in the wrong order.
e4 db 09 00 00 00 0e 00 78 00 64 00 00 00 00 00  ........x.d.....
b4 05 00 00 00 00 03 00 c9 1a 71 74 3b b2 cf 01  ..........qt;...
0b b7 71 74 3b b2 cf 01 0b b7 71 74 3b b2 cf 01  ..qt;.....qt;...
c9 1a 71 74 3b b2 cf 01 00 20 00 00 00 00 00 00  ..qt;.... ......
97 1d 00 00 00 00 00 00 20 20 00 00 00 00 00 00  ........  ......
11 01 42 00 4f 00 63 00 74 00 73 00 64 00 70 00  ..B.O.c.t.s.d.p.
5f 00 73 00 4c 00 61 00 5b 00 32 00 5d 00 2e 00  _.s.L.a.[.2.]...
6a 00 73 00 00 00 00 00 38 00 78 00 39 00 30 00  j.s.....8.x.9.0.
3b 00 61 00 70 00 70 00 3d 00 42 00 6f 00 43 00  ;.a.p.p.=.B.o.C.
----------------------------------------------------------------------
7a a4 08 00 00 00 14 00 70 00 58 00 01 00 00 00  z.......p.X.....
b4 05 00 00 00 00 03 00 91 bc 96 79 2c b1 cf 01  ...........y,...
f9 d7 a5 79 2c b1 cf 01 f9 d7 a5 79 2c b1 cf 01  ...y,......y,...
91 bc 96 79 2c b1 cf 01 00 10 00 00 00 00 00 00  ...y,...........
5e 05 00 00 00 00 00 00 20 20 00 00 00 00 00 00  ^.......  ......
0b 02 32 00 31 00 30 00 44 00 41 00 34 00 7e 00  ..2.1.0.D.A.4.~.
31 00 2e 00 4a 00 53 00 25 7c 01 00 00 00 00 00  1...J.S.%|......
5a 67 1d 00 00 00 06 00 f0 00 d4 00 01 00 00 00  Zg..............
Sorting index $I30 in file 1460.
The file reference 0x200000034f0f4 of index entry 1.122[1].jpg of index $I30
with parent 0x5b4 is not the same as 0x400000034f0f4.
Deleting index entry 1.122[1].jpg in index $I30 of file 1460.
The file reference 0x100000034f0ec of index entry 1.131[1].jpg of index $I30
with parent 0x5b4 is not the same as 0x200000034f0ec.
Deleting index entry 1.131[1].jpg in index $I30 of file 1460.
The file reference 0x100000034f0e6 of index entry 1.611[1].jpg of index $I30
with parent 0x5b4 is not the same as 0x900000034f0e6.
Deleting index entry 1.611[1].jpg in index $I30 of file 1460.
Unable to locate the file name attribute of index entry 10-1x1[2].jpg
of index $I30 with parent 0x5b4 in file 0x33fef1.
Deleting index entry 10-1x1[2].jpg in index $I30 of file 1460.
Unable to locate the file name attribute of index entry 10-1X1~2.JPG
of index $I30 with parent 0x5b4 in file 0x33fef1.
Deleting index entry 10-1X1~2.JPG in index $I30 of file 1460.
The file reference 0x300000034f0e7 of index entry 11-500x250[1].jpg of index $I30
with parent 0x5b4 is not the same as 0x400000034f0e7.
Deleting index entry 11-500x250[1].jpg in index $I30 of file 1460.
The file reference 0x300000034f0e7 of index entry 11-500~1.JPG of index $I30
with parent 0x5b4 is not the same as 0x400000034f0e7.
Deleting index entry 11-500~1.JPG in index $I30 of file 1460.
The file reference 0x200000034f0e1 of index entry 111-500x250[2].jpg of index $I30
with parent 0x5b4 is not the same as 0x300000034f0e1.
Deleting index entry 111-500x250[2].jpg in index $I30 of file 1460.
The file reference 0x200000034f0e1 of index entry 111-50~2.JPG of index $I30
with parent 0x5b4 is not the same as 0x300000034f0e1.
Deleting index entry 111-50~2.JPG in index $I30 of file 1460.
The file reference 0x200000034f0f4 of index entry 1122_1~1.JPG of index $I30
with parent 0x5b4 is not the same as 0x400000034f0f4.
Deleting index entry 1122_1~1.JPG in index $I30 of file 1460.
The file reference 0x100000034f0ec of index entry 1131_1~1.JPG of index $I30
with parent 0x5b4 is not the same as 0x200000034f0ec.
Deleting index entry 1131_1~1.JPG in index $I30 of file 1460.
The file reference 0x200000034f0c0 of index entry 133-500x250[2].jpg of index $I30
with parent 0x5b4 is not the same as 0x900000034f0c0.
Deleting index entry 133-500x250[2].jpg in index $I30 of file 1460.
The file reference 0x200000034f0c0 of index entry 133-50~2.JPG of index $I30
with parent 0x5b4 is not the same as 0x900000034f0c0.
Deleting index entry 133-50~2.JPG in index $I30 of file 1460.
The file reference 0x100000034f0fc of index entry 1459571[1].htm of index $I30
with parent 0x5b4 is not the same as 0x500000034f0fc.
Deleting index entry 1459571[1].htm in index $I30 of file 1460.
The file reference 0x100000034f0fc of index entry 145957~1.HTM of index $I30
with parent 0x5b4 is not the same as 0x500000034f0fc.
Deleting index entry 145957~1.HTM in index $I30 of file 1460.
The file reference 0x200000020b517 of index entry 1_smioeg3r[1].swf of index $I30
with parent 0x5b4 is not the same as 0x900000020b517.
Deleting index entry 1_smioeg3r[1].swf in index $I30 of file 1460.
The file reference 0x200000020b517 of index entry 1_SMIO~1.SWF of index $I30
with parent 0x5b4 is not the same as 0x900000020b517.
Deleting index entry 1_SMIO~1.SWF in index $I30 of file 1460.
The file reference 0xc0000002000f9 of index entry 21042952CAMS8HS0.js of index $I30
with parent 0x5b4 is not the same as 0xe0000002000f9.
Deleting index entry 21042952CAMS8HS0.js in index $I30 of file 1460.
The file reference 0x50000002e6891 of index entry 30FD59~1.HTM of index $I

 

The one BSOD recently is as followed:

 

 

==================================================
Dump File         : 101214-29156-01.dmp
Crash Time        : 10/12/2014 8:49:47 AM
Bug Check String  : REGISTRY_ERROR
Bug Check Code    : 0x00000051
Parameter 1       : 00000000`00000001
Parameter 2       : fffff8a0`00023010
Parameter 3       : 00000000`00e8f000
Parameter 4       : 00000000`00000374
Caused By Driver  : VIDEOPRT.SYS
Caused By Address : VIDEOPRT.SYS+fe39b010
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+75c00
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\101214-29156-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 302,113
Dump File Time    : 10/12/2014 8:50:39 AM
==================================================
 

 

My system specs are:

 

Windows 7 Home Premium
SP1 Build 7601
i7-2600 @ 3.40 ghz
12gigs ram


Edited by DrSatanDracula, 15 October 2014 - 07:17 AM.


BC AdBot (Login to Remove)

 


m

#2 ElfBane

ElfBane

  • Members
  • 775 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Florida
  • Local time:08:36 AM

Posted 15 October 2014 - 10:04 AM

You have a bad RAM stick, and/or the HDD is failing. Remove RAM sticks one-at-a-time to isolate.



#3 DrSatanDracula

DrSatanDracula
  • Topic Starter

  • Members
  • 72 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York City
  • Local time:08:36 AM

Posted 15 October 2014 - 11:56 AM

You have a bad RAM stick, and/or the HDD is failing. Remove RAM sticks one-at-a-time to isolate.

Dear Elfbane,

 

How can I communicate to HP that it is a likely RAM problem? The memory diagnostics do not find anything wrong with the RAM. They're very strict about this now, threatening that I might be charged if they can't find anything wrong with it.

 

I am still under warrant with my package and if I could, I'd like that memory to be sent to me free of charge.



#4 ElfBane

ElfBane

  • Members
  • 775 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Florida
  • Local time:08:36 AM

Posted 15 October 2014 - 01:31 PM

You are unable to open your PC case because of warranty stickers? If so, then you have to document, and make hard copies of logs.

 

1. When CHKDSK successfully completes a scan, it does NOT produce a log as lengthy as the one you posted. That log clearly shows records in clusters as cross-linked (basically this means the HDD is trying to look in 2 places [or more] for the data you've requested). This is not a good thing,,, that alone can cause the PC to lock up. This indicates to me a failing HDD.

 

2. The BSOD fault is blamed on the driver "VIDEOPRT.SYS", however this driver is probably not the actual cause (see here... http://www.solvusoft.com/en/files/bsod-blue-screen-error/sys/windows/microsoft/developer-network/videoprt-sys/ ). That's because videoprt.sys driver is often not the actual problem... it's another driver. When you get BSODs, write down and do screenshots of the faults... create the documentation you need!

 

So, it appears to me your new system has TWO problems; a failing HDD, and funky drivers causing BSODs. While  two faults appearing simultaneously is not impossible, it makes me suspect wonky RAM. But since you can't open the PC case, we have to try other means.

 

I suggest we focus on the CHKDSK log. Cross-linked records are not a good thing. If you can duplicate (and PRINT OUT) this CHKDSK log a couple of times, I believe this would be cause for HP to RMA your machine for a HDD replacement.

Hope this helps.



#5 DrSatanDracula

DrSatanDracula
  • Topic Starter

  • Members
  • 72 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York City
  • Local time:08:36 AM

Posted 16 October 2014 - 12:02 AM

Thank you very much for your help.

 

HP is very, very whiny about what they allow you to do whilst keeping warranties and all that. So I appreciate the help here.

 

Okay. So I should essentially show them the chkdisk log which implies a failing HDD? If I run chkdisk again, it is likely not to find the same faults. So at this point, I should more or less just send them the chkdisk log and say "hey, this is clearly indicative of many of my problems, which have not been resolved after the chkdisk"?

 

I'll be sure to back up these logs on paper and a flashdrive so I have access to them if this computer goes completely kaput.


Edited by hamluis, 16 October 2014 - 10:25 AM.
Removed unnecessary quotebox - Hamluis.


#6 DrSatanDracula

DrSatanDracula
  • Topic Starter

  • Members
  • 72 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York City
  • Local time:08:36 AM

Posted 27 October 2014 - 05:09 AM

Well, ain't that crappy:

 

It appears this problem is starting up again. I just had another freeze-up. I had thought the chkdisk had actually fixed ht eproblem, as my computer did not freeze since the last post I made here.

 

I am going to contact HP about this now as clearly this problem perists.

 

Is there a way to access the information of what causes a non-BSOD freeze up?



#7 DrSatanDracula

DrSatanDracula
  • Topic Starter

  • Members
  • 72 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York City
  • Local time:08:36 AM

Posted 28 October 2014 - 09:21 PM

Further update:

 

Now Checkdisk is running automatically again on start-up. Apparently ANOTHER consistency error has been found.

 

Hopefully HP won't keep blocking my attempts to get this resolved.



#8 hamluis

hamluis

    Moderator


  • Moderator
  • 54,865 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:36 AM

Posted 29 October 2014 - 06:19 PM

You should address the HD situation first...a bad hard drive is capable of screwing up any file (including Windows or the partition structure) that might rest upon such.  Do NOT run chkdsk /r again.

 

Run the long diagnostic test, please...tell us whether drive passes or fails.  Read instructions before proceeding.

 

Guide, SeaTools For DOS - http://www.seagate.com/support/seatools/SeaToolsDOSguide.pdf

 

SeaTools for DOS Download - http://www.seagate.com/support/internal-hard-drives/consumer-electronics/ld25-series/seatools-dos-master/

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users