I cannot pinpoint the source of my BSODs

I just got a BSOD "Memory Management"

And then my computer BSOD on start up... and then it would not even turn on again, it just beeped repeatedly. I turned it it off, waited an hour and now it turned on....

edit: Yes i mean i can get on to windows and everything at the moment

please help!

I do not understand your previous post. Are you able to boot into Windows?

Edit: I understand that your memory was corrupted, and you were unable to start Windows or get to the BIOS. What I do not understand is the current state of your machine.

blarp said:

I forgot to say, Ive also had a couple of more blue screens, the last one said "NTFS.sys"

edit: is this NTFS.sys significant? is it a clue to whats causing my BSODs? I googled NTFS and found alot of stuff but im not sure what to do....

This typically indicates a hard drive issue, but it can also be related to other hardware issues. Run a scandisk, and honestly, I would do as suggested by yowanvista https://www.sevenforums.com/crashes-d...ml#post1676122 and run a memtest as well. Just because your memory is brand new does not mean that it is working properly. You may have a bad slot in your motherboard, or you may have been sold faulty RAM.

Yes I am able to get into windows and bios

I also did a system file check with cmd, nothing found. Im not a computer expert but, with my old ram sometimes the only way i could use my computer without BSODING was by swtiching their slots they were in. My common sense tells me there must be a problem with the slots, what do you think?

I was reading somewhere about a possible fix... slightly increasing voltage to ram, what do you think?

blarp said:

Yes I am able to get into windows and bios

Okay. Next time your computer crashes and has that reaction when started, do the following:

1. Shut down the computer
2. Unplug the computer AC adapter from the wall and then unplug the battery if it is a laptop
3. Hold down the power button for 30 seconds
4. Plug the battery back in if it is a laptop then plug the AC adapter into the wall
5. Start your computer.

The above will clear all temporary memory in the computer and clear and reset the software connections between the BIOS and hardware. This will fix most memory corruptions and most component malfunctions.

blarp said:

Yes I am able to get into windows and bios

I also did a system file check with cmd, nothing found. Im not a computer expert but, with my old ram sometimes the only way i could use my computer without BSODING was by swtiching their slots they were in. My common sense tells me there must be a problem with the slots, what do you think?

I was reading somewhere about a possible fix... slightly increasing voltage to ram, what do you think?

Do a rigorous ramtest. Try different memory configurations (use one card at a time and check different slots) and run the boot version of RAM - Test with Memtest86+ for at least five passes. Once you find a memory card that passes the test, you will know that card and that slot are good. Test the other slots with the good card to find any bad slots. Then use the good slots to test if any of the remaining cards are bad.


Edit: To determine whether you need to increase the voltage to your RAM, you need to check your current voltage supplied by the BIOS and find what voltage your RAM requires. I have also read what you have read, but as I understand it, it only applies if your motherboard is supplying slightly less than what your RAM requires.

So I have a few updates:

Memtest passed 5 times with 0 errors, it took 10 hours.

Yesterday I had some interesting BSODs, I noted that one of them was "A thread tried to release a resource it did not own"

After my recent BSODs I thought it would be worth checking my memory.dmp with windbg again. And this time the results produced something different then before.

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmInterface+2c8f0 )

What could this mean? well... my windbg does keep telling me its using wrong symbols..... (even though i downloaded a big package of symbols to c\symbols, pointed the symbol file path to it, but it still says it needs right symbols)

I attached a new jcgriff to supply more info on my bsods...

If new is not a ram problem what could it be?

Please help!

blarp said:

So I have a few updates:

Memtest passed 5 times with 0 errors, it took 10 hours.

Yesterday I had some interesting BSODs, I noted that one of them was "A thread tried to release a resource it did not own"

After my recent BSODs I thought it would be worth checking my memory.dmp with windbg again. And this time the results produced something different then before.

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmInterface+2c8f0 )

What could this mean? well... my windbg does keep telling me its using wrong symbols..... (even though i downloaded a big package of symbols to c\symbols, pointed the symbol file path to it, but it still says it needs right symbols)

I attached a new jcgriff to supply more info on my bsods...

If new is not a ram problem what could it be?

Please help!

dxgmms1.sys is DirectX, suggesting either your DirectX is not up to date, or your display adapter driver is not functioning properly. Update DirectX first. If that does not fix the problem, download and install Phyxion.net - Driver Sweeper to remove your display adapter driver (you can find what it is by Start Menu->Right click My Computer->Manage->Device Manager (from the list on the left)->Display adapter).

Once the driver is removed, find the latest driver for your display adapter either from your computer's vendor (HP, Toshiba, DELL, Sony, etc.) or from the display adapter's manufacturer site.

probably a dumb question, by display adapter you mean graphics card right? my graphics card is listed under display adapter in device manager

and if you do mean graphics card, i recently updated it. I never removed the previous install of the driver with the sweeper before updating it, I guess that is important.

It is an ATI rad 5670 by the way