Win 7 64 Bit BSOD STOP: 0x0000007f

[sonicviz]

Hello,
I'm running a Win 7 ultimate 64 Bit upgrade from XP 32 bit.
I upgraded the hardware and associated bios/drivers etc before doing so, it all ran fine under XP.

Hardware upgrades:
Mobo P5B keep, bios to latest to support Q9650
PSU keep
CPU E6400->Q9650
GPU 7800GT -> 9600GT
Ram 3GB -> 8gb all same 2GB sticks
New 500GB system drive

XP was solid under new hardware

I've been having these consistantly inconsistant BSOD's (25+ since 13/3/2010, see attached minidump for latest).

They *usually* happen (~70%) when watching a youtube or associated video, but also on other operations like opening a new app etc.

I have latest bios, drivers etc for motherboard/hardware, but so far the bluescreenreview does not give me any specific info apart from:
0x0000007f ntoskrnl.exe+70600 Parm1 x00000008 (appears to be double fault = hardware related)

System is not overclocked

Things I have tried:
. Standardising all memory to same batch/manufacturer
. memchecks, also using M$ util - pass
. sfc /scannow - verified 100%, no violations
. swapped memory around
. checked board seatings

I suspect it could be an nvidia issue, but not sure. I can go and get another video card if I can accurately pinpoint to that, but who's to say the new VC won't have random 64 bit issues?

I use this also for live audio production, stable as a rock until the random BSOD, and I also use it for business - so this random BSOD gremlin is a real pitfa at the moment as it can potentially cause me a lot of grief at the wrong moment.

Any help much appreciated!

ty.

 

[sonicviz]

Addendum:
I came across this post "if you are using more than one 1.8V memory and running a x64 OS you should use a BIOS memory voltage setting of 2.1V and not 1.8V." Trouble with Geforce GTX 285 on windows 7 64 bit - NVIDIA Forums
so may give this a shot as well, till I hear back from some input here.

ty!

 

[Lordbob75]

Be careful when changing the voltage from your BIOS. You might burn something (not you). Check your RAM to make sure they should run at that voltage (or your video card if thats what you meant).

A bit of research shows that this stop code (7F) is usually caused by RAM and voltages. Make sure your RAM is running at the correct voltage for both the RAM and the mobo. Same for your video card.
Also, remove stick of RAM one at a time and check for stability. If the system crashes with just 1 or more sticks, then they very well might be bad.

~Lordbob

 

[sonicviz]

The Ram is brand new, no BSOD's under Win XP 32 sp3 before upgrade so why would it suddenly start to bork on the win 7 64 bit?

Which is why I suspect hardware driver related issues...hard to know, so little actual info they give you.

Ram is standard JEDEC 1.8v +/- .1 , but has an outer limit of 2.4v it looks like.
http://www.elixir-memory.com/products/file/Elixir-DDR2-UDIMM-1G-D-R12.PDF and has been running in Bios auto mode which I assume is defaulting to 1.8v.

I bumped it up to 1.9v, running fine atm monitoring all the temps, they are higher but not overly. Maybe I'll lock it down to 1.8v and see what transpires.

It looks like M$ leans toward memory issues General causes of "STOP 0x0000007F" errors but Run a system diagnostic utility supplied by your hardware manufacturer. lists a much wider range of possible causes.





This problem can occur when any of these issues occur:

• Defective memory, memory incorrectly installed or mismatched memory sticks
• BIOS having the wrong settings and/or overclocking the processor (CPU) or memory
• Stopped or slow fans causing overheating
• Defective or buggy hardware or video drivers
• Defective Processor (CPU)

 

[squall leonhart]

The Ram is brand new, no BSOD's under Win XP 32 sp3 before upgrade so why would it suddenly start to bork on the win 7 64 bit?

because windows 7 is a different beast.

 

[sonicviz]

The Ram is brand new, no BSOD's under Win XP 32 sp3 before upgrade so why would it suddenly start to bork on the win 7 64 bit?

because windows 7 is a different beast.

I understand memory is managed differently under different OS's, but I don't understand what you mean technically hardware wise. If the RAM is in spec with the motherboard and BIOS support (and JEDEC standards on top of that) how can the OS need specific RAM.

Do you have some links to explain what you mean further?

 

[squall leonhart]

Motherboards themselves can provide unstable or.. slightly off voltages to components making the entire system unstable unless you apply a little more then usual.

heck my rampage II gene provides more voltage then it should at 1.65, but less then it should at 1.64. tricky beasts they are.

 

[sonicviz]

Motherboards themselves can provide unstable or.. slightly off voltages to components making the entire system unstable unless you apply a little more then usual.

heck my rampage II gene provides more voltage then it should at 1.65, but less then it should at 1.64. tricky beasts they are.

But that should be consistant despite what OS is running should'nt it? (unless you are talking about possible mobo power flucuations due to specific OS loads, but I don't know much about that)

I've dropped my Bios mem voltage back to 1.8V and will see how that goes. 1.9V seemed stable for 12 hours, but temps are higher. It's been anywhere from a couple of hours to a couple of days between BSOD's sometimes so I'll try to load it up and force the issue.
If it is mem voltage related maybe it was the auto setting in the bios mem voltage spiking it into BSOD? Not much else to try at the moment....

 

[squall leonhart]

That would be true in a perfect world, Vista and 7 both use hardware alot harder then XP used to, meaning if any component is out of spec, it can bring it crashing down, while XP wouldn't bsod or VPU recover at all.

Its hard to explain really, but it just is how it is. Many of the vista early adopters came against this when they were using auto detected values for their memory or cpu, rather than configuring them manually.

 

[sonicviz]

kk, ty. I'll report back my results of memory voltage tweaking.