Post your BSOD pics.

[nando2323]

Post your BSOD pics and explain what causes it.

Well here is mine at work that happens all the time. It happens in SQL Server Management Studio when resizing columns while viewing a database. The fix I found was to disable the Microsoft Intellipoint driver because it is not compatible with Microsoft SQL Server WOW!

 

[Andrew Henry]

Why? Because it happens to all OS's.

 

[Flore]

The fix I found was to disable the Microsoft Intellipoint driver because it is not compatible with Microsoft SQL Server WOW!

How the hell did you figure that out?

 

[nando2323]

How the hell did you figure that out?

After searching multiple forums I came across the fix. No credit due to me just to the person that found out. I asked the same question though.

 

[contoursvt]

I'd post one but I have not had a BSOD since 2002

Since I learned to do the following when I build my systems, I have not had any issues.

1. build computer using industry standard components and chipsets. Dont go off brands just to save a bit of $$. For me this means big name motherboards, intel chipsets and intel CPU. Dont skimp out on the power supply. Dont need super high wattage but stick with a reputable brand. No mystery 500W brands that weigh less than a donut.

2. quality ram running at factory spec - no overclock..etc. No overclocker ram thats rated at higher voltage. Stick with JEDEC ratings.

3. do a burn-in of RAM/CPU for 24-48 hours. If nothing fails and no memory errors, then you know the hardware is good.

4. dont install beta versions of stuff and most importantly no beta drivers.

5. keep the system clean. No need to have 2-3 different antivirus and antispyware running all at the same time. Jsut keep it simple. AVG and windows firewall for me does the trick.

6. dont go surfing for warez and 'free' stuff on your main computer. Bad stuff is bound to happen.

7. run a proper UPS on the computer

 

[Schtumple]

I'd post one but I have not had a BSOD since 2002

Since I learned to do the following when I build my systems, I have not had any issues.

1. build computer using industry standard components and chipsets. Dont go off brands just to save a bit of $$. For me this means big name motherboards, intel chipsets and intel CPU. Dont skimp out on the power supply. Dont need super high wattage but stick with a reputable brand. No mystery 500W brands that weigh less than a donut.

2. quality ram running at factory spec - no overclock..etc. No overclocker ram thats rated at higher voltage. Stick with JEDEC ratings.

3. do a burn-in of RAM/CPU for 24-48 hours. If nothing fails and no memory errors, then you know the hardware is good.

4. dont install beta versions of stuff and most importantly no beta drivers.

5. keep the system clean. No need to have 2-3 different antivirus and antispyware running all at the same time. Jsut keep it simple. AVG and windows firewall for me does the trick.

6. dont go surfing for warez and 'free' stuff on your main computer. Bad stuff is bound to happen.

7. run a proper UPS on the computer

or, buy a mac...

 

[nando2323]

I'd post one but I have not had a BSOD since 2002

Since I learned to do the following when I build my systems, I have not had any issues.

1. build computer using industry standard components and chipsets. Dont go off brands just to save a bit of $$. For me this means big name motherboards, intel chipsets and intel CPU. Dont skimp out on the power supply. Dont need super high wattage but stick with a reputable brand. No mystery 500W brands that weigh less than a donut.

2. quality ram running at factory spec - no overclock..etc. No overclocker ram thats rated at higher voltage. Stick with JEDEC ratings.

3. do a burn-in of RAM/CPU for 24-48 hours. If nothing fails and no memory errors, then you know the hardware is good.

4. dont install beta versions of stuff and most importantly no beta drivers.

5. keep the system clean. No need to have 2-3 different antivirus and antispyware running all at the same time. Jsut keep it simple. AVG and windows firewall for me does the trick.

6. dont go surfing for warez and 'free' stuff on your main computer. Bad stuff is bound to happen.

7. run a proper UPS on the computer

I take all the following into account but yet still manage to get some at least every couple of months. That laptop there in the picture is a Dell Latitude D820 with the NVIDIA 512MB Card and 3GB of RAM from Crucial. If Microsoft makes crap drivers that don't work with their own software then there's no precaution for that. That comp is running XP-SP3 also.

 

[contoursvt]

Umm ya its not really any more immune IMO
http://images.google.ca/images?gbv=2&hl=en&q=OS+X+kernel+panic&btnG=Search+Images

I also have a G4 with 10.3.9 and I've had one before. It can happen as well.

or, buy a mac...

 

[contoursvt]

Microsoft doesnt make crap drivers for their own software. Hardware vendors make drivers for microsoft products. Microsoft doesnt write Nvidia drivers. Nvidia writes Nvidia drivers (as an exmple).

The computer you have sounds like it would be a bad combination for a notebook computer. A pentium D is a very VERY hot running chip. To have that in a notebook cant be good. An overheat could cause a bluescreen btw.

So have you actually done a memory test overnight? What test did you run?

I take all the following into account but yet still manage to get some at least every couple of months. That laptop there in the picture is a Dell Latitude D820 with the NVIDIA 512MB Card and 3GB of RAM from Crucial. If Microsoft makes crap drivers that don't work with their own software then there's no precaution for that. That comp is running XP-SP3 also.

 

[nando2323]

Microsoft doesnt make crap drivers for their own software. Hardware vendors make drivers for microsoft products. Microsoft doesnt write Nvidia drivers. Nvidia writes Nvidia drivers (as an exmple).

The computer you have sounds like it would be a bad combination for a notebook computer. A pentium D is a very VERY hot running chip. To have that in a notebook cant be good. An overheat could cause a bluescreen btw.

So have you actually done a memory test overnight? What test did you run?

If you actually read my first post instead of flaming then you would see why I said Microsoft makes crap drivers!!!!