Long running BSOD Win 7 64bit

ravenscar42

Honorable
Aug 31, 2013
2
0
10,510
Hi guys,

I've come to you all as I'm all out of ideas for my problem. I've read over this forum trying to find the answer and tried to apply what I've found, but to no avail. So I come to you now in the hope that your collective knowledge will save my sanity. About a month back I started getting BSOD's. Now my compute had been shipped in a house move and I thought it might have got a bit of a knock. I did all the tests of the hardware I could, had to buy a new power pack (corsair cx600m). Since then I've got the odd BSOD and I figured (from what I'd read) that it was to do with the memory. I tested both sticks (cosair 2gb each, bought as a pair) and memtest86 did about 10 sweeps each with no problems. I did notice that the DIMM slots configuration was behaving badly, throwing up the red memtest light in certain configurations. At the moment I've got them in the two slots closest to the processor (one in black, one in blue), putting them both in blue or both in black just didn't seem to work.

Well I still got BSOD's so I did a full reinstall of windows 7 64. Now, a couple of days down the line I get another BSOD. I have, today, just installed a new GPU and updated its drivers, but after a while gaming I come out, start watching a media file and boom, down it goes. I tried running verifier after following the advice of another forum which proceeded to make windows blue screen before even fully loading, so am I looking at a driver rather than hardware issue?

I really don't know and I've run out of places to know where to look. I'm not that adept at the technical stuff, but if it's laid out step by step can follow it all through, but nothing I've done seems to stop it. I've got the latest minidump (which I checked with blue screen viewer) and it says it's:

083013-18907-01.dmp 8/30/2013 11:34:35 PM DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL 0x000000d5 fffff980`02ae6e40 00000000`00000000 fffff880`045a31aa 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75c00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533) x64 ntoskrnl.exe+75c00 C:\Windows\Minidump\083013-18907-01.dmp 4 15 7601 269,848 8/30/2013 11:53:33 PM

But I'm lead to believe that that's pretty generic stuff. here's the link to the minidump in question: http://www.mediafire.com/download/2okep1u1m3v28av/083013-23571-01.dmp

My setup is:

AMD Phemom II X4 955
4GB DDR3 Corsair RAM
M4A89GTD PRO
Radeon HD 7700

In advance, I really appreciate the time you give to help me with this and I hope we can crack it.
 
Solution
Sound like the RAMs is placed in the wrong slots. Whatever color slot is closest to the processor, let's say it is black, you need to place the RAM (one in black, one in black). If the color slot closest to the processor is blue, then you need to place (one in blue, one in blue).

Hope this fixes the issue.

blackcell989

Distinguished
Jun 9, 2013
97
0
18,660
Sound like the RAMs is placed in the wrong slots. Whatever color slot is closest to the processor, let's say it is black, you need to place the RAM (one in black, one in black). If the color slot closest to the processor is blue, then you need to place (one in blue, one in blue).

Hope this fixes the issue.
 
Solution

ravenscar42

Honorable
Aug 31, 2013
2
0
10,510
Heya, thanks for getting back to me, unfortunately I still get the crashes when it's in the all blue or all black slots.
Could the motherboard be dying or is this more likely a driver issue? If so, how can I isolate which one it is?

Thanks again
 

TRENDING THREADS