Aggravatingly Frequent BSODS

Bhikshu · 23 Oct 2010

I have been using my current computer for around 5 months now, and have been experiencing BSODs with varying frequency-- for instance, yesterday I had no less than four within about ten minutes. Needless to say, I want a functioning system, so I need to get this fixed.

I am running Windows 7 Ultimate 64bit, a full retail version, on a computer whose components are mostly new (with the exception of my sound card, which is about 5 years old).

As I do not know much about computers, I'm going to include additional information (which may or may not be helpful, but better safe than sorry, right?)

At my more technically-gifted friend's request, I partitioned my drive into 2 parts. Oddly, on the primary drive, I see two versions of program files-- "Program Files (x86)", which is where programs tend to install by default, and just "Program Files". As I understand it, the "x86" usually is associated with a 32bit version, so why am I seeing this if I'm using 64bit?

Also, aside from BSODs, programs crash with alarming frequency some times. While trying to generate the performance report, for instance, windows explorer crashed twice.

richc46 · 23 Oct 2010

You have many different codes, as reasons. The most common is BC 24 NTFS. Check your hard drive.

Here are some of the other potetial causes
STOP 0x00000024: NTFS_FILE_SYSTEM Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

In order, test

Check Antivirus. Uninstall and test with MSE

Make sure all drivers are current.
The driver SPTD (Daemeon) should be removed.
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
www.duplexsecure.com/en/downloads

OUtdated drivers
AtiPcie AtiPcie.sys Tue May 05 11:00:22 2009
ASACPI ASACPI.sys Wed May 13 21:25:17 2009
amdxata amdxata.sys Tue May 19 13:56:59 2009
Rt64win7 Rt64win7.sys Fri May 22 10:52:30 2009
emupia2k emupia2k.sys Tue Jun 23 00:46:08 2009
ctsfm2k ctsfm2k.sys Tue Jun 23 00:46:10 2009
ctoss2k ctoss2k.sys Tue Jun 23 00:46:15 2009
ha10kx2k ha10kx2k.sys Tue Jun 23 00:46:17 2009
hap16v2k hap16v2k.sys Tue Jun 23 00:46:20 2009
ctaud2k ctaud2k.sys Tue Jun 23 00:46:46 2009
ctprxy2k ctprxy2k.sys Tue Jun 23 00:46:48 2009
COMMONFX COMMONFX.SYS Tue Jun 23 00:47:02 2009
CTAUDFX CTAUDFX.SYS Tue Jun 23 00:47:04 2009
CTSBLFX CTSBLFX.SYS Tue Jun 23 00:47:08 2009
ctac32k ctac32k.sys Tue Jun 23 00:49:35 2009
hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009

Any Microsoft dirvers can be ignored.
How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/

If these solutions do not correct the problem repost and I will supply further help;

Since there were many varied reasons, hardware may very well be the cause. If so we will start with a memory test. But go with my hunch, try the above, first.

Bhikshu · 02 Nov 2010

Ok, now I have a problem of an entirely different magnitude.

Long story short, I tried a lot of the stuff here and got a bsod to the effect of "This bugcheck is caused by an unhandled exception in a registry filter", and thereafter I was unable to start my computer properly. I later discovered, from a friend, that this might be due to my graphics card (the power would flicker on for a moment upon hitting the boot up button).

I unplugged my graphics card and, indeed, I could run my computer (though without a graphics card this was problematic). I re-inserted the graphics card, but failed to properly secure the power cords running to it. When I hit the on button, my computer made a horrible, high-pitched beep, and shut off. Now, even when I completely remove the graphics card (how I could originally run the computer), I can't get the power to come on.

Have I completely destroyed my computer?

Currently I am posting from my netbook.

richc46 · 02 Nov 2010

Computers beep when there is a hardware problem (should not be high pitched,however). The number of beeps and type give a clue to the problem. Example one long and two short may mean hard drive etc.
Sounds like you do have a hardware problem.