Windows 7 Crashing - Registry Rollback

[A4orce84]

Hey Everyone,

So my windows 7 machine (freshly formatted and working fine for the last few weeks) has recently started crashing every couple of days.

I'm not sure what's happening, but basically I turn on my computer and it hangs at the "Starting Windows" animation. Basically my computer comes to the desktop in a minute or two, but it will hang at the starting windows screen for what feels like 10 minutes before finally hitting a BSOD and restarting.

The recovery system kicks in, rolls back the registry, restarts, and I'm able to get back into my machine and desktop as if there were no issues.

I have copied the "error results" and am pasting them below:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1033

Additional information about the problem:
BCCode: 74
BCP1: 0000000000000002
BCP2: FFFFF880037CAB20
BCP3: 0000000000000002
BCP4: FFFFFFFFC000014D
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\120409-26140-01.dmp
C:\Users\Asif Ahmad\AppData\Local\Temp\WER-47906-0.sysdata.xml


If anyone could offer ANY assistance, I would greatly appreciate it. I'm not sure what's going on, but it seems like since I'm able to get back to my desktop with no issue after the rollback, it shouldn't be anything too crazy.

Thanks in advance guys!


--Asif

 

[torrentg]

Hi. You can follow this:

http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

 

[A4orce84]

Sorry about that. Here is the contents of my mini-dump file zipped up!

Thanks!

 

[torrentg]

Seems you already fixed the issue:

Bug Check 0x74: BAD_SYSTEM_CONFIG_INFO

I'd update these drivers to the latest 2009 versions by updating the respective software:

DLARTL_E DLARTL_E.SYS Tue Aug 01 23:05:19 2006
DLACDBHE DLACDBHE.SYS Thu Feb 08 23:05:10 2007
PxHlpa64 PxHlpa64.sys Mon Jul 24 20:18:43 2006
DRVECDB DRVECDB.SYS Fri Jul 21 14:21:08 2006

 

[A4orce84]

Well this is the 2nd time this has happened. I'm assuming something behind the scenes is messing with my registry possibly?

Any ideas what those drivers are? Device-wise, so I can easily update?

Thanks.

 

[torrentg]

No. Maybe for Roxio, Sonic or something. You can Google them.

 

[usasma]

More info on the error message: BSOD Index
Please note that this is a registry error.

Although the WinDbg stack doesn't mention NTFS.SYS, it is mentioned in BlueScreen View.
That, combined with the recurring problem, suggests to me a problem with your hard drive.

There's 2 things to check to rule this out:
- a free hard drive diagnostic: HD Diagnostic
- This procedure (try it several times, a couple of days apart, especially after the crash):

CHKDSK /R
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

Elevated Command Prompt
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry.
Copy/paste the results into your next post.

 

[A4orce84]

Chkdsk was not an option in the "Eventvwr" application unfortunately. =(

After running chkdsk, it did say it "fixed problems on my disk" though. But I don't know if that's it, or in a few days is my computer going to crap out again upon booting, and then rollback the registry again for everything to work correctly.


Should I check anything else? Anyone else have any ideas?

 

[usasma]

Run the hard drive diagnostic: HD Diagnostic
That'll tell you if there's a problem with the hard drive.

You can also run CHKDSK /R again in a couple of days.
If it gets more errors, then there's a problem.
The problem is either with the hard drive (the test above will tell us this), or with a program accessing the NTFS file system improperly.

It won't hurt to run SFC.EXE /SCANNOW from and Elevated (Run as administrator) Command Prompt.