BSOD, Mini Dump Attached. Help?

[DanDinh]

EDIT 9/6/10

Thanks for the help guys. I found out the problem and my machine is faster than ever booting up and loading now. It was my power supply that was crapping out on me. I had an exact same model I bought about 1 1/2 years ago and I compared the two and the newer one I had was so crappy, they changed the quality over the years. It was lighter and the wires felt cheap, no wonder it went from 60 to 29.99 :[ oh well thanks though guys.

 

[ttran]

Hi and Welcome back!

The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC /SCANNOW

2. I still suggest that this somehow still related to RAM issue, or bad mobo, but let's get to that later.

3-Event viewer
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If y our driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Please remove Avast:
http://www.avast.com/uninstall-utility
Install MSE:
http://www.microsoft.com/security_essentials

Regard,

Tuan

 

[ttran]

Please update following out of date drivers:

RTCore64 RTCore64.sys Wed May 25 13:39:12 2005 (42941D90)

It's date from 2005 and is way too out of date (RivaTuner/EVGA Precision). please reset any overclocking, then remove the software or update it.

Rtnic64  Rtnic64.sys  Mon Mar 31 12:39:38 2008 (47F0791A)

Realtek Ethernet NIC driver
Realtek

Regard,

Tuan

 

[DanDinh]

Thanks for the fast reply Tuan, I've updated the RealTek Ethernet driver to the latest one 7/23/2009.

For the EVGA Precision It's updated to the latest version but I guess the RTcore64 hasn't been updated. Is there an updated RTcore64 file? So I can just replace the file. I cant seem to find it but even if I do there's no date of when the driver was made. I need the program not to overclock but to control the fan speed of my video card.

I've ran SFC /Scannow and no problems appeared.

Event Viewer has only one event logged which is BugCheck, and i've posted that in my first post. Event ID 1001

No triangles on device manager..

Could it possible that my ram is not compatible with my motherboard? This is the first blue screen I've had with this ram since I changed it to the appropriate timings.

 

[ttran]

I don't think there is any update for RTcore64.sys. As far as I know, they have update for RTcore32.sys only. I've seen many BSODs caused by them so please remove it. I would ask other team members if they know there is alternative speedfan control for you.

In the meantime, please enable Driver Verifier

 

[DanDinh]

Okay so I didnt uninstall EVGA Precision yet and haven't done Driver Verfier either but I was playing a game of Warcraft III and Alt Tabbed out and I had a BSOD this time was Memory_Management

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041284, 0xfffff900c34a6001, 0x000000000000262d, 0xfffff90000812000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-20857-01.

Note: I have only 2GB of RAM
Stock Timings 9-9-9-24 1.8v

Edit #2: So I was afking in Warcraft III again and got another BSOD! This time was IRQ_NOT_LESS_OR_EQUAL.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffff680003b9988, 0x0000000000000000, 0x0000000000000000, 0xfffff800028e92e2). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-15366-01.

Edit #3: So I uninstalled EVGA Precision to get rid of RtCore64, ill see how that goes. Does anyone know how to work SpeedFan?

Any info on this log?

 

[DanDinh]

So I uninstalled EVGA Precision, loaded up Warcraft III again and another BSOD!
IRQ_NOT_LESS_OR_EQUAL

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffffa7ff3ffffe0, 0x0000000000000002, 0x0000000000000001, 0xfffff800028a2f9e). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-12308-01.

This is frustrating, I totally regret building this PC now. Any tips on what's failing so I can get a it replaced?

PSU? MoBo? Ram? Video Card?

Gunna try out Driver Verifier now.

 

[DanDinh]

Ok so I ran the Driver Verifier and boy did I BSoD. Currently have 3 dumps saved, I had more BSoD but that was before windows even got to the login screen and they didn't save. One of the dump actually displayed the driver that was causing the problem.

Here's the dumps.

Thanks

 

[ickymay]

these old drivers need updating

BIOS64.sys fffff880`037dc000 fffff880`037e4000 0x00008000 0x3ee27f50 08/06/2003 01:12:00
BS_I2cIo.sys fffff880`037c0000 fffff880`037cb000 0x0000b000 0x457d0d57 11/12/2006 08:48:39
BS_TPIO64.sys fffff880`037b9000 fffff880`037c0000 0x00007000 0x49f91858 30/04/2009 04:17:44

please go to the biostar support page and update all of your drivers for your motherboard ?

do you have the latest bios for your mobo ?

 

[DanDinh]

Yes, I do have the latest BIOS for my MoBo which is 7/1/10.

I dont know how to update the other files. Doesnt say anything on the site.

 

[ttran]

Can I ask you what model of your mobo please bro?

 

[DanDinh]

Hey Tuan, its BioStar TA870+

Thanks for all the help guys.

 

[ttran]

Version 5.0/5.1 or version 5.2, there are 2 TA870+ so I want to make sure the right one

 

[DanDinh]

5.0/5.1

 

[ttran]

Update all the driver in here, especially the chipset one
BIOSTAR :: TA870+ :: Driver

 

[DanDinh]

I've downloaded that once before the chipset driver (when i first built the computer and ran with the faulty sticks) but that's long ago and I formatted. When i dl'd it it gave me ATi Catalyst, I'm using Nvidia GPU right now is that a problem?

 

[ttran]

Install all the latest driver on that site to see how it improve the performence first.

 

[DanDinh]

Well, this is the first time I actually installed the chipset after a reformat. Haven't gotten a BSOD yet played a whole game in Warcraft III. So far so good, stable. I wouldn't get my hopes up though, this p.c has put me through hell. Is it necessary to install the chipset? Does it increase performance? Guess it was my fault there. We'll see after a cold boot later on today. Been a long night. Thanks guys and good night/morning

 

[DanDinh]

So no BSOD yet, but on cold boot something weird happens. I start it up loads up to windows gets to my desktop and about 15 seconds later, my whole screen turns blank. There's no cursor nothing responds, had to hard reset and everything was fine and stable after. Pretty weird, any thoughts on this?

 

[ickymay]

Well, this is the first time I actually installed the chipset after a reformat. Haven't gotten a BSOD yet played a whole game in Warcraft III. So far so good, stable. I wouldn't get my hopes up though, this p.c has put me through hell. Is it necessary to install the chipset? Does it increase performance? Guess it was my fault there. We'll see after a cold boot later on today. Been a long night. Thanks guys and good night/morning

the chipset drivers are essential