BSOD Windows Vista 0x0000007B 0x80599BB0 0xC0000034 0x00000000 0x00000000

Hello,

Our Dell Inspiron 1525 (which operates with Windows Vista) showed up the so feared blue screen of death a couple of days ago with the error 0x0000007B 0x80599BB0 0xC0000034 0x00000000 0x00000000. I have been researching since then for possible causes and I realize the 0x7B is a boot problem, but I'm not sure what to do.

Important details:
- There is no safe mode option at startup. The only options are to Launch Repair (which, of course, I have already done, without success) and to Start Normally, leading always to the same BSOD.
- I don't have the Windows CD as the operating system already came installed in the machine.
- I've read all the other answers related to this issue in this Community.

The last thing I want to do is to have to format the computer and re-install Windows. Please, is there anything I can try before this?
This stop error is usually related to sata drivers. It cant see/find the hdd

Did someone install vista with AHCI disabled in the BIOS then turn it back on after??


6 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Blue screens are caused by faulty hardware or faulty hardware drivers.

 

To See if a Fix is Available

In Control Panel (and select Classic view in the left hand pane) choose Problem Reports and Solutions (type problem in Start's search box), go to Problem History, right click your error and choose Check For Solution. You may also right click and choose Details for more info. Post those details here.

 

To See if a Recent System Change Caused It

In Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then choose Reliability and Performance Monitor and choose Monitoring Tools then Reliability Monitor (type Reliability in search on Start) . This list is a chart of software installs, uninstalls, Windows updates, and crashes by date (scroll left to see earlier dates). See if your crashes started happening after you installed or uninstalled something.

 
Standard Hardware Troubleshooting
 
 
First lets test what hardware we can. Hardware faults can appear as many software faults, therefore we need to test hardware first..
 

Please do the following in order. Memory faults can cause disk corruption, disk faults can cause disk corruption. Disk corruption causes corrupted files (which SFC may be able to fix). If you get an hardware error stop and post back. Do not run chkdsk with faulty memory.

 
Memory Diagnostic
If you haven't run a memory diagnostic then please do so. Click Start - Control Panel - choose Classic View in left hand pane - choose Administrative Tools -  then Memory Diagnostics Tool.
 
S.M.A.R.T
Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).
 
Disk drives in Windows monitor themselves for impending failure. The feature is called S.M.A.R.T. It will detect impending failure 30% of the time. In an elevated command prompt type (it's one line)
 
wmic /namespace:\\root\wmi PATH MSStorageDriver_FailurePredictStatus get active,predictfailure,reason /format:List
 
If it's on Active will be true, if not on turn it on in the computer's BIOS.
 
Predict Failure should be False if everything's ok.
 
In Vista and later if SMART predicts failure Windows prompts the user to run Backup.
 
Run Chkdsk
In Computer right click all your drives and choose Properties, then Tools tab, then click Check Now. Tick BOTH checkboxes then Start. Reboot. This will take overnight.
 
SFC
Check for file corruption by clicking Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).
 
sfc /scannow
 
For Memory Diagnostic Results
Click Start - Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then Event Viewer then look at Event Viewer (Local) - Applications and Services - Microsoft - Windows - MemoryDiagnostic-Results for entries.
 
Look for EventID is 1201 or 1101 and Source is MemoryDiagnostic-Results
 
Double click the entry for details on that entry.

For Chkdsk Results
Click Start - Control Panel (and select Classic view in the left hand pane) choose Administrative Tools then Event Viewer then look at both the Application and System logs (under Windows Logs) for entries.
 
Look for EventID is 7 and Source is Disk
Look for EventID is 11 and Source is Disk
Look for EventID is 51 and Source is Disk
Look for EventID is 52 and Source is Disk
Look for EventID is 55 and Source is NTFS
Look for EventID is 130 and Source is NTFS
Look for EventID is 1001 and Source is Autochk
Look for EventID is 1001 and Source is Winlogon
Look for EventID is 1001 and Source is WinInit
Look for EventID is 1001 and Source is Chkdsk
Look for EventID is 26212 and Source is Chkdsk
 
Double click the entry for details on that entry.
 
P.S. 7 and 55 are the auto repair codes where windows repairs disk errors silently on the fly. 52 is the SMART warning.
 
For SFC Results
Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type (or copy and paste by right clicking in the Command Prompt window and choosing Paste).
 
findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log|more
 
This will see which files are corrupted. We may be able to copy them from another computer.
 

 
Dump Files
 
Dump files are files containing the state of the machine when it crashed. We can analyse the file to identify the driver (or program) causing the crash. See the last section on how to get them analysed by a volunteer.
 
Analyse Dump Files
If you want to analyse your own dump files.
 
You need to start Explorer as Administrator to access the files in C:\windows\Minidump. Right click Explorer and choose Run As Administrator.

Download and install Debugging Tools for Windows
http://msdn.microsoft.com/en-us/windows/hardware/hh852363
Install theWindows SDK but just choose the debugging tools.

Create a folder called Symbols in C:\

Start Windbg. File menu - Symbol File Path and enter

srv*C:\symbols*http://msdl.microsoft.com/download/symbols
 
Close and reopen WinDbg. File menu - Open Crash Dump

This will analyse the crash dump. You need to close and reopen WinDbg for each dump file analysed. Because you are downloading symbols from the internet WinDbg will appear to be doing nothing. But it's downloading. Be patient.
 
You are looking for a driver or system library that the crash occurred in at the end of the listing. Find the file, right click then Properties - Details tab. If it shows a driver you'll need to update the driver identified. Most drivers are in c:\windows\system32\drivers.
 
Search the Drive for a File.
Click Start - All Programs - Accessories - Right click Command Prompt and choose Run As Administrator. Type replacing drivername.sys with the name of the file being searched (or copy and paste by right clicking in the Command Prompt window and choosing Paste).

 

dir c:\drivername.sys /a /s

 
If it shows a system file see if you can get a program from analyze -v.

Type in theWinDbg command prompt
 
!analyze -v
 
-v stands for Verbose and if the crash was originated by a program, as opposed to hardware or a driver, it will appear in the middle of the listing.
 
eg
 
PROCESS_NAME:  java.exe
IMAGE_NAME:  ntkrnlmp.exe
 
PROCESS_NAME only appears in the analyze -v output and only if a program originated the call that faulted.

 
Upload Them for Analysis
 
Or upload the minidump files to your Public folder on Skydrive and copy the link from the address bar and I'll analyse them.
 
Skydrive is Microsoft's Windows Live file upload site at https://skydrive.live.com/.  Read about it at http://explore.live.com/skydrive.

If you have downloaded any of the Live applications or have a web based Live mail account you already have access to your Skydrive.

Put your event list in the Public folder and copy the link from the address bar.

--
.
--

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated March 5, 2020 Views 2,427 Applies to: