New
#21
I don't have Alcohol 120%, how do I uninstall ci.dll with this Revo program?
I don't have Alcohol 120%, how do I uninstall ci.dll with this Revo program?
I have looked at the remaining six dumps from today. One of the was a Driver Verifier enabled dump that pointed to CI.dll as the cause as mentioned in the post above. The remaining five dumps are error code 1A and point to memory corruption.
Nothing specific is shown in the dumps.STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
We will wait to see what your system does after you address the problems in the post above.Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSOD.zip\Windows7_BSOD_jcgriff2\080810-9172-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e93e50 Debug session time: Sun Aug 8 11:44:52.528 2010 (GMT-4) System Uptime: 0 days 0:03:27.636 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa8001245150, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa8001245150 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: WerFault.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002d39ede to fffff80002cc6600 STACK_TEXT: fffff880`083a1828 fffff800`02d39ede : 00000000`0000001a 00000000`00041790 fffffa80`01245150 00000000`0000ffff : nt!KeBugCheckEx fffff880`083a1830 fffff800`02cf9cc9 : 00000000`00000000 000007fe`fbfe5fff fffffa80`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33946 fffff880`083a19f0 fffff800`02fe0170 : fffffa80`038c6110 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`083a1b10 fffff800`02fe057b : 00000000`00000000 000007fe`fbf90000 fffffa80`00000001 fffffa80`052dc0d0 : nt!MiUnmapViewOfSection+0x1b0 fffff880`083a1bd0 fffff800`02cc5853 : fffffa80`05350060 fffff880`083a1ca0 fffffa80`03904060 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f fffff880`083a1c20 00000000`77bbfffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000ba778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bbfffa STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+33946 fffff800`02d39ede cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946 BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSOD.zip\Windows7_BSOD_jcgriff2\080810-9796-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50 Debug session time: Sun Aug 8 11:49:20.224 2010 (GMT-4) System Uptime: 0 days 0:03:47.707 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa8001283e50, ffff, 0} Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa8001283e50 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002cfcede to fffff80002c89600 STACK_TEXT: fffff880`08535538 fffff800`02cfcede : 00000000`0000001a 00000000`00041790 fffffa80`01283e50 00000000`0000ffff : nt!KeBugCheckEx fffff880`08535540 fffff800`02cbccc9 : 00000000`00000000 00000000`05dc1fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33946 fffff880`08535700 fffff800`02fa3170 : fffffa80`04fe7790 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`08535820 fffff800`02fa357b : 00000000`00000000 00000000`058f0000 fffffa80`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b0 fffff880`085358e0 fffff800`02c88853 : 00000000`05d07000 00000000`00000000 fffffa80`04cf4060 fffff880`08535b50 : nt!NtUnmapViewOfSection+0x5f fffff880`08535930 fffff800`02c84df0 : fffff960`000d4a5c fffff880`08535ca0 fffffa80`04cf3b60 00000000`000bdeb8 : nt!KiSystemServiceCopyEnd+0x13 fffff880`08535ac8 fffff960`000d4a5c : fffff880`08535ca0 fffffa80`04cf3b60 00000000`000bdeb8 fffff880`08535bd0 : nt!KiServiceLinkage fffff880`08535ad0 fffff800`02c88853 : 00000000`56010b74 00000000`00000238 00000000`00000000 00000000`00000000 : win32k!NtGdiCreateDIBSection+0x3e4 fffff880`08535bb0 00000000`731a056a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000bde98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x731a056a STACK_COMMAND: kb FOLLOWUP_IP: win32k!NtGdiCreateDIBSection+3e4 fffff960`000d4a5c 488bcf mov rcx,rdi SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: win32k!NtGdiCreateDIBSection+3e4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4bdc4376 FAILURE_BUCKET_ID: X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4 BUCKET_ID: X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4 Followup: MachineOwner ---------
ci.dll is a Windows driver and should not be messed with. When the dump blames a Windows driver, it is often symptomatic of another issue.
What ci.dll does is unknown to me, but I don't want you to mess anything up by messing with it.
This is what I get when I try to do that... [attached image]
Thank you, Jonathan. Interesting, I found two references via Google that showed it to be part of Alcohol. I will remember that. I appreciate it.
Genomcide, disregard ci.dll. This means two more Driver Verifier enabled dumps pointed to Windows files. We will have start looking elsewhere.
Took a shot in the dark and tried to just reseat my RAM and see if I saw any improvement. So far no BSOD *crosses fingers*
Very good thinking; I should have thought to suggest that. I hope you have no more BSOD's. :)
Uh oh, issue is back and I'm running out of ideas.
Attached is the new dumps.
If the information helps... I didn't turn off the system for about 2-3 days and it ran FINE. This morning I did shut down and I turned it on after I got home from work. Then I started getting repeat BSODs again.
Edit: I also just flashed the newest BIOS version from ASUS. Maybe that will help too?
Last edited by Gnomicide; 10 Aug 2010 at 18:38.
Hmm...no new dumps in that report. Could you empty out your C:\Windows\Minidump folder, then manually upload any new dumps that occur?
https://www.sevenforums.com/tutorials...en-forums.html