CTL.DLL BSOD

#1
TYPO I meant CTL.DLL ERROR BSOD View attachment Windows_NT6_BSOD_jcgriff2.zip [HR][/HR]Just got a news system built and am getting a CTL.dll error whenever I turn on my HDMI display ...not sure what is doing it.... I have attached the dump file as a zip..help is greatly appreciated.

Windows 7 64 bit Ultimate retail
All new hardware
OS build Service Pack 1 less than a month

I have attached my dump file and the system file checker results and any help is appreciatted... one thing to note is the system file checker results I get a
Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted


Thank you for your help
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#2
Re: TYPO I meant CTL.DLL BSOD

I am not the expert here, those folks normally hang out in the BSOD forum, but one may drop by.

Until then, each of your dump files seems to show a problem with memory being access incorrectly. Along those lines there are some drivers you might want to check. Each of these may not be part of the problem, but do look a little strange.

SSPORT.sys
GVTDrv64.sys
gdrv.sys

Ssport is a fairly recent driver, but show up as started, but not showing a good location in you system info report.
The other two are older and also do not show a good location and both show running.

I do not see what they are doing, but you might check around and see what is starting them up.

Did you load a driver for the HDMI, if you need to..?
 


Captain Jack

Extraordinary Member
#3
Re: TYPO I meant CTL.DLL BSOD

Hello there,

It would be nice if you just follow the instructions from one of the websites. Because there aren't lot of BSOD analyst and the ones used to visit different websites. It would be a waste of time for two people working on same issue.

TYPO I meant CTL.DLL ERROR BSOD - Windows 7 Forums
 


#4
Re: TYPO I meant CTL.DLL BSOD

I do have all the latest drivers for my NVIDIA GeForce GTX 550 ... sorry I am somewhat of a newbie..does this mean an issue woith my memory (the Ram) or the drivers for the video card..you think afull reinstall, clean install or repair may fix the issue????
 


Captain Jack

Extraordinary Member
#5
Hello there,

Seems like few things are going on.

Run a Hardware Diagnostic Hardware Diagnostic | Captain Debugger (RAM and Hard drive)
If your Overclocking please reset to default values
Uninstall any third party Firewall / Internet Security as if now.


GVTDrv64.sys Tue Sep 05 03:10:02 2006
dsNcAdX64.sys Tue Jun 19 12:17:32 2007 - Network Connect VPN software by Juniper Networks Customer Support Center - Juniper Networks. If you cannot update this driver, uninstall the software. It is obsolete.

Code:
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffffffa8009c4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003301e14, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003500100
 fffffffffa8009c4 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiResolveTransitionFault+124
fffff800`03301e14 488b00          mov     rax,qword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  fffff88005a5f5c0 -- (.trap 0xfffff88005a5f5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffffa8009c4 rbx=0000000000000000 rcx=0000000000000004
rdx=0000000fffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003301e14 rsp=fffff88005a5f750 rbp=fffff8a00a3f2010
 r8=ffffffffffffffff  r9=00000001ab86b880 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiResolveTransitionFault+0x124:
fffff800`03301e14 488b00          mov     rax,qword ptr [rax] ds:0fff:ffffffff`fa8009c4=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d02a9 to fffff800032d0d00

STACK_TEXT:  
fffff880`05a5f478 fffff800`032d02a9 : 00000000`0000000a ffffffff`fa8009c4 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`05a5f480 fffff800`032cef20 : 00000000`00000000 fffff800`00000002 fffff880`08000000 00000001`ab86b880 : nt!KiBugCheckDispatch+0x69
fffff880`05a5f5c0 fffff800`03301e14 : 00000000`00000000 fffffa80`0a6410b0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`05a5f750 fffff800`032ef6f5 : 00000000`00000000 00000001`ab86b880 fffffa80`0a874440 fffffa80`0996dec8 : nt!MiResolveTransitionFault+0x124
fffff880`05a5f7e0 fffff800`032ee0b3 : 00000000`0011f3a1 00000000`00830150 fffff680`00004180 fffffa80`0996dec8 : nt!MiResolveProtoPteFault+0x325
fffff880`05a5f870 fffff800`032ddf69 : 00000000`00000000 00000000`00830150 00000000`02f5e368 fffff800`00000000 : nt!MiDispatchFault+0x1c3
fffff880`05a5f980 fffff800`032cee2e : 00000000`00000000 00000000`00830150 00000000`00000001 00000000`744d2828 : nt!MmAccessFault+0x359
fffff880`05a5fae0 000007fe`fd67117a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`02f5e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd67117a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiResolveTransitionFault+124
fffff800`03301e14 488b00          mov     rax,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiResolveTransitionFault+124

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+124

BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+124
 


#6
Re: TYPO I meant CTL.DLL BSOD

Hello there,

It would be nice if you just follow the instructions from one of the websites. Because there aren't lot of BSOD analyst and the ones used to visit different websites. It would be a waste of time for two people working on same issue.

TYPO I meant CTL.DLL ERROR BSOD - Windows 7 Forums
Sorry I did see the link..all the best to you
 


#8
Re: TYPO I meant CTL.DLL BSOD

I have read online that ctl.dll may be a virus ...is that correct???
 


Captain Jack

Extraordinary Member
#9
Re: TYPO I meant CTL.DLL BSOD

It's possible you could find that file under C:\Windows\System32 go ahead and copy that file and upload it to VirusTotal - Free Online Virus, Malware and URL Scanner it will tell you if that file is infected or not. Also download Malwarebytes and run a complete scan under Safe Mode
 


#10
Re: TYPO I meant CTL.DLL BSOD

Could havng that virus or the that file cause a BSOD???

Thank you once again for all your help
 


Captain Jack

Extraordinary Member
#11
Re: TYPO I meant CTL.DLL BSOD

Viruses can cause BSOD. So Yes it's possible.
 


#12
Re: TYPO I meant CTL.DLL BSOD

Viruses can cause BSOD. So Yes it's possible.
Missing my Mac more and more ...no ...oops there are viruses for MAc LOL...
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top