• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Memory Dump Caused BSOD

P

PhishingJimi

n00b
Joined
Aug 10, 2004
Messages
53
Any help on this topic would be much appreciated.

I've been having a blue screen issue with the following code:

0x0000007f (0x0000000A, 0x00000000, 0x00000000, 0x00000000)

I found this link: http://support.microsoft.com/kb/137539
but it does not have specific information for my error.

Another potential symptom i've noticed is that the task manager shows only 3 gigs of RAM, though I have 4 installed and everything else (including bios and CPUID) show me having 4 gigs.

Please help if you have any advice.

-Thanks
 
what OS? 32-bit XP will not display the full 4 gigs.
run a memtest?

The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are:
Low-level hardware corruption, such as corrupt memory (RAM)
Mismatched memory modules
A malfunctioning motherboard
Click to expand...
 
Memory Dump Caused BSOD
Click to expand...
It may help you to know that the memory dump is part of the BSOD process, the memory dump doesnt cause a BSOD.

If you have a 32bit OS, everything in the system has to fit into 4GB absolute max.
So your gfx card memory, any remapped BIOSs, memory on soundcards etc all take up part of the 4GB space.
Its normal to have about 3GB ram free when 4GB is installed on a 32bit OS.

As the post above suggests, start with stability tests, test each component individually.
ie ram, cpu, gfx card
Check for anything getting hot, that includes any heatsinks on the motherboard.
If things are getting hot, it may not be the cause of a failure but its wise to take steps to reduce heat. To see if heat is a cause of the crashes, blow a housefan at the PCs insides and see if things improve.
 
OS is Vista 32-bit Home Premium. Ran both the Windows memtest and one pass of Memtest86, will do more passes tonight. Also, reset the CPU back to stock speed.

Is it possible the mobo chipset could be overheating?
 
PhishingJimi said:
OS is Vista 32-bit Home Premium. Ran both the Windows memtest and one pass of Memtest86, will do more passes tonight. Also, reset the CPU back to stock speed.

Is it possible the mobo chipset could be overheating?
Click to expand...

You should have suspected the overclock before posting here.
Does it still BSOD now it isnt overclocked?

Heat always needs to be considered as it is a major limiting factor for stability.
If you want to know if the motherboard chipset is overheating then check it.

Leave memory testing overnight.
 
I stepped it back to 10x 333 now, it hasn't bsod'ed in a while (the kiss of death). But I havent really tried any hard gaming. will run memtest overnight to check results.

Will get back to you guys in the morning.

thanks for the responses
 
ended up staying up a bit longer, you mean the .dmp files kipper?

another side note, when running Intel Burn test, it runs fine for each setting except maximum stress (100% memory load) in which case it fails immediately. The other lesser memory-intensive options run fine for however long.
 
Looks like the overclock became unstable.
This can happen if pushing too hard (starts producing more heat due to heat related damage), if the power supply is starting to have trouble or if cooling/ambient temps change for the worse.
 
Stepping back the multiplier from 11x to 10x seems to have solved the issue. Didn't forsee this happening though, since my core temps rarely hit 50 degrees C even under load. Just thought that was a little weird
 
PhishingJimi said:
Ran 12 passes of memtest while I was at work, no errors. Guess bad RAM is out of the question.
Click to expand...


don't be on it.
Unless all tests are completed you cannot say the RAM is ok.

I had an issue with my system that while I was install Gentoo it would always segfault the kernel at roughly the same point during compiling Boost - very big C++ library, can easily eat > 1Gig of RAM

Turns out it was my RAM being undervolted and at higher RAM usage/RAM addresses it couldn't retain the data.
I ran a couple of memtests and it looked ok - however I kicked it off and buggered off down the shops for an hour or so only to come back to find errors :(
upped ram from default 1v8 to recomended 2v1 and \o/
 
PhishingJimi said:
Stepping back the multiplier from 11x to 10x seems to have solved the issue. Didn't forsee this happening though, since my core temps rarely hit 50 degrees C even under load. Just thought that was a little weird
Click to expand...

Make sure the temps are definitely in that ballpark as they are quite low.
If so, just raise the voltage a little higher to get stable.
Have you overclocked before?
 
yea, i had my e5200 overclocked to 3.3 for about 6 months until I got this chip, then I had my e7500 overclocked to 3.6 for about 3 weeks before this whole fiasco started.

Right now CPU-ID is showing 1.304 core V with my overclock being stepped back to 3.3 for the e7500. So far it's been stable for 72 hrs, which is significantly better than anything for a week prior to this recent clean period.
 
You must log in or register to reply here.
Back
Top