Constant BSOD over the past two week, varying error codes

[devalonski]

Hello,

About every other boot, I get a BSOD for one reason or another. Sometimes, no BSOD will show up, but the comp. will loop through the welcome screen, meaning the welcome screen will show but will not displays user accounts and then it will turn black and back to the welcome screen again.

• Disk checks haven't pulled up anything.

• I've done virus scans with Kaspersky I.S. 2012, and Malwarebytes several times and there doesn't seem to be a virus involved.

Many Thanks,
devalonski

 

[koolkat77]

Welcome

Your msinfo file is corrupted

Please upload your msinfo32.nfo file. To get this:

• Click on the Start rb:
• Type msinfo32 into the Search programs and files box
• When it opens, go to File, Save
• Save as msinfo32.nfo and save in a place you will remember
• Let it finish the process of gathering and saving the system info
• Right click the .nfo file, click send to compressed (zipped) folder
• Upload the .zip file here.

PS: Kaspersky itself causes blue screens on some systems

 

[devalonski]

koolkat77,

Thanks for the speedy response. Btw... after the issue is resolved, will I be able to delete my uploads? It seems risky posting all this info.

Thanks, Devalonski

 

[koolkat77]

Thanks.

STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual causes: Device driver, Memory

Start Menu\Programs\Kaspersky Internet Security 2012	Public:Start Menu\Programs\Kaspersky Internet Security 2012	Public

Suggestions:

Kaspersky causes BSODs on some systems, please uninstall it
(You can install it back later if we know it wasn't a problem)

Install Microsoft Security Essentials and run a full scan
→ Microsoft Security Essentials - Free Antivirus for Windows

Run the system file checker, reboot each time (if it finds integrity violations)
→ http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Do these and observe your computer, let us know if there are more BSODs

 

[devalonski]

So it appears the system file checker showed several problems that it could not repair. I would like to correct these on my own; however, i do not have a windows 7 installation disk, since the comp. came with the software.

I attached the SFC results because I'm not sure what I'm looking at. Are these the only errors? How do I fix them?

"ieapfltr.dll" "mstscax.dll" "ieapfltr.dll" "InetRes.adml" "DFDWiz.exe"

Thanks!

 

[koolkat77]

I'm asking a friend to take a look at it.
Did you install MSE?

 

[devalonski]

Sorry, I forgot to mention that. Yes, i did instal MSE and there were no viruses or anything.

 

[koolkat77]

That's good.
Any crashes so far?

 

[devalonski]

Yes, I've had one since running MSE and doing the system file checker. Also, I've installed AVG and did a full scan, no viruses still.

 

[koolkat77]

Do not run 2 antiviruses at the same time.
Please upload the newest dump.

 

[koolkat77]

Ok, it's attached.

No dump files.
Anyway,

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data 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/Windows 7 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 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.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

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.

 

[NoelDP]

The Event reports show major problems with the filesystem



Please run a full CHKDSK and (another) SFC scan....
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type
CHKDSK C: /R
and hit the Enter key.

You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, and then reboot.
The CHKDSK will take a few hours depending on the size of the drive, so be patient!
After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

then run the SFC.

SFC -System File Checker - Instructions
Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
SFC /SCANNOW
and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.
Copy the full CBS.log file created to your desktop (you can't manipulate it directly) and then compress the copy and upload it to your SkyDrive (http://skydrive.live.com ) and post a link to it so that I can take a look.

 

[devalonski]

KoolKat,

I followed your directions and now when I try and boot, I get the following BSOD: USBfilter.sys 0x00000D5

School week started for me, so I'll try your route also Noel next time I get a break.

Many Thanks

 

[devalonski]

I disabled driver verifier in Safe Mode, uninstalled AVG and MSE, reinstalled Kaspersky, and updated a few drivers using Driver Reviver. Problem seems to be gone for the meantime, computer now runs normal. I'll be back should the problem arise again.

Thanks for the support,
Devalonski

 

[devalonski]

New BSOD message

Hello again,

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

0x1000007e