[scorcher9]

I am having BSODs in win7 with the error code 0x0000007E and it starts the crash dump. I can hardly run the windows for 2 or 3 minutes. I don't know what information about my machine will be useful for you guys in resolving so please help me in this issue and tell me what info I can post here.

[Borzi]

Most likely either a corrupt install, you've fiddled with it, or there's hardware issues. You'll need to specify what you're running it on and whether you've had a chance to mess it up. Sounds like it's stuffing up just after you installed it, might be worth a reinstall (if you downloaded the installer, redownload) and make sure you're networked during the install so Windows can pull the latest drivers. Video cards are a common culprit. Also check whether you've left sufficient hard drive space for the operating system, XP would generate the same error in all of the mentioned situations.

If it's a stock laptop, name the model eh, a custom built desktop name the components.

[Rollin' Rog]

When did these begin?

-------------------------------------------------------------------------------------------
I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to c:\windows\minidump and copy the last few minidump files to that folder. *this assumes 'c' is your boot drive, if it is not, subsitute accordingly
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder.
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.

This might point us to a non Microsoft driver causing the error, if one exists for it.

If you do not see any minidumps, be sure you are not using any cache cleaner such as CCleaner. Also run sysdm.cpl and select Advanced > Startup and Recovery. Make sure "small memory dump" is the one chosen under "write debugging information" and the location should be %systemroot%\minidump

Since almost all bugchecks can be caused by faulty ram, I would recommend you perform memory tests.

To perform a memory check run mdsched.exe and when you reboot and the scanner appears press F1 for Advanced Options and try the Extended test.

----------------------------------------

I would also recommend you try a Clean Boot test >> http://support.microsoft.com/kb/929135/en-us

[scorcher9]

So nice of you guys for taking some time out for me, thank you!

I have windows 7+windows xp dualboot. Win7 is having these BSODs it doesn't even let me run it a few minutes but I have this XP which is running fine. As for the dualboot I have it for some time and everything was good and clean. Then my brother installed some applications in Win7 and some driver updates, after which these BSODs strarted appearing. I have attached some of the dump files, please if you can resolve this issue I'll be highly grateful!

[Frank4d]

You are running Windows 7 Build 7127 pre-RTM which is beta software. So it could be fixed with a repair install, or not. Most of the logs point to ntkrnlpa.exe and srv2.sys as possible culprits.

I recommend buying the final version of Windows 7 and try again.

[scorcher9]

Originally Posted by Frank4d

You are running Windows 7 Build 7127 pre-RTM which is beta software. So it could be fixed with a repair install, or not. Most of the logs point to ntkrnlpa.exe and srv2.sys as possible culprits.

I recommend buying the final version of Windows 7 and try again.

Thank you for your response. Can you please guide me what are these files? Are they some drivers or windows files or what?

These BSODs started appearing from last couple of days, before that the windows was just fine.

[Rollin' Rog]

The first is a core system Memory Management driver, but the second is probably where the issue lies, and is associated with a "remote server" application. >> http://www.google.com/search?client=...utf-8&oe=utf-8

It was the subject of a recent Security advisory

http://www.microsoft.com/technet/sec...ry/977544.mspx

You do seem to have a server configuration established from what I can make out of the Back Trace, and Bit Defender could also be a suspect since it will have its fingers in the pie.

Also, for what it's worth, the last driver in the back trace (asyncmac.sys) is a "remote access" serial network driver >>

http://www.greatis.com/vista/Drivers/a/asyncmac.sys.htm

[scorcher9]

As for the security advisory, i remember at many times BitDefender warned me that it has blocked a port scan attempt at port 139 and it showed some ip address. I was lazy enough to take any action because it said it already blocked it. I think BitDefender is by far the most reliable antivirus+antispyware+firewall software (at least that is what everyone say).

Finally, what do you conclude now where is the problem actually? And also advise me any workaround!

[Rollin' Rog]

I don't know how you have the system set up. What exactly is the "remote server" configuration?

How long can you go without a BSOD in Safe Mode with Networking?

Hmmm, what is this we've got here? >>

** WARNING: Unable to verify timestamp for acovdelz.SYS
*** ERROR: Module load completed but symbols could not be loaded for acovdelz.SYS

Only google hit for it is here, which usually means a malicious file, possibly a rootkit >>

http://www.google.com/search?client=...utf-8&oe=utf-8

And this is from a different back trace >>

WARNING: Unable to verify timestamp for aytwavc8.SYS
*** ERROR: Module load completed but symbols could not be loaded for aytwavc8.SYS

Ok, looks like it belongs to Daemon Tools -- and I think you should remove that for the time being as it may affect memory management processes.

[scorcher9]

It is my home computer with a broadband connection.

I don't have daemon tools on my system, but I have Alcohol!

Can you please explain what is a rootkit and back trace?

[Rollin' Rog]

If you only have Alcohol, then that uses the same driver and technique

In any case I would uninstall all "virtualization" software.

You may want to try with BitDefender uninstalled as well.

The "back trace" is all the loaded drivers from the time of the fault, it is similar to a "trap frame" which includes drivers using the actual memory context of the fault.

A "rootkit" is a driver that is loaded at boot time which does not normally show as an installed driver as it uses "stealth" techiques. It is normally a "malware" problem, but not in the case of Daemon Tools and other software trying to avoid detection.

[scorcher9]

Sir thank you for your support! Do you think that the windows being the beta version is causing some problem as the other person said?

Just for the info, I have no networking other than the broadband connection. I have done a deep system scan with BitDefender and found no virus or malware. Now I'll try uninstalling BitDefender and Alcohol. I will post the results soon.

For the time being, I am experimenting with the msconfig. Disabled all the services other than ones from Microsoft. 10 minutes and no BSOD yet. Waiting for one....

[scorcher9]

I uninstalled Alcohol, and BitDefender but still getting BSODs...

I've attached the latest dump file kindly check it out!

Thanks alot for your help.

[Rollin' Rog]

I am still seeing the same srv2 error.

Does it occur also in Safe Mode with Networking support? If so, post a new minidump for that.

This build of Win7 was evidently one leaked to many torrent downloads. Is that how it was obtained? The debugger will not even provide complete symbol packages for it since certain critical system drivers are not the same as current versions.

I may really just have to go with Frank4d's suggestion that you need a current version.

But I'd also like to know more about the starting processes, do the Scanlog in Normal mode >>


Download and install HijackThis. Run it and select "do a system scan and save the log file". Then copy/paste the contents of the log to a reply

http://www.trendsecure.com/portal/en...ols/hijackthis

[scorcher9]

As for the HijackThis log file, here it is;

1 hour on Safe Mode with Networking and no BSOD.

I don't know about the windows as I got it from a friend.