I've been getting BSOD frequently of late

I

ishnath

New Member
Six days ago, while installing deamon tools on my pc, i got my first BSOD. I uninstalled deamon in the safe mode and PC started working well. One day later, while writing data on a multisession disk using Roxio Creater DE, i got another BSOD. After that I got another while installing adobe cs4 master collection. I asked help from my neighbours and finally decided to format my harddrive and re-install windows. At the end, when I had installed all the programs again, I got a BSOD while removing MusicmatchJukebox icon from the system tray. I've uninstalled MusicmatchJukebox from my computer a while ago, and it is working fine, but I think this is serious. I've never had BSODs before. What should I do? I can't write details of what appears on the blue screens as it happens so quickly.
PS-What problems in my PC are implied by occurence of BSODs, and what problems can they cause?
 

My Computer

System One

Hello ishnath, welcome to Vista Forums!


It could be a RAM issue or other HW failure; one thing at a time; in the start menu, start/search box type "mem" and click on "Memory Diagnostic Tool" at the top and let it run to see the results.

Be sure to post back with the outcome.















Later :shock: Ted
 

My Computer

System One

  • Manufacturer/Model
    * BFK Customs *
    CPU
    Intel C2Q 9550 Yorkfield
    Motherboard
    ASUS P5Q Pro
    Memory
    8GB Dominator 8500C5D
    Graphics Card(s)
    XFX ATI 1GB 4870 XXX
    Sound Card
    Realtek HD 7-1
    Monitor(s) Displays
    1x 47" LCD HDMI & 2x 26" LCD HDMI
    Screen Resolution
    1920x1080P & 1920x1200
    Hard Drives
    2x 500GB 7200RPM 32MB Cache WD Caviar Black
    PSU
    Corsair 620HX
    Case
    CM Cosmos RC-1000
    Cooling
    Tuniq Tower 120, 2x 140mm and 3x 120mm case fans
    Keyboard
    HP Enhansed Multimedia
    Mouse
    Razer Diamondback 3G
    Internet Speed
    18.6Mb/s
    Other Info
    My First Build ;)
Hi ishnath,
To find that is causing the BSOD we need the technical infrmation of the Bluescreen, we need to have the Error code for the BSOD, If the system is restarting as soon as you get the BSOD, then restart the system and go to advance boot option and select the option Disable automatic restart after system crash and workk on the system and this time the system has a BSOD the system will not restart !
So you can take the BSOD error code and google it you will find some clue abt the error or you can run the windows Debugger that will give you a detail information abt the BSOD.


Just some useful tips.
 

My Computer

System One

Jerin said:
Hi ishnath,
To find that is causing the BSOD we need the technical infrmation of the Bluescreen, we need to have the Error code for the BSOD, If the system is restarting as soon as you get the BSOD, then restart the system and go to advance boot option and select the option Disable automatic restart after system crash and workk on the system and this time the system has a BSOD the system will not restart !
So you can take the BSOD error code and google it you will find some clue abt the error or you can run the windows Debugger that will give you a detail information abt the BSOD.


Just some useful tips.
Click to expand...

Just as a suggestion, a minidump has all of the info you've requested plus a lot more, and it's a lot easier to obtain.

By itself, the bugcheck code is almost entirely useless as a means of troubleshooting because it confers no specific information about the cause of the error. In fact, the same underlying fault may manifest itself as (for example) 0x50, 0xD1, 0xA, and a whole bunch of others, depending on the precise environmental conditions at the time. Even knowledge of the 4 bugcheck parameters does not necessarily help unless one happens to be extremely lucky and the (relevant) memory addresses match an article which has already been published.

When it comes to quick bugcheck troubleshooting, minidumps 0wn.
 

My Computer

System One

I see. I need a small info. I'm going to read and copy the contents of the next BSOD. But is the minidump contained in the BSOD? Once I get the blue screen again, where do I go to read/save the minidump?
 

My Computer

System One

ishnath said:
I see. I need a small info. I'm going to read and copy the contents of the next BSOD. But is the minidump contained in the BSOD? Once I get the blue screen again, where do I go to read/save the minidump?
Click to expand...

You don't have to wait for the next crash. Your \windows\minidump folder probably already contains several minidumps. If you copy a few of the latest ones to a different folder, then zip them up, and upload them here, someone may be able to tell you why the machine is crashing.
 

My Computer

System One

Oh! Now I regret to have formatted my harddrive. There's only one file in that folder- corresponding to the only crash since the recent installation. I've attached the zip file.
 

Attachments

  • Minidump.zip
    21.9 KB · Views: 4

My Computer

System One

ishnath said:
Oh! Now I regret to have formatted my harddrive. There's only one file in that folder- corresponding to the only crash since the recent installation. I've attached the zip file.
Click to expand...

The cause of the crash is not obvious from that dump. However, it's likely to be one of the drivers below. You've got many old drivers and they ought to be updated or removed:

start end module name
81ff5000 81ffdb40 PxHelp20 Tue Jul 25 10:18:21 2006 (44C5634D)
8b00f000 8b65c000 igdkmd32 Thu Jan 03 03:48:24 2008 (477BC058)
8b772000 8b790000 Rtlh86 Fri Jan 25 19:46:39 2008 (4799A1EF)
8b79b000 8b7a0ee0 MxlW2k Tue Jun 26 08:39:01 2001 (3B37BD85)
8b7b9000 8b7c0000 GEARAspiWDM Tue Aug 08 03:11:27 2006 (44D7743F)
8bc0a000 8bdf8d80 RTKVHDA Thu Dec 20 21:00:35 2007 (476A3D43)
8be00000 8be0c000 RtNdPt60 Tue Dec 11 13:50:18 2007 (475DFAEA)
a4d4c000 a4d52440 windrvNT Mon May 10 18:42:04 2004 (409F405C)
 

My Computer

System One

You must log in or register to reply here.
Back
Top