Blue Screen OS version 6.1.7601

[AWN7F]

got tthis problem for several day and my place call
"my little fun house"


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

Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 834A8F13
BCP3: 8CF9BB0C
BCP4: 8CF9B6F0
OS Version: 6_1_7601
Service Pack: 1_0

Files that help describe the problem:
C:\Windows\Minidump\042213-35568-01.dmp
C:\Users\CINDY\AppData\Local\Temp\WER-49046-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Lets run a SFC /scannow .

If SFC /SCANNOW locates any corrupted files please upload the log file . Log file could be located C:\Windows\Logs\CBS\CBS.log

Once that is complete. Run chkdsk /F /R . Open the Elevated command prompt as you did for SFC /SCANNOW.


#7sp1


Did you have any USB video devices attached? If so, disconnect them and see if that helps.
Also, please uninstall any software related to the USB video device. Then download a fresh copy and install it.


AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.
Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

#threadorder


Sorry for not being clear. I specifically wondered why stated "...but I can't be sure." Why is that? What does the stop on the button desktop say?

As long as I'm correct about the wireless USB device, things should work just fine afterwards.

With BSOD's there shouldn't be any permanent damage as Windows is designed to "fail fast" and avoid problems that way. There is a chance of some corruption due to the BSOD's, but not as much as if you'd get by shutting down the computer by being hold the power switch (LMAO) end of it is time!!.

 

[axe0]

I'm not sure I follow you, where did you get this info from?

Sorry for not being clear. I specifically wondered why stated "...but I can't be sure." Why is that? What does the stop on the button desktop say?

I have no idea what this is about and cannot answer without context.

BSODs don't cause corruption of any sorts, they prevent corruption as much as possible. If there is corruption that looks to be due to BSOD crashes, it's not because of the BSOD but because of what happened prior the BSOD. Furthermore, a BSOD cannot prevent permanent damage as that's something beyond the BSOD process. Think about hard drive failure, if a drive starts to fail the number of bad blocks may increase, this is the most common way a hard drive could fail, therefore causing permanent damage which is not something a BSOD can prevent.