one BSOD after another BSOD

Intro

i get BSODs, sometimes it just gives me a pile of codes as an error message and sometimes i get DRIVER_IRQL_NOT_LESS_OR_EQUAL

i have gotten this problem a month ago, sometimes it happens 5 minutes i use my computer and sometimes it doesnt happen for two days with no issues.

A while back i got these BSODs, Initially there was a few software programs that no longer were functional, such as games or my anti virus and my firefox, they had errors after my BSODs came in.

after reinstalling them including a nvidia graphics drivers update i thought i solved the problem but i didnt.

Computer Specs:

Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
Language: English (Regional Setting: English)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: Default System BIOS
Processor: AMD Phenom(tm) II X4 840 Processor (4 CPUs), ~3.2GHz
Memory: 4096MB RAM
Available OS Memory: 3328MB RAM
Page File: 1343MB used, 5309MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

Graphics card is a nvidia GTX 460

Age of OS: i got this computer five months ago, installed it that far back, only once. Full version i guess.

OEM: i have no idea...

Yeah the OS was a retail CD disk purchase.

louis cardinal said:

Intro

i get BSODs, sometimes it just gives me a pile of codes as an error message and sometimes i get DRIVER_IRQL_NOT_LESS_OR_EQUAL

i have gotten this problem a month ago, sometimes it happens 5 minutes i use my computer and sometimes it doesnt happen for two days with no issues.

A while back i got these BSODs, Initially there was a few software programs that no longer were functional, such as games or my anti virus and my firefox, they had errors after my BSODs came in.

after reinstalling them including a nvidia graphics drivers update i thought i solved the problem but i didnt.

Computer Specs:

Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
Language: English (Regional Setting: English)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: Default System BIOS
Processor: AMD Phenom(tm) II X4 840 Processor (4 CPUs), ~3.2GHz
Memory: 4096MB RAM
Available OS Memory: 3328MB RAM
Page File: 1343MB used, 5309MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

Graphics card is a nvidia GTX 460

Age of OS: i got this computer five months ago, installed it that far back, only once. Full version i guess.

OEM: i have no idea...

Yeah the OS was a retail CD disk purchase.

Several problems

First
Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.

Second Your crashes appear to be caused by a device driver.
To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

1. Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
2. Try disabling memory caching of the BIOS.
3. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer. (see memtest below)
   
4. Please run chkdsk

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

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.

See "CHKDSK LogFile" below in order to check the results of the test.


B- 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"


C-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 (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.





Third please run these two tests


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-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/Win7 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" (without the quotes) 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

nice, thanks for your help zigzag3143

since i dont have alot of time, it will take me a while to do ALL of the things you asked above, ill be in touch in a while.

Let us know how it turns out, and if you need any further help

okay first off i was using my computer then i got constant waves OF BSODs, one of the softwares i was using (Steam) before this happened got corrupted so the next time i logged on it didnt work, that crossed the line. i went forward to verification of my drivers, i did exactly what you asked for with the "verifier".

the error i recieved was a "NTFS.sys" ( a driver) which i never gotten before.

So, now im getting multiple blue screen errors and then after three seconds of the dumping it automatically reboots.

what do i do now? change the verifier back? what am i suppost to do with the verifier and all the drives that i disabled.

stopped the verifier after around 8 BSODs happening precisely 20 seconds after the log on screen showed.

used "verifier /reset" to stop it And For some damn reason strangely... havent gotten a single BSOD for a day (yay back to gaming).

but i swear my problem may come back, is that all that needs to be done with the driver verifier? or i post some dump logs?

louis cardinal said:

stopped the verifier after around 8 BSODs happening precisely 20 seconds after the log on screen showed.

used "verifier /reset" to stop it And For some damn reason strangely... havent gotten a single BSOD for a day (yay back to gaming).

but i swear my problem may come back, is that all that needs to be done with the driver verifier? or i post some dump logs?

Post whatever dmp files you have from when verifier was running. If you cant tell which is which send them all

attachment below

louis cardinal said:

attachment below

Easy, Your Avira. Remove and replace with Microsoft Security essentials


Avira AntiVir Removal Tool - Download

Virus, Spyware & Malware Protection | Microsoft Security Essentials