Mutliple BSOD's on start up and random. Minidumps attached

[WaffleMuffin]

Hey everyone,
I been looking for help on my BSOD issue. I have figured out where to find the minidump files and I have hopefully attached them here.

I was has having BSOD's problem before, but I didnt know what to do about it or what it was. So I formatted my hard drive and reinstalled windows 7. The computer came with Vista and I installed Windows 7 a year ago. I am still getting the BSOD at random times and on start up after the reinstall . I started to learn what Stop codes are and that this issue is fixable, I hope. So if someone can take a look at my minidumps and let me know what is happening, it would be greatly appreciated.

I remember I had a BSOD over a year ago, and I un plugged and plugged back in SATA cables and RAM sticks to clean up connects. A friend of mine told to do it then, and it seemed to have helped. I hope that is the case now, the machine is running fine for the past hour now, I hope it continues.

 

[zigzag3143]

No DMPS attached.



We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[WaffleMuffin]

Yes, I realized that. I'm working on that now. Hope to have them up soon.

 

[WaffleMuffin]

Here are the minidumps. There are four files from C:/Windows/minidump folder.

 

[zigzag3143]

Where are the minidumps. There are four files from C:/Windows/minidump folder.

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

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 "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- 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.

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.

 

[WaffleMuffin]

Zigzag, thanks for your help. I will run the Memtest and report back with what I find.

I have a Western Digital external HD that I run Raid 0/1 on. I have not installed the software for it yet, but I will do that after I run the Memtest and move sticks around to see what is bad.

 

[WaffleMuffin]

Memtest:
I let Memtest run overnight and checked it this morning at 8 passes. Memtest showed that there were NO errors, but since I had to get to work, I let Memtest continue running while I am at work.

Is there a report that Memtest produces that I can post on here to have someone double check the test?

Do I still need to move sticks of RAM around if the Memtest comes up with no errors?

Driver Verifier:
I'll try setting up the Driver Verifier tonight or tomorrow night when I have time.
- I have a netbook to use to get to the forums.
- I really dont care what happens to what I have installed on the computer I'm trouble shooting. I already did a complete format of the HD and reinstalled Win7. I keep all my important files on a secondary or external hard drive, (I've learned my lesson with that one before).

Also, I am not overclocking. I dont know where to begin to do that anyway.

 

[WaffleMuffin]

Just got home and Memtest ran 18 tests with no errors. I'm going to move onto the Driver Verifier now.

 

[WaffleMuffin]

Minidump after turning on the driver verifier. I got one BSOD on reboot and that is what is attached here. Computer rebooted itself after the crash and is running right now. I leave it one for the next few days and use it as much as I can.

Is it OK to install more programs on the computer when I'm trying to debug for BSOD? I mean I have CAD and Photo programs that should stress that I still have to reinstall.

Thanks for your help everyone.

 

[WaffleMuffin]

I found my minidumps files from the BSOD's before I reinstalled Win7. Can anyone tell me if they similar or different then the first minidumps that I posted ealier? I want to make sure I'm chasing the same problem. Thanks.

 

[zigzag3143]

I found my minidumps files from the BSOD's before I reinstalled Win7. Can anyone tell me if they similar or different then the first minidumps that I posted ealier? I want to make sure I'm chasing the same problem. Thanks.

No the only thing the earlier ones have in common with the most recent is the old drivers that were present then and still are, including your network driver.


CURRENT

xcmemVx64.sys    9/15/2008 5:04:14 AM        fffff880`03d8b000    fffff880`03deb000    0x00060000    0x48ce250e                        
xcbdaVx64.sys    9/15/2008 5:04:16 AM        fffff880`03d0f000    fffff880`03d43700    0x00034700    0x48ce2510                        
xchalVx64.sys    9/15/2008 5:04:54 AM        fffff880`0580e000    fffff880`05db3000    0x005a5000    0x48ce2536                        
xcfeVx64.sys    9/15/2008 5:04:55 AM        fffff880`046f7000    fffff880`047a0000    0x000a9000    0x48ce2537                        
Rt64win7.sys    2/26/2009 5:04:13 AM        fffff880`047a6000    fffff880`047d8000    0x00032000    0x49a65b0d                        
sxuptp.sys    5/8/2009 12:13:37 AM        fffff880`03c26000    fffff880`03c70000    0x0004a000    0x4a03b171

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 try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[WaffleMuffin]

Thanks Zigzag!

Did you take a look at the single minidump I posted yesterday from the BSOD I got after turning on the Driver Verifier?

 

[zigzag3143]

Thanks Zigzag!

Did you take a look at the single minidump I posted yesterday from the BSOD I got after turning on the Driver Verifier?

Yes. It is the one I referred to as "current"

 

[WaffleMuffin]

OK, so I need to go through each of the drivers that you listed as current and make sure that they updated with the most current driver from the manufactures website? Correct?

How do I update drivers without using the Windows Update? Is it as simple as copying and pasting the new driver in the file location of the old driver?

 

[zigzag3143]

OK, so I need to go through each of the drivers that you listed as current and make sure that they updated with the most current driver from the manufactures website? Correct?

How do I update drivers without using the Windows Update? Is it as simple as copying and pasting the new driver in the file location of the old driver?

Correct. If the date on the driver is before Jul 13, 2009 it needs to be installed in compatibility mode.

 

[WaffleMuffin]

After finding out what this drivers are or where they are from, I think that I only one I need to update is Rt64win7.sys. The first 4 drivers look like the belong to a antivirus program call Avast!, and I think I downloaded that a long time ago and no longer have it on the computer. The last one I think I can just delete.

Can someone please confirm that for me?

xcmemVx64.sys - belongs to a Avast! program that is a free antivirus program that I do not have on my computer. (I might of at point) xcmemVx64.sys Analysis Report

xcbdaVx64.sys - belongs to ViXS XCode Series Windows AVStream Driver for x64 Platforms, which I have no idea what it is. xcbdavx64.sys - What is the xcbdavx64.sys from ViXS Systems Inc.? (id:1211640)

xchalVx64.sys - xchalVx64.sys Analysis Report

xcfeVx64.sys - xcfeVx64.sys Analysis Report

Rt64win7.sys - belongs to Realtek and I think is for my modem card. Rt64win7.sys BSoD

sxuptp.sys - I think I can delete this one. sxuptp.sys Windows process - What is it?

 

[zigzag3143]

After finding out what this drivers are or where they are from, I think that I only one I need to update is Rt64win7.sys. The first 4 drivers look like the belong to a antivirus program call Avast!, and I think I downloaded that a long time ago and no longer have it on the computer. The last one I think I can just delete.

Can someone please confirm that for me?

xcmemVx64.sys - belongs to a Avast! program that is a free antivirus program that I do not have on my computer. (I might of at point) xcmemVx64.sys Analysis Report

xcbdaVx64.sys - belongs to ViXS XCode Series Windows AVStream Driver for x64 Platforms, which I have no idea what it is. xcbdavx64.sys - What is the xcbdavx64.sys from ViXS Systems Inc.? (id:1211640)

xchalVx64.sys - xchalVx64.sys Analysis Report

xcfeVx64.sys - xcfeVx64.sys Analysis Report

Rt64win7.sys - belongs to Realtek and I think is for my modem card. Rt64win7.sys BSoD

sxuptp.sys - I think I can delete this one. sxuptp.sys Windows process - What is it?

rename anything you dont know to *;BAK and update the Realtek.

 

[WaffleMuffin]

BAK is the file extension that I should be renaming? Then I can delete the one's I dont want?

 

[zigzag3143]

BAK is the file extension that I should be renaming? Then I can delete the one's I dont want?

Bak will prevent them from loading. If nothing complains then You can either remove them or "ZIP" them and store them just in case.

 

[WaffleMuffin]

I just updated the Realtek driver with the Win7 auto installation tool from this link: Realtek

The install went smoothly, but now I cant connect to my wireless router. I tried unplugging the router and playing with the settings to see if I can get it working. Nothing is working. Thoughts?

I'm also having a hard time finding some of the file names that I need to rename with BAK. I using the search bar under the window START icon, is there a better way?