BSOD errors in Windows 7 64bit (reports attached) help please

[shantijoe]

Hello
I've just installed the full retail version of W7 64bit and am having regular BSOD crashes and 'Recovered from a serious error' messages. Hardware is 1 year old (Intel DH67GD) i2500K, 12 GB RAM).
Any suggestions welcomed,
thanks, joe

 

[shantijoe]

CHDSK crashes W7 64 bit

Hello
I was advised to run CHDSK but in the final stages another BSOD occoured: Status 0xc0000189, Fatal System error c000021a.
Any thoughts on why the crash occoured? Can I try CHDSK in safe mode?:shock:
thanks, joe

 

[writhziden]

The error you give means the registry is corrupted or your temporary memory is corrupted. First, try clearing the temporary memory:

1. Shut down and turn off the computer.
2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
3. "Remove the computer from any port replicator or docking station, disconnect
   cables to printers or devices such as external monitors, USB memory sticks or SD cards, headset or external speakers, mouse or auxiliary keyboard, turn off WIFI and Bluetooth wireless devices." (Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English))
4. Hold down the power button for 30 seconds. This closes the circuit and ensures all
   power from components is drained to clear the software connections between the BIOS
   and hardware and clear any corruption in the temporary memory.
5. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall. Do not reconnect any unnecessary peripherals; monitor, keyboard,
   and mouse should suffice and be the only peripherals reconnected.
6. Turn it on to reinitialize the software connections between the BIOS and hardware

 

[shantijoe]

Temp. Memory or Registry errors?

The error you give means the registry is corrupted or your temporary memory is corrupted.

Thanks a lot for your speedy resonse. I'll try to continue without the extra USB devices and see what happens. If BSOD returns I assume it's a corrupt Registry?
If so is there an alternative to a fresh Windows install?
thanks again, joe

 

[writhziden]

A fresh install may be necessary, but you should take care of possible SSD problems first. See my analysis for more information.


Device Concerns:

Photosmart Premium C309g-m	ROOT\MULTIFUNCTION\0000	This device is disabled.
SBRE	ROOT\LEGACY_SBRE\0000	This device is not present, is not working properly, or does not have all its drivers installed.

Were you aware of the above? If so, please explain your troubleshooting steps.

SBRE, is reporting "tv_ConfigMgrErr24". - Microsoft Answers​

Analysis:

Crashes are probably due to the SSD. I would recommend doing some steps to resolve SSD issues:

• Make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.
  1. Power off the system.
  2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
  3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
  4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
  5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
  6. Let the computer remain in the BIOS for 20 minutes.
  7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
  8. Leave the drive disconnected for 30 seconds to let all power drain from it.
  9. Replace the drive connection(s) and then do steps 4-8 again.
  10. Repeat steps 1-4.
  11. Start your computer normally and run Windows.
  
  The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community
  
  While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

 

[shantijoe]

Thanks again: I've tried to reinstall the printer drivers but the error message continues and the printer works normally so I can't resolve that...
I understood that as the Vertex SSD is a system drive I was unable to update it's firmware..?
I will update the Chipset, Hard disk controller/SATA drivers,
thanks, joe

 

[writhziden]

If you want to update your SSD, you will need to first back it up as a system image, then update the firmware, and then restore the system image. See

http://www.sevenforums.com/tutorials/663-backup-complete-computer-create-image-backup.html?ltr=B

http://www.sevenforums.com/tutorials/73828-imaging-free-macrium.html

Free Backup Software: Paragon Backup & Recovery Free Edition - Overview

for some possible steps.

 

[shantijoe]

Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.

• 1. Leave the drive disconnected for 30 seconds to let all power drain from it.
  2. Replace the drive connection(s) and then do steps 4-8 again.
  3. Repeat steps 1-4.
  4. Start your computer normally and run Windows.
• 
  
  While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

Thanks I did all the preceding steps without error but after the final SSD power cycle I was greeted by the BSOD on booting into Windows- any thoughts?

thanks joe

 

[writhziden]

You did not mention yet if you had a chance to update the firmware drivers. I still think that should be made a priority.

Another option is to install on a platter hard disk and see if your problems persist. That would at least determine whether it is indeed an SSD based issue.

 

[shantijoe]

System SSD Firmware update...

Hello
I've followed you advice and finally traced the sabre.dll that was causing problems. This has been deleted along with the HP printer softwate whose uninstall caused another BSOD.
I'm left, as you say, with the issue of updating the SSD firmware. I'm delaying as it's a system drive and I find it very difficult to follow the procedure on these pages. Can you point to a simple link for this?
many thanks again, joe

 

[Golden]

Hi shantijoe,

Mike asked me to drop by here to help with updating the SSD firmware, as I did this recently too. The methods vary depending on exactly which make of OCZ Vertex you have.

Can you please provide the exact model so I can provide detailed steps of the procedure?

Regards,
Golden

 

[shantijoe]

BSOD after firmware 2.22 installed

Hello
I followed the instructions and used an ISO- fairly straightforward:
the firmware update produced a confusing meesage: Firstly 'Update unsuccessful'
then something like 'new firmware version 2.22 installed'. I then closed the toolbox.
I checked the disk and it has been installed however but another BSOD then occcoured.
Everything is now updated;BIOS, Firmware, SSD power test etc but another BSOD..?
thanks, joe

 

[shantijoe]

The exact model of my Vertex is: VTX3-25SATA3-240G
I hope this helps..?
thanks! joe

 

[shantijoe]

If you want to update your SSD, you will need to first back it up as a system image, then update the firmware, and then restore the system image.
.

Hello again
I used the update tools available here but had a strange result:
Following your advice for a system drive I created a system image to restore to after the update.
The update first produced the message: "Device not supported (Vertex 3 240GB) update failed" followed by 'update successful- firmware version 2.22'.
On reboot another BSOD occoured but on finally entering windows (without a system image restore) I found that the drive had in fact been updated.
This is as accurate an account as I can give other than the quotes which represent the information as well as I recall.
thanks again, joe:huh:

 

[Golden]

Hi Joe,

Sorry - I completely forgot about this. Did you use the Linux-based updater tools, or boot from a different hard disk?

OCZ Technology

Version 2.22 is definately the latest, so it appears that you did update correctly:
http://www.ocztechnology.com/files/ssd_tools/OCZ_SSD_v222_Firmware_Release_Notes.pdf

I think that message you got is a red-herring : were you using IDE or AHCI mode in your BIOS?

Regards,
Golden

 

[shantijoe]

ssd update

hello,
yes, I used the Linux based tools and continue to get BSOD. Did I follow the correct procedure? Do you suspect a faulty SSD or Registry errors? Which message was the 'red herring'?
thanks, joe

 

[shantijoe]

I am using AHCI mode,
joe

 

[Golden]

OK. For my Vertex 2 I had to change to IDE mode, then flash the firmware, then change back to RAID. I used the Linux-based tools. I got a very similar message to yours, but the firmware showed as updated. - hence the red herring.

Joe, as far as I can tell, you updated it correctly, so I think the problem lies elsewhere.

Has Mike (writhzeden) recommend performing a 'power-cycle yet'?

Regards,
Golden

 

[shantijoe]

Hello
yes, I've tried the power cycle (as per my previous reply) but got BSOD afterwards. Everything is up-to-date: BIOS, Firmware, Windows updates, yet the pattern continues. My platter HD was stable using the same set-up (hardware and drivers) but this doesn't mean new problems haven't developed> I've spent about 30 hours investigating this so far,
thanks for the on-going help, joe

 

[Golden]

Hi Joe,

OK. I had a similar problem (ignore the title, it wasn't the NVidia driver but the SSD), which I fixed by power-cycling but only after I updated the SSD firmware:

http://www.sevenforums.com/crashes-...ling-updated-nvidia-driver-2.html#post1940158

I would recommend cycling once again. If you still get a BSOD after that, upload a new dmp file for Mike to take a look at - I'll let him know to come back here again.

Regards,
Golden