Memory Dump

iflog · Post by **iflog** » Tue Jun 27, 2006 11:54 pm

Im getting a physical memory dump when playing LinksLS2000 direct IP.

0x000000D1 (0x00000014,0x00000007,0x00000001,0xBFC504EE)
Address BFC504EE base at BFC2C000, Date Stamp 4)c0327f - p17.sys
Physical memory dump complete.

Anyone know why this is or how to stop it?

Thanks

7thkevin · Post by **7thkevin** » Wed Jun 28, 2006 12:04 am

try reinstalling it or geten a patch

Post by **YeOldeStonecat** » Wed Jun 28, 2006 12:50 am

p17.sys is a Creative Audigy driver component (your sound card)
Get the latest drivers from Creative Labs.

iflog · Post by **iflog** » Wed Jun 28, 2006 11:47 pm

I uninstalled the game and reinstalled it from disc. I downloded the newest driver for my Soundblaster Live and then I couldnt get the sound to work. I uninstalled Soundblaster and reinstalled it from the disc. Sound works again. Game still doesnt. I can even play it offline and I'll only get a hole of golf in then I get BSOD. New numbers.

Stop: 0x0000007F (0x0000000D,0x0000000,0x0000000,0x0000000)
UNEXPECTED_KERNAL_MODE_TRAP
Begining dump of physical memory
Physical memory dump complete. Contact your sytem administrator or technical support group.

mnosteele52 · Post by **mnosteele52** » Thu Jun 29, 2006 12:03 am

0x0000007F is most likely hardware failure, my bet is your sound card.

Post by **YeOldeStonecat** » Thu Jun 29, 2006 12:57 am

http://support.microsoft.com/kb/137539/

I still would put money on your sound card drivers...focusing around the optimal method of replacing your existing drivers with the latest ones.

I'd uninstall your old drivers..every instance of them in add/remove programs. Then remove your sound card from device manager. Reboot. Then install the latest drivers.

iflog · Post by **iflog** » Thu Jun 29, 2006 11:40 pm

Well your not going to believe what it was. I opened up the case to find a ton of dust built up all over. It was inside the fans and in the grids on my cpu heat sink. I had to spray air and vaccuum everything I could. My guess is that the cpu was overheating and since it is right next to the ram sticks it was hitting them too. All is well now. Live and learn. Keep it clean. Thanks for all the replies.

mnosteele52 · Post by **mnosteele52** » Fri Jun 30, 2006 12:08 am

Thanks for letting us know what it turned out to be.