Vista problems

Soldato
Joined
2 Jun 2007
Posts
6,839
Location
Mornington Crescent
Right, I made a couple of threads a while ago, then forgot about them (Sorry!), but now I'm just rounding all my problems up in one thread, for sorting out.

The main problem is freezing. Sometimes, my computer just freezes. I've noticed this happening at three specific times. Either on the vista login screen, usually if its been left there for a few minutes. If not there, then as its logging on, near the end when things like MSN and AIM are signing on, getting all their popups coming up with email notifications. And finally, its happened a couple of times on closing utorrent.
When it freezes, its just completely stopped. Keyboard doesn't do anything, caps lock and all that doesn't turn on the lights, No mouse movement, and leaving it doesn't do anything, it requires a restart. I've tried updating my wireless drivers, with no luck, and since its happened also updated my graphics drivers. Still nothing. Last night, I tried to get memtest working, but couldn't get it on a bootable DVD for whatever reason, so settled for the vista memory diagnostic thing. Set it to run the full memory test 10 times overnight, it managed 7 passes by the morning (about 10 hours of testing) where I had to end it, and it hadn't found any errors.


Secondly, when I shut my PC down, it sometimes just sits on the 'shutting down' screen not doing anything. If I leave it like this for a while, it bluescreens, though I usually just turn it off with the power button before this. If it helps, I can let it happen again next time to have a look at the crash dump.


An unrelated problem I have has only happened twice, a few weeks apart from each time. When logging in, I put the password, the screens go black, but the desktop doesn't come up. However, its not frozen, I can bring up the task manager and it shows the processes running, not the full set but still a lot. Logging out using the task manager and logging back in doesn't sort this, it requires a full reboot. No idea what causes this either, and it reboots into windows fine after that.

Hope its ok having it all as one thread, but I'm not sure what could cause any of these, and I'd rather avoid having to reinstall vista. Temperatures are all fine, idle around 35, up to 50 under full stress, and there's no problems when gaming, so I don't think that's a problem.

Specs:
[email protected]
4Gb ram
P5b mobo
HD4850 1Gb
Vista x64
Dual monitors.
 
Right, installed Windows 7 RC1, spend the morning installing all the drivers, getting things working... and it just froze on me again. Exactly the same as before, everything just stopped. No HDD activity, no response.

Because of this, I'm guessing its some kind of hardware problem?
 
I'd say so yeah.

Maybe up the CPU voltage one value. I'd also make sure your RAM has the correct timings set in the BIOS, as well as the correct amount of rated voltage. Also, make sure the RAM isn't past its rated speed.

Failing that, up the Northbridge voltage one value.
 
Thanks for the reply. I took a couple of pics of my bios, which are attached, that showed how it was. I've now put the vcore up to 1.400V, and with a bit of luck its as simple as that.

It all looks ok, doesn't it?





Also, I looked through and couldn't see anything to do with the northbridge voltage. Should I have any of the settings in the pic changed to non-auto?

Thanks!
 
Try locking the PCI-E frequency to 100. (on auto it can overclock with FSB, much like memory will)

Failing that, run memtest and check to see if the memory passes. That way, you'll know that it cant be the memory thats at fault, as long the the timings, speed (800mhz im guessing?) and voltage are set to the recommeded values.

Then try putting it back to stock and see if it is the overclock thats the cause. Should it still fail, i'd then try a BIOS update to the latest version.
 
Try locking the PCI-E frequency to 100. (on auto it can overclock with FSB, much like memory will)

Failing that, run memtest and check to see if the memory passes. That way, you'll know that it cant be the memory thats at fault, as long the the timings, speed (800mhz im guessing?) and voltage are set to the recommeded values.

Then try putting it back to stock and see if it is the overclock thats the cause. Should it still fail, i'd then try a BIOS update to the latest version.

Thanks for the replies, I'll try the PCI-E frequency now.
As for memtest, I ran the vista memory diagnostic tool overnight (10 hours) and it completed 7 passes without finding any errors, so I'm pretty sure the Ram's ok.
This is the ram I have, 4x1Gb sticks of it, and if I remember, I was getting bluescreens running it at anything less than 2.1V, which is the usual voltage for running 4 sticks, if I remember correctly.

As for BIOS, I'm pretty sure I'm running the latest version, but I'll check the next time I reboot. Cheers.
 
Sorry for the silence, not had access to my computer recently. Anyway, I've removed the overclock, no problems yet (Just over 24 hours). However, came back to it today, and it was on the login screen. Logging in, it apparently bluescreened.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8004889570
BCP3: FFFFFA80079E7050
BCP4: FFFFFA8004FCEBD0
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini051309-01.dmp
C:\Users\Iviv\AppData\Local\Temp\WER-20043928-0.sysdata.xml
C:\Users\Iviv\AppData\Local\Temp\WER8B44.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Put the dmp file into WinDbg, and it says:

Probably caused by : ntoskrnl.exe ( nt+54650 )

Which doesn't sound very good. Also, for whatever reason ESET firewall didn't want to startup, and its telling me to restart to start it again, so I'm going to try that now.
 
I had a similar problem with my computer randomly locking up which was down to the LAN card interfering with the SATA controller.

I'd also try diababling or removing varous non-essential pieces of hardware, like removing a few sticks of RAM, just to see if it has any effect.

Could be worth trying if even just to eliminate possible sources of the problem.
 
It just happened again, with the CPU at stock settings, when I opened utorrent.

I have a feeling its the wireless card, since it often freezes when I open or exit uTorrent. Belkin haven't even released vista-64 drivers for my card, so I've had to be running chipset drivers instead.
The only problem I have is that my computers too far away from the router to just use an ethernet cable to test if the problem's with the wireless card.

Would it be possible to somehow use my laptop to connect to the network wirelessly, then use an ethernet cable from the laptop to the PC? Or would I need a crossover cable for that?
 
Came back to a bluescreen again:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800488A4F0
BCP3: FFFFFA8006CC8050
BCP4: FFFFFA8006C87010
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini051409-02.dmp
C:\Users\Iviv\AppData\Local\Temp\WER-1905786-0.sysdata.xml
C:\Users\Iviv\AppData\Local\Temp\WER90BA.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

The very strange thing is, looking in my minidump folder, there's two dumps for today! Once created at 15:00 and one at 16:00. Both list ntoskrnl.exe as the cause again.

I'm not sure I've got any crossover cables kicking around, how would I know one just by looking?

Thanks!
 
Back
Top Bottom