Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Recent Bsods happening at random

30 Mar 2013   #11

Windows 7 Home Premium x64
 
 

I believe I updated ASACPI.sys. I have Installed and uninstalled PCProbeII, I don't know if this was what u meant me to do? I had no idea how to update AODDriver2.sys, it wasn't clear to me at all.

When I was using sfc /scannow, it didn't fix all problems, so I put sfcdetails.txt aswell in the attachments, as did I with the BSODs I had over the last few days.

I didn't gain any problems with chkdisk.

My System SpecsSystem Spec
.

30 Mar 2013   #12

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Quote   Quote: Originally Posted by koolkat77 View Post

The following is for information purposes only. Any drivers in red should be updated/replaced/removed.

AsIO.sys Mon Apr 6 13:21:08 2009 (49D9AD64)
Asus PCProbe Utility
http://www.carrona.org/drivers/driver.php?id=AsIO.sys

ASACPI.sys Thu Jul 16 09:31:29 2009 (4A5E9F11)
Asus ATK0110 ACPI Utility (a known BSOD maker in Windows 7 and Win8). Also a part of many Asus utilities
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
Any drivers in red should be updated/replaced/removed.

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 Windows 7 systems.
Quote:
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.
Sometimes the driver remains and continues to cause BSOD's.
My System SpecsSystem Spec
31 Mar 2013   #13

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

Interesting SFC details there.
SFC managed to repair all but one error, but the unrepaired error is of a type which could be caused by other problems.
Please run the Windows Update Posting Instructions and post the requested data - it will give more background to possible corruption than is visible from the details.txt file.
My System SpecsSystem Spec
.


03 Apr 2013   #14

Windows 7 Home Premium x64
 
 

I have removed AsIO through deivce manager. Also I didn't see AODDRIVER, and i believe I have updated ATAKPCI utility already. I am still getting BSODs though, so this isn't the solution. I did what NoelDP asked and i have uploaded my BSODs of the meantime.
My System SpecsSystem Spec
03 Apr 2013   #15

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

Thanks.
The CheckSUR is interesting as well
I'm not even going to try to address the IE10-related problems, since MS is attempting to produce a patch/fix for these, and I haven't seen the particular one you have before..

It did also show the following problems, though...
Code:
Checking Component Store
(f) CSI Payload File Missing 0x00000000 Amd64\EP0NOE8F.DXT amd64_prnep00d.inf_31bf3856ad364e35_6.1.7600.16385_none_ae3f8d47fad9c2a7 
(f) CSI Payload File Missing 0x00000000 Amd64\EP0NOJ8F.DXT amd64_prnep00d.inf_31bf3856ad364e35_6.1.7600.16385_none_ae3f8d47fad9c2a7 
(f) CSI Payload File Missing 0x00000000 Amd64\EP0NOE8H.DXT amd64_prnep00d.inf_31bf3856ad364e35_6.1.7600.16385_none_ae3f8d47fad9c2a7 
(f) CSI Payload File Missing 0x00000000 Amd64\EP0NOJ8H.DXT amd64_prnep00d.inf_31bf3856ad364e35_6.1.7600.16385_none_ae3f8d47fad9c2a7
These belong to an Epson printer- and are from the original disk. It's possible that they were 'cleaned' by an overly-aggressive cleanup tool.

The CBS log is even more interesting this time....
Code:
 Line 53931: 2013-04-03 18:57:04, Info                  CSI    00000330 [SR] Repairing 8 components
 Line 53932: 2013-04-03 18:57:04, Info                  CSI    00000331 [SR] Beginning Verify and Repair transaction
 Line 53933: 2013-04-03 18:57:04, Info                  CSI    00000332 [SR] Cannot repair member file [l:36{18}]"Amd64\EP0NOE8F.DXT" of prnep00d.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 53934: 2013-04-03 18:57:04, Info                  CSI    00000333 [SR] Cannot repair member file [l:36{18}]"Amd64\EP0NOJ8F.DXT" of prnep00d.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 53935: 2013-04-03 18:57:04, Info                  CSI    00000334 [SR] Cannot repair member file [l:36{18}]"Amd64\EP0NOE8H.DXT" of prnep00d.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 53936: 2013-04-03 18:57:04, Info                  CSI    00000335 [SR] Cannot repair member file [l:36{18}]"Amd64\EP0NOJ8H.DXT" of prnep00d.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
 Line 53939: 2013-04-03 18:57:04, Info                  CSI    00000337 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"iesetup.dll" from store
 Line 53942: 2013-04-03 18:57:04, Info                  CSI    00000339 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"ieuinit.inf" from store
 Line 53945: 2013-04-03 18:57:04, Info                  CSI    0000033b [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:24{12}]"iernonce.dll" from store
 Line 53957: 2013-04-03 18:57:05, Info                  CSI    00000340 [SR] Repairing corrupted file [ml:520{260},l:76{38}]"\??\C:\Program Files\Internet Explorer"\[l:14{7}]"pdm.dll" from store
 Line 53960: 2013-04-03 18:57:05, Info                  CSI    00000342 [SR] Repairing corrupted file [ml:520{260},l:76{38}]"\??\C:\Program Files\Internet Explorer"\[l:20{10}]"msdbg2.dll" from store
 Line 53969: 2013-04-03 18:57:05, Info                  CSI    00000346 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:32{16}]"iernonce.dll.mui" from store
 Line 53972: 2013-04-03 18:57:05, Info                  CSI    00000348 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:30{15}]"iesetup.dll.mui" from store
In addition to the 4 Epson files, there are a number of IE-related problems - compare them with the previous run...
Code:
2013-03-30 16:01:06, Info                  CSI    00000354 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\nl-NL"\[l:32{16}]"iernonce.dll.mui" from store
2013-03-30 16:01:06, Info                  CSI    00000356 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\nl-NL"\[l:30{15}]"iesetup.dll.mui" from store
2013-03-30 16:01:06, Info                  CSI    0000035a [SR] Repairing corrupted file [ml:520{260},l:88{44}]"\??\C:\Program Files (x86)\Internet Explorer"\[l:14{7}]"pdm.dll" from store
2013-03-30 16:01:06, Info                  CSI    0000035c [SR] Repairing corrupted file [ml:520{260},l:88{44}]"\??\C:\Program Files (x86)\Internet Explorer"\[l:20{10}]"msdbg2.dll" from store

Some are the same files - and some are different.

I suspect malware is at work here.

I'll post a fix protocol for the Epson files later - but you need to do some deep checks for malware.
I'll also see if I can glean any more information out of the logs
My System SpecsSystem Spec
03 Apr 2013   #16

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

I've uploaded a file - rj1aa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\rj1aa
hit the enter key - if you get a 'Not Found' error try
DIR D:\rj1aa

or
DIR E:\rj1aa


The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\rj1aa <drive>:\windows\winsxs /y /i /s /v /h

(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply


My System SpecsSystem Spec
04 Apr 2013   #17

Windows 7 Home Premium x64
 
 

I did ur steps, the cmd window didn't say anything about problems that couldn't be fixed after that! This seems positive to me, attached the cbs txt file.
My System SpecsSystem Spec
04 Apr 2013   #18

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

I don't see Driver Verifier being active during any of these crashes so far (unless I'm missing some). Koolkat did mention previously that while you said DV was on, the crashdumps said it wasn't. Remember that you must click the 'Finish' button after setting everything up in Driver Verifier and then you need to restart the system cleanly. If the system does not at least shut down cleanly during the restart process, all settings in DV are lost. If DV isn't already causing a boot loop on the system, you can check to see if it's on by going back into it and selecting "Display existing settings". If no drivers are listed, then DV is off.

I'd like some crashdumps generated when DV is active. Remember, if DV causes a boot loop, you can enter Safe Mode and disable it from there.

Analysts:

Crashes consistently show faults that are caused by a corruption of a memory address, notably the top half of the address is getting fudged:

Code:
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880098a0118
Arg3: fffff8800989f970
Arg4: fffff800030e2b6b

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

EXCEPTION_RECORD:  fffff880098a0118 -- (.exr 0xfffff880098a0118)
ExceptionAddress: fffff800030e2b6b (nt!MmUnmapViewInSystemCache+0x000000000000014b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800989f970 -- (.cxr 0xfffff8800989f970)
rax=ff00fa8007f42120 rbx=fffffa800b9b65d0 rcx=0000000000000000
rdx=0000000000af8e0a rsi=0000000000000000 rdi=fffff6fcc0195000
rip=fffff800030e2b6b rsp=fffff880098a0350 rbp=fffffa800a7b9b50
 r8=fffffa80079658d0  r9=fffff98032a00000 r10=fffffa8007f420a0
r11=fffff8a000095940 r12=0000000000000000 r13=0000000000000000
r14=fffffa80057c7050 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!MmUnmapViewInSystemCache+0x14b:
fffff800`030e2b6b 4c3910          cmp     qword ptr [rax],r10 ds:002b:ff00fa80`07f42120=????????????????
Resetting default scope

...
This kind of corruption always appears in this same position, though sometimes a random word value appears instead of 00. I've not been able to trace back far enough with these minidumps to determine where things went wrong, so I cannot ascertain whether a driver bug went in and smeared it, or whether some hardware issue swooped in and smacked it ugly during operation. I would need at least a kernel dump to figure this, though Driver Verifier will probably be a better option at the moment. Notably, this seems to occur frequently with file operations, so perhaps the disk is involved. Again, DV might assist us in finding the root.
My System SpecsSystem Spec
04 Apr 2013   #19

Windows 7 Home Premium x64
 
 

Hey, it is true that I haven't uploaded anything with DV on.

The reason for this is because when i had put DV on, I didn't get the full bsod. My PC crashed as it does with a BSOD, but it doesn't go to the blue screen and reboots after, it got stuck on the crash thing. Do you understand what i mean? I can try to enable DV again, but I am not sure it will help. But because it doesn't get to the blue screen, it doesn't create a dump files and thus I couldn't upload a dump file with DV on.
My System SpecsSystem Spec
04 Apr 2013   #20

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

So it freezes before it even displays a blue screen, or it's actually displaying the blue screen but doesn't generate a crashdump, and it just gets stuck on that screen? If the latter, provide the bugcheck code and its four parameters shown on the blue screen, and any module name (e.g. baddriver.sys) mentioned. That at least will give us something.

Ultimately, though, what sounds like is happening is the DV checks are altering the environment enough where some file filter driver is bugging out even moreso than it already is, preventing even KiBugCheckEx from doing disk I/O. So whatever is involved in the disk device stack is responsible. Contemplate on what programs you have installed that involve watching or interacting with disk activity as they could be potential causes. That's a pretty generic definition, but at least it may lead us somewhere.

If DV doesn't work, at least a kernel dump of your latest crash may give us some clues. It's MEMORY.DMP located in Windows directory. Archive it and upload to 3rd party filesharing site.
My System SpecsSystem Spec
Reply

 Recent Bsods happening at random





Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:29 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33