Random BSODS at Random Times - Please Help

pcnm0430 · 07 Nov 2009

Hello everyone and thank you for taking the time to read a newbie's post.

Anyways, I'm having a really frustrating problem.

Symptoms:
- Random BSODs happening at random time intervals from bootup
Example: Bootup, and after 5 minutes, BSOD. Bootup again, and
after 30 minutes, BSOD.
- BSODS are variety of errors not just one.

Side Note:
- Been running exact same build of windows 7 x64 from august 2009 till
November 2009. At around the 3rd, I did a clean install using the exact same
disc, drivers, etc. Problems started after my clean install.

Actions Taken:
- Ran Windows Memory Diagnostic on all memory with no errors
- Ran Windows Memory Diagnostic on each memory DIMM individually, and no errors
- Ran SeaGate Seatools and my hard drive passed
- Reinstalled Windows XP, Vista, and 7 version of my wireless usb adapter and problem continued
- Removed NVIDIA drivers for my 9600GT and using the default ones, problem still remained
- Problem still continues in Safe Mode and Safe Mode with Networking

- Did another clean install of windows 7 using again the same disc and drivers etc as from the time it worked, still nothing.

- on another post i read to run VERIFIER /FLAG 1 /ALL or something similar in command prompt. The last two minudumps are after I ran that and rebooted.

--------

The minidumps since the last clean install are included.

Any ideas?

Thanks,
Roik

H2SO4 · 07 Nov 2009

Hello and welcome to SF :)

pcnm0430 said:

The minidumps since the last clean install are included.

Where?

pcnm0430 · 08 Nov 2009

hmmm that's weird, they did upload O_o

reuploading

EDIT: attached to first post

H2SO4 · 08 Nov 2009

pcnm0430 said:

hmmm that's weird, they did upload O_o

reuploading

EDIT: attached to first post

A multitude of different crashes. I'd suggest you start by...

- Removing this driver ("BitDefender"?):

Image path: \SystemRoot\system32\DRIVERS\bdfsfltr.sys
Timestamp: Fri Jul 24 01:46:52 2009 (4A6885EC)

- Updating the older Wifi driver - it has known problems and it caused at least some of your crashes:

Image path: \SystemRoot\system32\DRIVERS\athrxusb.sys
Timestamp: Mon Jan 29 23:57:10 2007 (45BDEF26)

After that, upload any additional minidumps as (if) crashes occur. I suspect your machine may also have an underlying hardware defect, so make sure nothing is overclocked or undercooled.

pcnm0430 · 08 Nov 2009

Thank you for the quick response.

question: how exactly do I update that driver? I use a Belkin Wireless G [outdated i know >.>] and I installed the latest setup file available from the belkin website to make the thing work.

H2SO4 · 08 Nov 2009

pcnm0430 said:

Thank you for the quick response.

question: how exactly do I update that driver? I use a Belkin Wireless G [outdated i know >.>] and I installed the latest setup file available from the belkin website to make the thing work.

Exactly? Probably by buying a different WiFi NIC with an up-to-date driver which is certified for use with Win7.

There are several threads around here (and the rest of teh Interwabs) bemoaning the lack of updated driver for the NIC you've got now. I'm an optimist, however, so I suggest you check the situation again with the manufacturer. Email them if necessary.

pcnm0430 · 08 Nov 2009

Hmm emailing them is an option, however this wireless adapter/driver combination worked well with windows 7 for well over a month a a half. Why the recent trouble?

H2SO4 · 08 Nov 2009

pcnm0430 said:

Hmm emailing them is an option, however this wireless adapter/driver combination worked well with windows 7 for well over a month a a half. Why the recent trouble?

I don't know. You might want to ask them that in the same email (attach the minidumps though).

I'm not being facetious. Questions along the lines of "why only now?" and "why is it working on another machine?" are almost non-sensical in terms of crash debugging. The number of different code path combinations (A called D called B called Q called Z called M...) is truly vast, and in a crash you've only got the exact pattern that seemed to lead to a problem. Why did that pattern never occur before, or why did the same pattern not crash previously? That's for the driver developers to answer. Speculation is not useful in this context.

pcnm0430 · 08 Nov 2009

H2SO4 said:

I'm not being facetious. Questions along the lines of "why only now?" and "why is it working on another machine?" are almost non-sensical in terms of crash debugging. The number of different code path combinations (A called D called B called Q called Z called M...) is truly vast, and in a crash you've only got the exact pattern that seemed to lead to a problem. Why did that pattern never occur before, or why did the same pattern not crash previously? That's for the driver developers to answer. Speculation is not useful in this context.

Point taken. Will definitely be contacting them.
By the way right before writing this post, and after the removal of the bitdefender driver, i got another blue screen [minidump attached]. Fortunately, it took a bit longer to happen than usual [progress?]

.

Maybe a bit off topic: do you know of any alternative or 3rd party driver that would make this wireless adapter work?

-----

UPDATE: I have tried reinstalling the belkin latest wireless G driver for my adapter under vista server 1 compatability because in my mass googling i saw something somewhere related to how someone got it working under that mode. Ill update if i get another blue screen. Crossing my fingers :P

UPDATE: Nope, that didn't do anything. I got a SYSTEM_SERVICE_EXCEPTION BSOD, and another BSOD some 20 minutes after. these two are attached in "2 more .dmp files.rar"