hard core blue screens, UPDATE 4-25

VooDoo · Post by **VooDoo** » Fri Apr 02, 2004 8:16 am

since i build this computer (VooDoo4) ive been getting these blue screens, and i tryed past vid drivers, im running the current drivers from BF:V cd

i cant get any screen shots, ill try to get some w/my dig camera but i need to get the cord from storage

some of the errors i get are

bad_pool_caller

and it points to a file some times win32k (i think)

i know its not much to go on, any ideas??

me

sethpa · Post by **sethpa** » Fri Apr 02, 2004 8:33 am

What OS? When's it happen? Trying to establish a pattern here, have you tested the memory for problems? If it's a new build with new, untried components, sounds like you have something not right with the hardware. Also, try eliminating items and running as bare as possible, see what is causing the blue screens.

VooDoo · Post by **VooDoo** » Fri Apr 02, 2004 8:44 am

os : xp pro

happending at ramdom, it could happen when its just setting there, looking at the net, playing a game, when ever it want to

everything is on the mobo, (sound, 2 nics) but the vid

me

sethpa · Post by **sethpa** » Fri Apr 02, 2004 10:44 am

Try reseating memory, then if still wacked, different stick. One thing at a time..... If running more than one stick of memory, try one slot only, also, different slots.

Get into the bios, disable, all unnecessary items, serial ports, sound, etc... Good luck..

VooDoo · Post by **VooDoo** » Fri Apr 02, 2004 12:06 pm

its one stick of 2700 (i think)

thanx ill try it

me

rogue · Post by **rogue** » Fri Apr 02, 2004 12:31 pm

Random BSOD's are usually RAM related, so if reseating doesn't work, try upping the DDR voltage to 2.8v in the BIOS.

VooDoo · Post by **VooDoo** » Fri Apr 02, 2004 2:01 pm

d/l the free memtest posted here

i got 16 hits

i took a eraser (sp) to the contacts, reseat it ran the scan again

got the same errors

and its 2100 ddr ram not 2700 as posted befor

i cant try diff ram b/c the ram in my game/file server, on the first pass, 203 errors poped up

Originally posted by rogue
Random BSOD's are usually RAM related, so if reseating doesn't work, try upping the DDR voltage to 2.8v in the BIOS.

what will that do?

me

VooDoo · Post by **VooDoo** » Fri Apr 02, 2004 2:24 pm

i found this

ddr reference voltage in the BIOS i uped it to 2.8

rescaned errors found

me

Executioner · Post by **Executioner** » Fri Apr 02, 2004 3:22 pm

Sure sounds like it's ram related. I had pc2100 in a rig that I built for my father-in-law, and it would always BSD at bootup when going into win2k. So I ordered a new pc2700 stick and it solved the problem.

My son has rdram and his xp pro setup would reboot after a cold start. If he left it on, it would work with no problems. We swapped out one of the sticks with another, and it solved the problem (got lucky to find it with the first stick).

On my spare win2k rig in the garage (a dually), I could not enter into the on board scsi bios as it would lock up the pc. Required a hard reset. Booting into windows worked fine (figure that one out). Finally after some months, the errors began appreaing in win2k with a BSD. I swapped out each stick of ram until I found the one causing the problem, and now I can enter into the SCSI bios without locking up the pc.

That is why I like having spare memory sticks. You just never know.

VooDoo · Post by **VooDoo** » Sat Apr 03, 2004 12:36 pm

does anyone have memory i can buy from them

me

VooDoo · Post by **VooDoo** » Sun Apr 04, 2004 1:55 pm

is there a way to clean the contacts for the memory on the mobo

me

Post by **FlyingPenguin** » Mon Apr 05, 2004 7:57 am

You can clean the contacts on the memory stick (or any card) using a pencil eraser (a clean one!).

However, the way memory sockets are designed, removing and inserting it will clean it.

VooDoo · Post by **VooDoo** » Mon Apr 05, 2004 8:14 am

Originally posted by FlyingPenguin
You can clean the contacts on the memory stick (or any card) using a pencil eraser (a clean one!).

that, i knew, but thanx

me

VooDoo · Post by **VooDoo** » Mon Apr 19, 2004 6:04 pm

NOW IM PISSED

I GOT NEW MEMORY FROM AMDFORUMS (THEY ARE NOW PC Perspective / Amdmb Forums)

AND SWITCHED OUT THE MOBO WITH THE SAME ONE BUT THIS ONE HAS REV 2.0 ON IT

EVERYTHING IS THE SAME

IM STILL GETTING THE BSOD

I GOT PICS FROM MY CAMERA (THANX DAMAN, FOR THE 7 IN 1)

HERE THEY ARE

ME

eGoCeNTRoNiX · Post by **eGoCeNTRoNiX** » Mon Apr 19, 2004 6:14 pm

Didn't look it over, but maybe this will help..

http://www.microsoft.com/resources/docu ... p_czgw.asp