Random 7 ult x64 BSODs

[forlornidealist]

I have been getting random BSODs. There is not a particular activity that seems to cause it, I am not even using the computer half the time when it happens.

I recently replaced my video card (went from an xfx nvidia 7800GTX to a sapphire radeon hd 6970) and my system drive (went from a 74gb wd raptor to a 120gb ocz vertext 3 ssd) and the issue persists, so it cannot be hdd or video card.

I have run a memtest86+ and no errors were reported after several passes.

I took 2 of my 4 4gb sticks of memory (going down from 16gb to 8gb) and the issue persists. I am in the process of swapping the slots/sticks etc to try to narrow it down to see if there might be a bad stick.

I have attached the required info and updated my system profile.

Any help greatly appreciated!

PS I reinstalled windows when I upgraded the system drive, and when I did I didn't reinstall Norton 360 because I thought it may have been the culprit. Unfortunately it was not.

 

[Jonathan_King]

Hello,

Acronis is blamed for one crash; try uninstalling it for the time being. Still, I doubt that's the true cause.

Open a command prompt, and run:

chkdsk /r

Also, run the three Prime95 tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 26 15:26:37.104 2011 (UTC - 4:00)
System Uptime: 0 days 1:50:14.243
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SyncToy.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
BiosReleaseDate = 11/24/2010
SystemProductName = GA-890FXA-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 26 00:51:34.200 2011 (UTC - 4:00)
System Uptime: 0 days 2:08:34.309
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for fltmgr.sys - 
*** WARNING: Unable to verify timestamp for tdrpm273.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm273.sys
Probably caused by : tdrpm273.sys ( tdrpm273+46f3e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_tdrpm273+46f3e
BiosReleaseDate = 11/24/2010
SystemProductName = GA-890FXA-UD5
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[zigzag3143]

I have been getting random BSODs. There is not a particular activity that seems to cause it, I am not even using the computer half the time when it happens.

I recently replaced my video card (went from an xfx nvidia 7800GTX to a sapphire radeon hd 6970) and my system drive (went from a 74gb wd raptor to a 120gb ocz vertext 3 ssd) and the issue persists, so it cannot be hdd or video card.

I have run a memtest86+ and no errors were reported after several passes.

I took 2 of my 4 4gb sticks of memory (going down from 16gb to 8gb) and the issue persists. I am in the process of swapping the slots/sticks etc to try to narrow it down to see if there might be a bad stick.

I have attached the required info and updated my system profile.

Any help greatly appreciated!

PS I reinstalled windows when I upgraded the system drive, and when I did I didn't reinstall Norton 360 because I thought it may have been the culprit. Unfortunately it was not.

\
Memory corruption caused by an unknown driver please run these two tests


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.



Driver verifier

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

 

[forlornidealist]

Update

@Jonathan_King
I have uninstalled true image and the issue remained.

I have run a chkdsk /r and am waiting to see if it made a difference, although I'd be surprised if it did since this was a fresh windows install and I had the same issue on a different hard drive.

I have run the Prime 95 'blend' test for 6 hours and none of the 6 workers stopped. I will run the other 2 tests over the next 24 hours.


@zigzag3143
I have already run memtest86 (as I said in the original post). It ran for 5 passes without errors. Does it really make a difference if I test each stick individually?

I have made the driver verifier settings changes and will await another BSOD.



I have attached 3 new dump files from today in a zip. The computer also has a BSOD while I was at work but for some reason there was no dmp created. The error was:
KERNEL_DATA_INPAGE_ERROR (0x0000007A)


Thanks for the help to both of you!

 

[forlornidealist]

Update again

So after enabling the driververifier settings, I was not able to get into windows, nor was i able to get into safe mode, nor was I even able to get into the system restore utility.

I am currently reinstalling windows from disc.