Two BSOD in one day. BCCodes: 3b and d1

[Gewitter05]

When I played the sims late last year I started getting the 3b code. I don't use my desktop very often, but since I recently moved I have began to use it more. The other day it crashed while I was gone for less than a minute and then today it crashed twice within a couple of hours. A couple of months ago I read it could be my drivers. I downloaded slim drivers and noticed my graphics card needed to be updated. Then today when my computer crashed I read that if you have your computer setup to automatically download updates that it could mess up the drivers by having them go back to the bad driver or something. So I went and changed that setting and opened slim drivers again and saw that my graphics card needed to be updated again so I did. Only then I got another BSOD and that's when I saw the DRIVER_IRQL_NOT_LESS_OR_EQUAL. I have the two error messages and will attach the dump files. I tried reading and figuring it out myself, but I feel like I am going in circles and I don't know where to begin. Thanks for the help... I forgot to mention I used this site to help look up bug check codes

Bug Check Code Reference (Windows Debuggers)


[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7601.2.1.0.256.1[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]

[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: 3b[/FONT]
[FONT=&quot] BCP1: 00000000C000001D[/FONT]
[FONT=&quot] BCP2: FFFFF880112E9912[/FONT]
[FONT=&quot] BCP3: FFFFF88002D52780[/FONT]
[FONT=&quot] BCP4: 0000000000000000[/FONT]
[FONT=&quot] OS Version: 6_1_7601[/FONT]
[FONT=&quot] Service Pack: 1_0[/FONT]
[FONT=&quot] Product: 256_1[/FONT]

[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\072014-39873-01.dmp[/FONT]
[FONT=&quot] C:\Windows\Temp\WER-62103-0.sysdata.xml[/FONT]

[FONT=&quot]Read our privacy statement online:[/FONT]
[FONT=&quot]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/FONT]

[FONT=&quot]If the online privacy statement is not available, please read our privacy statement offline:[/FONT]
[FONT=&quot]C:\Windows\system32\en-US\erofflps.txt[/FONT]

New blue screen
[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7601.2.1.0.256.1[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]

[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: d1[/FONT]
[FONT=&quot] BCP1: 0000000000000000[/FONT]
[FONT=&quot] BCP2: 0000000000000002[/FONT]
[FONT=&quot] BCP3: 0000000000000001[/FONT]
[FONT=&quot] BCP4: FFFFF88001867850[/FONT]
[FONT=&quot] OS Version: 6_1_7601[/FONT]
[FONT=&quot] Service Pack: 1_0[/FONT]
[FONT=&quot] Product: 256_1[/FONT]

[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\083014-37955-01.dmp[/FONT]
[FONT=&quot] C:\Users\Trance\AppData\Local\Temp\WER-63118-0.sysdata.xml[/FONT]

[FONT=&quot]Read our privacy statement online:[/FONT]
[FONT=&quot]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/FONT]

[FONT=&quot]If the online privacy statement is not available, please read our privacy statement offline:[/FONT]
[FONT=&quot]C:\Windows\system32\en-US\erofflps.txt




[/FONT]

 

[essenbe]

Please run the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html . All you have listed is a text of the dump files. Use option 2 and press the 'Grab All' button. Then give it a little time to work. Then upload the zip file here.

 

[Gewitter05]

I went ahead and did the SF Diagnostic Tool and added the zip file to original post.

 

[essenbe]

There were only 2 dump files created since July.

 lmvm avgtdia
start             end                 module name
fffff880`03e3f000 fffff880`03e7e000   avgtdia  T (no symbols)           
    Loaded symbol image file: avgtdia.sys
    Image path: \SystemRoot\system32\DRIVERS\avgtdia.sys
    Image name: avgtdia.sys
    Timestamp:        Tue Apr 15 06:26:40 2014 (534D1770)
    CheckSum:         0003E248
    ImageSize:        0003F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is your AVG Anti Virus

lmvm nvlddmkm
start             end                 module name
fffff880`11250000 fffff880`11eb4000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon May 19 18:08:44 2014 (537A8EFC)
    CheckSum:         00C1EA41
    ImageSize:        00C64000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Nvidia driver

 lmvm cdd
start             end                 module name
fffff960`007b0000 fffff960`007d7000   cdd      T (no symbols)           
    Loaded symbol image file: cdd.dll
    Image path: \SystemRoot\System32\cdd.dll
    Image name: cdd.dll
    Timestamp:        unavailable (00000000)
    CheckSum:         00000000
    ImageSize:        00027000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is a .DLL supplied by Windows as a display type driver

lmvm dump_ataport
start             end                 module name
fffff880`04fc0000 fffff880`04fcc000   dump_ataport T (no symbols)           
    Loaded symbol image file: dump_ataport.sys
    Image path: dump_ataport.sys
    Image name: dump_ataport.sys
    Timestamp:        Mon Jul 13 18:19:47 2009 (4A5BC113)
    CheckSum:         0000DE50
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is another Windows supplied driver to provide disk access during a Crash Dump

Please update your graphics driver using this guide http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

I would also uninstall AVG and replace it with MSE

You also have quite a few windows files missing r corrupt.

Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[Gewitter05]

Last night I upgraded the driver, uninstalled AVG and I ran the sfc / scannow. It said it needed to reboot to fix the files, but it was 2:30 in the morning so I decided to run it again this morning. Then it came up saying-- Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log. I will attach screen shot and the file with the CBS.Log. I just finished a third reboot. I was writing this while it was running and it said the same thing.

 

[essenbe]

Gewitter05, I think most of your problem is you are using an illegal Windows 7. The only way it can be activated is to alter system files.

Counterfeit installations such as yours contained heavily modified code that causes the installation to behave in unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them

 

[Gewitter05]

Alrighty. Thanks! I didn't realize it wasn't legal until my screen said so. Someone built the computer for me, but I wasn't friends with him and I moved away when I saw it wasn't legit. Another friend of mine said I should be okay as long as everything is running okay. Which everything was running fine until recently. Thanks again for the help.

 

[essenbe]

No problem.