Windows 7: Experiencing many BSOD, with random errorcodes

NeedCoffee · 23 Aug 2012

Hello,
Since the last couple of weeks i have had multiple BSOD wich appear to be random. De errorcode involved changes a lot, and i cant remember seeing the same one twice.
There have been no hardware changes, and i am about to give up and do a fresh reinstall of Windows. Before i do however i thought i try to get some wise people to look at it, just in case it turns out to be something rather simple, and a reinstall is not needed. I have read the "how to post" bit and am including the zip file of the latest BSOD.
Could the problem be due to a failing Graphics card?

Apologies for any grammar mistakes as english is not my native language, but i'll do my best

Arc · 23 Aug 2012

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000116797, Address of the instruction which caused the bugcheck
Arg3: fffff8800a76d010, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!GdiProcessCallout+237
fffff960`00116797 088d15f2d620    or      byte ptr [rbp+20D6F215h],cl

CONTEXT:  fffff8800a76d010 -- (.cxr 0xfffff8800a76d010)
rax=0000000000000000 rbx=0000000000000f2c rcx=fffff900c200fdd8
rdx=0000000000000001 rsi=fffff900c200fce0 rdi=fffff900c200fce0
rip=fffff96000116797 rsp=fffff8800a76d9f0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff88006957578 r12=fffffa800f5d6b30 r13=fffffa800ae4dd50
r14=0000000000000001 r15=fffffa800f5d6c90
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
win32k!GdiProcessCallout+0x237:
fffff960`00116797 088d15f2d620    or      byte ptr [rbp+20D6F215h],cl ss:0018:00000000`20d6f216=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff96000115ea3 to fffff96000116797

STACK_TEXT:  


CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    fffff96000116797 - win32k!GdiProcessCallout+237
    [ 48:08 ]
1 error : !win32k (fffff96000116797)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff8800a76d010 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

System device driver fails, most probably it all is caused by memory fault.
I would suggest you to run

NeedCoffee · 23 Aug 2012

Thanks for responding, and taking the time to look into it.

I assume the tests need to be done in this order?
Test will be ran, at the earliest possibility, and i will post the outcome back here...

Arc · 23 Aug 2012

No need to maintain any order, but I would suggest you to run the memtest at first. If memtest fails to detect any thing, then go for the other two tests.

NeedCoffee · 23 Aug 2012

After running Furmark for 45 mins there didnt seem to be a problem (temp min 75C, temp max 93C, fan 56%)
Then i ran Prime95 and within 5 mins had a BSOD

(file added)
I will run memtest overnight, but these tests i could run now, so i did ....

FredeGail · 23 Aug 2012

Information

Jump-in by a request from Arc.

BSOD Analyse

I believe I may have found your issue. You have the pre-2009 version of ASACPI installed. This is the number one BSOD causer you can find within third party drivers.

Quote:

Driver Description
Asus ATK0110 ACPI Utility (a known BSOD maker in Windows 7). Also a part of the Asus PCProbe and AISuite Utilities
Driver Reference Table - ASACPI.sys

Code:

ASACPI.sys Thu Jul 16 05:31:29 2009 (4A5E9F11)

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
7: kd> lmvm ASACPI
start             end                 module name
fffff880`04d9c000 fffff880`04da4000   ASACPI     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
    Image name: ASACPI.sys
    Timestamp:        Thu Jul 16 05:31:29 2009 (4A5E9F11)
    CheckSum:         00010BC2
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Best Regards,
Frederik.

Arc · 23 Aug 2012

Well done, my friend

NeedCoffee · 23 Aug 2012

I really hope you are right, since it sounds like an easy thing to fix. Since i dont use these mentioned programs anymore (and haven't been for a long time) and they are not in my program list anymore. I will try to google it and see what I need to do next, but if you can tell me what would be the best thing, i will not hold it against you

FredeGail · 23 Aug 2012

You should be able to find either of the software I mentioned in the description in your Control Panel (Add and Remove Programs).

*Go ahead and delete the software that belongs to the driver.
*See if it's still located in \SystemRoot\system32\DRIVERS\ASACPI.sys, if yes--

Safely Remove Drivers:

To remove this safely, please do the following:
- ensure that you have a bootable DVD to use to get into Startup Repair (the Win8 installation DVD will do). If you don't have one, then use this procedure to create a System Repair disk: System Repair Disc - Create in Windows 8
- set a System Restore point (to use with the System Repair disk if you can't get back into Windows).

- download this free program: Autoruns for Windows Use it to disable any entries that has the name, ASACPI, or in general the mentioned software, see description (by removing the checkmark in the far left column)
- check for any services related to this driver and/or program (use services.msc) and disable them
- check in Device Manager (use devmgmt.msc) for any devices related to this driver and/or program. Make sure to enable the viewing of hidden devices. Uninstall any that you find. DO NOT rescan or reboot yet!
- search your system for the ASACPI.sys driver and rename it to ASACPI.BAD

Then reboot and see if it's removed.

Cheers,
Frederik.

NeedCoffee · 23 Aug 2012

Thanks again for your time and guidance. I have gone trough all the steps mentioned, and I cant find and any remains of the forementioned files and/or programs. When checking the Device Manager however, there is a yellow exlamation mark at an "unknown device" wich according to the Hardware-id is the ATK0110. For now i have disabled the device, since removing it does not seem to do anything. Hopefully there will be no more BSOD for a while, and will I be able to mark this thread as solved!

Windows 7: Experiencing many BSOD, with random errorcodes

Experiencing many BSOD, with random errorcodes problems?