random BSOD occuring on new windows install

[skirby4]

I am getting seemingly random BSODs when I use my computer. The main culprits seem to be tcpip.sys and ntoskrnl.exe but there are others as well. Ive been trying to trouble shoot but I am really not sure. I am beginning to think it's faulty hardware (mobo or hd) but i want to be 100% sure before i replace something. The system is 2 years old.

Specs are:
GIGABYTE GA-EX58-UD5 LGA 1366 Intel X58 ATX Intel Motherboard
SAPPHIRE 100245L Radeon HD 4850 512MB 256-bit GDDR3 PCI Express 2.0 x16
Intel Core i7-920 Bloomfield 2.66GHz LGA 1366 130W
CORSAIR DOMINATOR 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
Western Digital Caviar Black WD1001FALS 1TB 7200 RPM SATA 3.0Gb/s 3.5"

 

[fimble]

Hi skirby4 and Welcome to the Forums.

Three of your .dmp files return a stop error 0x124 which is usually hardware related and is probably your main issue.

See Stop 0x124 - what it means and what to try for assistance.

The majority of your .dmp files however, indicate device drivers which will not help your cause.

Uninstall Daemon Tools. The driver it utilises, sptd.sys, is notorious for causing BSOD in Windows 7. Use the correct download for your system to remove sptd.sys. Be sure to click remove!!

PC Tools Internet Security is also known to cause issues with Windows 7. Uninstall and replace with BSOD friendly Microsoft Security Essentials

Question Do you also have Threatfire installed? If so uninstall that as well using the AV Uninstaller listed.

NOTE!! Running two AV products at the same time will cause conflicts!


Outdated drivers can and will cause issues. Update these drivers:

netr28ux.sys Mon May 25 05:38:17 2009 Ralink RT2870 series USB 802.11n Wireless Adapter Driver (you may have a different manufacturer)

RTKVHD64.sys Fri Sep 03 09:02:27 2010 Realtek HD Audio

RtNdPt60.sys Mon Jul 20 03:27:32 2009 Netgear GA511 Driver file (Realtek chipset)

 

[skirby4]

I removed my older harddrive and installed windows on a new drive. I haven't had a bluescreen since. Seems like this was the problem. Fingers crossed.