I get BSOD errors sometimes after the pc has been on for a few minutes and more often immediately after trying to watch a movie using any media player (Windows media, Ulead, etc.)

I’ve ran memtest86, hotcpu tester, tested my hard drives, swapped ram sticks and running the system with each stick of ram separately but the same error always occurs. I have even tried swapping the video card and removing all non-essential hardware, swapped all cables, and cleared dust wherever possible.

The only thing that seems to make the pc stable is when I downgrade the bus speed on the motherboard from 166 (333Mhz) to 133 (266Mhz). Obviously downgrading the bus speed drops performance quite a bit and the 2500+ cpu is now reported as a 1900+ on boot.

Any help on my dilemma would be greatly appreciated. Minidumps of the errors are attached to my post.

Software:

Windows XP SP2


Hardware:

Amd 2500+ Barton 333 Mhz Bus
Shuttle AN35N Ultra-400 Motherboard
1 – 256MB Ram 333Mhz FSB (Kingston)
1 – 256MB Ram 333Mhz FSB (Patriot)
Nvidia FX5200 Video Card 128MB Ram
1 – Hitachi 80GB 7200rpm Drive
1 – Hitachi 90GB 7200 rpm Drive
8X DVD/RW
Hauppauge PVR-150 Video Capture Card
300 Watt Power Supply

Attached Files

	Minidumps1.zip (84.4 KB, 1 views)
	Minidumps2.zip (85.8 KB, 1 views)

Hi,

The culprit maybe WinTV2K.EXE or hardware error of your TV card.


Mini103005-01.dmp BugCheck 1000007F, {f, 0, 0, 0}
Owning Process 813633c0 Image: WinTV2K.EXE

Mini103005-02.dmp BugCheck 1000007F, {f, 0, 0, 0}
Owning Process 813ee9c8 Image: WinTV2K.EXE

Mini110105-01.dmp BugCheck 1000007F, {f, 0, 0, 0}
Owning Process 820927c0 Image: WinTV2K.EXE

Mini110505-01.dmp BugCheck 10000012, {1, 200, 0, 0}
Owning Process 81b44020 Image: wmplayer.exe

Mini111405-01.dmp BugCheck 1000007F, {f, 0, 0, 0}
Owning Process 82cd5438 Image: csrss.exe

Mini111905-01.dmp BugCheck 1000007F, {f, 0, 0, 0}
Owning Process 82bc8328 Image: wmplayer.exe

Mini120105-01.dmp BugCheck 10000012, {1, 0, 0, 0}
Owning Process 82c38248 Image: SageTV.exe

Mini120205-01.dmp BugCheck 1000007F, {f, 0, 0, 0}
Owning Process 82741370 Image: Config.exe

Thanks... This will help me to narrow it down more. I will focus on those now to see if it fixes it.

I replaced the power supply since it did not respond after one of my reboots and that seemed to fix all the error messages I was having so it appears to have definitly been a hardware issue.

Thanks...

Kevin

Hi Keving,

I'm glad to hear that your problem is resolved.