[ElizabethMeek]

http://forums.techguy.org/windows-vi...ol_caller.html

The above link is the first set of issues I was having. (Sorry the thread was expired so I couldn't post on it.)

The most recent BSOD are happening when I first turn the computer on. Some times before I have a chance to enter my password to log onto Windows.

Here are the minidump files:

[Rollin' Rog]

I've looked at the ones for this month, and while there are a number of different Stop errors reported, 2 out of the 4 report either "memory corruption" or "hardware" failure.

So I would start by testing the Ram.

Vista has a basic built-in ram tester which you can run from the command mdsched.exe

When you reboot to the scanner, press F1 for Advanced Options and run the extended tests.

[ElizabethMeek]

I ran the extended memory test though it did not find any problems... If I am reading the report correctly.

I attached a copy of the report and a summary.

Thank you for taking a look at this issue... again.

Elizabeth

[rainforest123]

For what length of time did you run Vista's mem diag?

If the computer has a floppy disk drive, run memtest86 from floppy disk.

www.memtest86.com

If only an optical disk, run memtest86 from that.

Hopefully, someone one can tell us how to fun mt86, for 8+ hrs from an optical disk. I haven't figured it out, yet.

How often do the BSODs occur?

RF123

[ElizabethMeek]

Sorry for the delay in reply.

rainforest:
I do not understand your first question. I ran vista's mem diag until it was finished, the process took about 3 hours.

I do not have a floppy drive.

I went to the memtest86 site.... but they only wanted to sell me software?

And the BSOD frequency is random. Somedays not at all, others when I first turn on the computer, and days like today... two BSOD and the computer froze before I could get to this site.

The thing I find odd is: I'm not doing anything different to change the amount of BSOD. Which is why it seems 'random' to me.

If you need anymore information, please use the link. That has my system's information and the tests I have run already.

Thank you for looking at the issue.

Elizabeth

[Rollin' Rog]

Since your first BSOD for this month pointed at a "mouseclass" driver and you have >> pmxmouse.sys which is for a "primax" mouse -- I would start by just uninstalling that driver and NOT reinstalling it. MS has its own drivers and does not really need anything else.

See how it goes that way.

I would also try updating the Display drivers since they can always be a factor.

And I'm not personally confident with PC Tools reliability, but let's leave that for later

For what it's worth the current address for Memtest86 is actually http://www.memtest.org

but I don't see any reason to run it now.

[ElizabethMeek]

Okay, that mouse driver is uninstalled and the display drivers are updated.

I'll keep my fingers crossed waiting for the next BSOD.

Thank you,

Elizabeth

[rainforest123]

RR:
Thanks for the correction.

EM:
Follow RR's advice.

When I have run Vista Mem Diag, it will not auto terminate; runs until I tell it to cease.

unsubscribed

RF123

[ElizabethMeek]

Yesterday I had another BSOD. The "Not_Less_or_equal_to" one. After the computer shut down, I tried to launch it but the launch failed. Windows sugested I run Launch repair. I did so and it sugested I return to the last restore point, which I did. The computer ran fine for the remainder of the evening.

The next day (today) I turned on the computer, launched window's explorer to check my e-mail. My computer shut itself down. No blue screen, it didn't freeze either. The screen went black and the moniter said 'no signal' as if the computer was turned off. When it launched windows I started in safe mode to type out this message.

I seem to be going backwards.

Please let me know if there is anything else I can do to get this fixed.
Elizabeth

[Rollin' Rog]

A cold shutdown like that (and no reboot) is usually initiated by the BIOS in response to overheating or possibly power supply issues.

If it rebooted -- then memory is still suspect, but power supply glitches can also cause it.

You might give Speedfan a go at monitoring temps and look for a rise of more than 30 - 35 c from a completely cold boot, although if you shut down almost immediately after a boot, that makes heat less likely and a motherboard or power supply issue more likely.

There are also voltage monitors with speedfan but they are usually not reliable.

http://www.majorgeeks.com/download337.html

Be advised if this is a Dell desktop -- it may not have a temperature sensor on the motherboard except for the hard drive.

By the way, is the computer under warranty? If so I would start talking to their support about a possible hardware issue with the motherboard or power supply.

[ElizabethMeek]

Okay.. I got speedfan yesterday then left my computer off for 20 hours before turning it on. After another cold shutdown today... I launched speedfan and here is the read out.

I'm not sure what it means.... but the burning inferno icons can not be good.

Sad thing is, this was a new build from Dell with their new liquid cooling system.
I would hate to think this expensive cooling system is doing so poorly, but I wouldn't be shocked.

[Rollin' Rog]

Sheesh, if Speedfan is right then those core temps are high, and your 12 volt reading is 3 volts low.

While I more or less trust Speedfan on accurate temperature readings, I do not always trust it to know what is critical.

And I do not trust its voltage readings at all

A GPU (graphics processor) reading of 78 c is almost certainly higher than it should be except in the most extreme gaming, and even then is borderline.

I'm not so sure about the processor readings, but they do seem high, and if this is the correct data for it, too high by far:

Core 2 Extreme QX9650
(quad 3.0GHz - 2x6MB) ?V
(0.85V~1.3625V) 1.45V 125A 130W 64.5° C

http://users.erols.com/chare/elec.htm