Windows 7 BSOD and constant freezing

Toggle sidebar Toggle sidebar
S

skilo

Reputable
Jun 26, 2014
10
0
4,510
So i got an older desktop PC for free the other day, It's a Compaq Presario SR5510F, It came with windows Vista installed but i erased vista and install windows 7 ultimate x64.

Ever since i have been having constant freezing and sometimes BSOD, It's always the same BSOD error everytime.

I ran CHKDSK and it found no problems, I ran sfc and it found no problems there either.

My computers specs are:
CPU: AMD Athlon x64 dual core 5000+ 2.60GHZ
RAM: 2GB DDR2
OS: Windows 7 Ultimate x64

Any idea what it could be?

Here is the crash dump:

==================================================
Dump File : 062614-22604-01.dmp
Crash Time : 6/26/2014 12:57:17 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000061
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`009ea180
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062614-22604-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 283,024
Dump File Time : 6/26/2014 1:03:24 PM
==================================================

 
Sort by date Sort by votes
Hmm it looks like a driver problem
What components do you have?
Try booting to safe mode

This may help you,give it a shot. Link:http://www.tomshardware.co.uk/answers/id-1982448/ntoskrnl-exe-driver-bsod.html

And nickvalle is right, if your RAM is under 2 GB It will lag and be unstable
 
Upvote 0 Downvote


Ok i managed to boot into the computer in safe mode, I played around for a few minutes and tried to play back the windows sample video in media player and boom! BSOD, This time it looks like a different error than before though.

==================================================
Dump File : 062614-17331-01.dmp
Crash Time : 6/26/2014 3:17:46 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041201
Parameter 2 : fffff680`0000f500
Parameter 3 : 9b900000`38edf867
Parameter 4 : fffffa80`033fcec0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062614-17331-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 271,456
Dump File Time : 6/26/2014 3:19:15 PM
==================================================



 
Upvote 0 Downvote
Can you upload some of the minidump files for us to run through a debugger? Before I start spouting ideas. Does it have onboard video? are you using another video card? check the heatsink on the cpu see if its blazing hot when it crashes, before this, was vista crashing? it may be a hdd issue as well. but the hanging on POST is the big indicator that this is not software at all.
 
Upvote 0 Downvote


Here are the dump files: Dump Files Here/

I also unplugged the computer and opened it up to check if anything was loose but everything looked ok to me, The thing looks absolutely brand new on the inside.

It does have trouble booting though, It often gets hung on the bios screen but if you turn it off and on a few times it finally boots into windows.
 
Upvote 0 Downvote
that's indicative of a bad overclock, overheating or possible bad ram. Since it is a Compaq, its not overclocking. It absolutely is a hardware issue. And we can mostly rule out harddrive. So, does it have F2 diagnostics? most Compaq computers have HP diags. So see if those run. also, if you can get into the bios, restore defaults, save and exit. If HP diags pass or are not available, download Memtest and run that for a good few hours/ overnight.
 
Upvote 0 Downvote


Well it's been about 2 hours now, I am on test #8 of memtest and it still has not found any memory errors.

I booted into a linux live cd and the same freezing happens so that should mean that it's definetly not driver related, So if the memory is ok and HD is ok i guess that only leaves the CPU and motherboard? Do you see anything in those dumps that might give me a clue of what to look for?

 
Upvote 0 Downvote
last crash was like the first. Overall, I think you are running on a custom hardware that requires a custom graphics driver. You might also check your BIOS for corruption one of the dumps indicated that the graphics hardware was disabled. (if the info was correct, it may not be)
-------------

first guess is that you are running a generic version of windows on a system that requires a custom drivers from HP.
last BIOS update was 2008.

let me look at the two other crashes real quick and see if there is something more useful

the second crash, looks like the graphics driver/hardware did not get a hardware interrupt. I would be looking to see if the driver is incorrect or that the hardware requires a custom driver, based on the age, it might require a 32 bit version of windows and a 32 bit custom version of the driver.
you might also want to look at the versions of the loaded driver
it kind of looked like you had one from 2008 and another 2013

fffff880`0f0c9000 fffff880`0fdd3000 nvlddmkm \SystemRoot\system32\DRIVERS\nvlddmkm.sys Wed Jan 30 23:45:04 2013 (510A2100)
fffff880`04197000 fffff880`041fad80 nvm62x64 \SystemRoot\system32\DRIVERS\nvm62x64.sys Fri Oct 17 14:01:06 2008 (48F8FD12)

i did not see the framebuf.dll driver in this dump though..

--------------------

the first crash was in memory mangement with a undocumented subtype (41201)
you have one driver that I would look at that was loaded
framebuf.dll

Machine info:

Vendor Phoenix Technologies, LTD
BIOS Version 5.25
BIOS Starting Address Segment e000
BIOS Release Date 02/29/2008
Manufacturer Compaq-Presario
Product Name KQ513AA-ABA SR5510F
SKUNumber KQ513AA#ABA
Family 103C_53316J
Product Iris8
Version 1.0
Manufacturer Hewlett-Packard
Processor ID b20f0600fffb8b17
Processor Version AMD Athlon(tm) 64 X2 Dual Core Processor 5000+
Processor Voltage 8dh - 1.3V
External Clock 201MHz
Max Speed 3000MHz
Current Speed 2613MHz


02: Type Video [disabled]
02: Description
03: Type Ethernet [disabled]
03: Description
04: Type Sound [disabled]

 
Upvote 0 Downvote
Reset the bios to factory defaults. reseat the ram, boot with one stick at a time, disconnect every thing but the hdd. and the power cables and such (obviously). and pray... freezing in a live cd means its most likely not a hdd issue. its gotta be heat or a failing MOBO. at this point its just process of elimination. you didn't mention, is the processor cool to touch after dying? is the fan spinning (I know it sounds obvious) but if you never look inside wile its running, you wouldn't know for sure.
 
Upvote 0 Downvote


we have established that this is not a OS compatibility issue. he experiences lockups on POST and while in a Linux live boot.
 
Upvote 0 Downvote
it should just be grey thermal paste, a thick heat conductive, kind of grease. (should not conduct electricity )
generally, you don't want to remove a CPU unless you have new paste to put on. sometimes on old system the paste dries out and the CPU overheats but you tend not to get this bugcheck.



 
Upvote 0 Downvote


Well the CPU seems to be stuck to the heatsink, Maybe i should just stick it back in and try to install windows 7 32bit?

I'm not going to install Vista on this machine, I will trash it before i use Vista.

 
Upvote 0 Downvote
i would try a 32 bit windows but if you have the lockups during POST and your BIOS is not corrupted then you have a hardware problem that windows will just hit.

sometimes, a BIOS gets corrupted and you have to toggle a hardware feature off then on to get it to rebuild its database of hardware interrupts that it sends to the operating system.



 
Upvote 0 Downvote
You are on treacherous ground now man. be very careful with those pins, you may want to get some new paste. scrape off the old stuff! its possible if the mobo or cpu is a little crazy, 32 vs 64 wont matter. don't forget to try the steps I mentioned. but its been fun troubleshooting. let us know how it ends
 
Upvote 0 Downvote


I have decided that it's just not worth the trouble or the money to fix this thing, I am now in the process of stripping it down for parts, I will probably be selling the sata cables, The HDD, The flatscreen monitor, and the RAM sticks on ebay.

Thanks for your suggestions guys.

 
Upvote 0 Downvote


There will be a funeral service for it wed 25th (Garbage day), If any of the forum member would like to PM me their condolences that will be fine.

Presario SR5510F, I know i only knew you for roughly 24 hours, But i want you to know that the guys on tomshardware forums did everything they could to save you, But alas your creator had designed you with planned obsolescence in mind.

And now a moment of silence for the Presario model SR5510F...
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom