Windows 8 Random freezes + BSODs

M

mimi123

Active member
Joined
Nov 12, 2012
Posts
30
Well, my PC freezes sometimes, random.
It can be working many hours well or freezes two or more times in an hour.
Sometimes stop it and did not show BSOD. When this , mouse, keyboard and screen freeze and reset button did not work. I must to power off pressing power button for some seconds.
I use this PC as HTPC, watch videos, music, TV, web...


My system:

· OS - Vista/ Windows 7 ? Now Windows 8 (tested on Windows 7 and freezes too)
· x86 (32-bit) or x64 ? Always x64
· What was original installed OS on system?Fresh install. Format, then install.
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full retail
· Age of system (hardware) Less than one year.
· Age of OS installation - have you re-installed the OS? One month, always fresh install.

· CPU Intel i7 2700K
· Video Card Integrated i7 (HD3000)
· MotherBoard ASRock Z68 Professional Gen3 Fatal1ty
· Power Supply - brand & wattage Corsair TX650 650wats

· System Manufacturer None
· Exact model number (if laptop, check label on bottom) None


-Memory 2x4GB G Skill RipjawsX F3-17000CL9-4GBXM (tested for 12 hours)
-Hard disk system Now Corsair Force 3 SSD 120GB (tested and last firmware) SO installed for test with another hd (Samsung HD204ui) and freeze too.
-Hard disk for data Now Samsung HD204ui. Tested with none and same results.
-TV card Pinnacle PCTV DVB-T Dual PCI
-Optical drive Optiarc BD RW BD-5300S ATA Device


View attachment Windows7_Vista_jcgriff2.zip

Drivers and BIOS updated. I don´t know how to resolve this situation.
I activate driver verifier, I did it by following the steps in this forum, and crash more often and many times.

Sorry for if I forgot something.

Very thanks.
 
Re: Random freezes + BSODs

Hi -

Intel graphics driver listed as probable cause in most dumps -
Code: 
[font=lucida console]igdkmd64.sys                Wed Oct 17 15:12:29 2012 (507F031D)
[/font]
http://www.sysnative.com/drivers/driver.php?id=igdkmd64.sys

I wonder if this video related driver is causing problems for Intel -
Code: 
RoyalTS64.sys               Thu Sep 14 02:23:12 2006 (4508F550)
Update the driver or remove the software for now.

http://carrona.org/drivers/driver.php?id=RoyalTS64.sys

Remove Elby and any other virtual devices until the problems are solved.

Video card, RAM or other hardware failure are also candidates.

If you have an SSD, check manufacturer's support site for a firmware upgrade.

Regards. . .

jcgriff2


BSOD SUMMARY

Code: 
[font=lucida console]
Debug session time: Mon Nov 12 10:08:00.831 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111212-15968-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 0 days 15:22:58.139
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
BugCheck 1000007E, {ffffffffc0000005, fffff880044b835e, fffff88002df0788, fffff88002deffc0}
Probably caused by : igdkmd64.sys ( igdkmd64+23b35e )
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880044b835e, The address that the exception occurred at
Arg3: fffff88002df0788, Exception Record Address
Arg4: fffff88002deffc0, Context Record Address
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_VRF_igdkmd64+23b35e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 11 18:44:43.036 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111212-15578-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 0 days 0:11:21.710
BugCheck 50, {fffff8a00859dc10, 1, fffff88004d6107c, 0}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+32b07c )
Bugcheck code 00000050
Arguments: 
Arg1: fffff8a00859dc10, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88004d6107c, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_VRF_igdkmd64+32b07c
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 11 18:33:03.177 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111212-15562-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 0 days 0:08:40.851
BugCheck 116, {fffffa800a466010, fffff88004240550, ffffffffc0000001, 3}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+f550 )
Bugcheck code 00000116
Arguments: 
Arg1: fffffa800a466010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004240550, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_igdkmd64.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 11 18:24:03.344 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111212-15421-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 0 days 0:08:39.018
BugCheck 116, {fffffa800a94e010, fffff880048e5550, ffffffffc0000001, 3}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+f550 )
Bugcheck code 00000116
Arguments: 
Arg1: fffffa800a94e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048e5550, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_igdkmd64.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 11 18:15:05.638 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111212-15468-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 0 days 0:08:44.312
BugCheck 116, {fffffa800c2644d0, fffff88004486550, ffffffffc0000001, 3}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+f550 )
Bugcheck code 00000116
Arguments: 
Arg1: fffffa800c2644d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004486550, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_igdkmd64.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 11 18:06:03.090 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111212-15484-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 0 days 0:08:40.763
BugCheck 116, {fffffa800b0254d0, fffff880042b4550, ffffffffc0000001, 3}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+f550 )
Bugcheck code 00000116
Arguments: 
Arg1: fffffa800b0254d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880042b4550, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_igdkmd64.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 11 17:57:03.688 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111112-15390-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 0 days 0:08:36.362
BugCheck 116, {fffffa800c2054d0, fffff88004a72550, ffffffffc0000001, 3}
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+f550 )
Bugcheck code 00000116
Arguments: 
Arg1: fffffa800c2054d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004a72550, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_VRF_IMAGE_igdkmd64.sys
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Nov 11 13:04:34.766 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\111112-14218-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 1 days 6:10:26.208
BugCheck 133, {1, 780, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
Bugcheck code 00000133
Arguments: 
Arg1: 0000000000000001
Arg2: 0000000000000780
Arg3: 0000000000000000
Arg4: 0000000000000000
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x133
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x133_nt!_??_::FNODOBFM::_string_+13ca8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Nov  3 18:19:16.937 2012 (GMT-5)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\110412-8828-01.dmp]
Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
System Uptime: 0 days 3:29:26.044
BugCheck 133, {1, 780, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
Bugcheck code 00000133
Arguments: 
Arg1: 0000000000000001
Arg2: 0000000000000780
Arg3: 0000000000000000
Arg4: 0000000000000000
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x133
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x133_nt!_??_::FNODOBFM::_string_+13ca8
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

         
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=http://mvp.microsoft.com/profiles/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   

           [url=https://www.sysnative.com/forums/member.php/1-jcgriff2][color=#000033][u]jcgriff2 - Sysnative Forums[/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/FONT]
 
Thanks for your reply.

I suspect from graphics too.

RoyalTS64 and Elby removed.
Graphics driver is the latest.
SSD updated with last firmware and I run chkdsk as I read in this forum.

How can I force the BSOD?
 
Now crash one more time. TV card and drivers removed. Elby uninstalled. Graphics drivers 2875, latest.

No BSOD only freeze.

I read any for event viewer but I don´t know if this image is usefull:


eventviewer.jpg

If you need more data or to do anything, tell me, I am at your disposal.

Very thanks for your help.
 
Last edited:
How are temps?

How often does the freezing occur?

Any pattern to it?

Any spikes prior to freezes - CPU, RAM, ..?

Keep RESMON up -
START | type resmon
 
How are temps?
Low, all well refrigerated.
How often does the freezing occur?
One or two on a day.
Any pattern to it?
No, sometimes watching a film with MediaPlayer, sometimes with Firefox, sometimes doing nothing.
Any spikes prior to freezes - CPU, RAM, ..?
I think no. My system is very over sized. I´m stressing the system with prime95, Fumark and CrystalDiskMark and all run OK.

Keep RESMON up -
START | type resmon OK now up.
 
I´m lost. When I stress my computer did not crash.
I did not know what or how to do to cause failure. Now the system is working for more than 3 hours, but I have not done anything to fix it.
The system will fail again for sure.

My system stressed:

Stress test.jpg

Very thanks for your patience.
 
Temps look great under Prime95.

This seems like hardware failure, but run Driver Verifier again - 36 hours minimum.

Did you/other build the system, i.e., it's not am OEM store system?
 
Temps look great under Prime95.

This seems like hardware failure, but run Driver Verifier again - 36 hours minimum. OK. I configure Verifier like this: http://www.techsupportforum.com/forums/f299/driver-verifier-windows-8-windows-7-and-vista-bsod-related-473665.html

But there is not any option like "Concurrentcy Stress Test" in my Windows 8, it seems to be an error.



Is like this OK?

Verifier settings.jpg

Did you/other build the system, i.e., it's not am OEM store system? I bought the parts and mounted it myself.

If it is hardware failure I need to know the bad part to solve the problem.

Now running Driver verifier...

Very thanks.
 
The system crash (BSOD) every time I run TotalMedia5.
Driver ARCSEC.sys failed.

I unistalled TMT5 and continue running Driver Verifier.
 
Now the system is up and running well. No BSOD and no freeze.

Windows Update found 11 updates and need to Restart the system to apply changes.

Restarting...
 
Stressing my system, for more than two hours, and did not crash:

AIDA64 Stress.jpg

Now I´m testing power off-on, hibernate, suspend and all programs I use normally, except programs related to TV card (is not installed yet), TMT5 and Elby.
 
I report the issue of ArcSec.sys to Arcsoft.

Sorry I did not understand this. What do you want to say with "I really have a hard time believing that Intel's driver is faulty." Do you think the Intel´s driver is causing problems or NOT?


My system is stable for the last 24 hours, no crash, no BSOD, no freeze.

I will wait 12 hours more and then I want to install the TV card, TMT5 and Elby.
Any suggestion on how to do? Install one and then another or all at one time? Sequence? Add the new drivers to Driver Verifier?

Very thanks for your help, I´m very grateful.
 
Last edited:
mimi123 said:
Sorry I did not understand this. What do you want to say with "I really have a hard time believing that Intel's driver is faulty." Do you think the Intel´s driver is causing problems or NOT?
Click to expand...

Hi -

I DO NOT believe Intel's drivers are causing a problem as it is really unheard of for newly written Intel drivers to be flagged by Driver Verifier.

It is my theory that the Intel driver was a victim here of another 3rd party driver clashing (adversely interacting) with Intel, leaving Intel to take the blame, so-to-speak.

I'm glad to hear of BSOD-free status and also that the freezing has subsided & of course hope this continues.

Regards. . .

jcgriff2
 
Thanks for the clarification and sorry for my English. Now I understand you perfectly.

At this moment the system is up and running well for more than 36 hours.
I think is the moment for add the TV card and add these drivers to Driver Verifier too.

Your comments are very helpful. :thumbsup2:

Regards.
 
Arcsoft reply to the incidence with ArcSec.sys:

Hello Mimi,

Thank you for contacting ArcSoft. It's Josie to help.
Regarding your concern, it seems that some programs on your computer had interfered the core file of TMT. The ArcSec.sys file is set for the protection of TMT. So if it detects any abnormal condition with TMT, this file can protect the core files from being cracked. We would recommend you to have a check of your system to see if you have installed programs such as antivirus, programming softwares which might occupy the TMT files or have conflit with TMT. Please try to uninstall them to see if your case is fixed.

We hope this information helps. Please feel free to contact us if you have any other questions.
Wish you a nice day!
Best Regards,
ArcSoft Support
11/15/2012 12:58:17 AM
Click to expand...


Now I´m testing the TV card, later I will take up the issue with TotalMedia.
 
Last edited by a moderator:
Hi Mimi -

mimi123 said:
... The ArcSec.sys file is set for the protection of TMT. So if it detects any abnormal condition with TMT, this file can protect the core files from being cracked..
Click to expand...

I'm not sure what they are implying here as I can't imagine what they think would "crack" core files. I assume they mean "crack" as in "modify"...? It sounds absurd to suggest that a 3rd party protection driver is needed in a Windows 8 system. There are conditions where drivers attempt to access memory they should not, but no actual modification can take place with an x64 device driver.

ArcSoft TotalMedia5 utilizes the PCTV DVB-Tuner..?

Which PCTV DVB-T device do you have?

http://www.pctvsystems.com/tabid/62.../Driver/tabid/123/language/en-GB/Default.aspx

The one thing I did notice on that page is that there are no Windows 8 drivers listed. This may be a case of incompatibility.

I did find this ArcSoft EXE running in the original files provided in post #1 -
Code: 
eservutil	1.0.0.33	42.60 KB (43,624 bytes)	8/14/2012 5:31 PM	ArcSoft, Inc.
	c:\program files (x86)\common files\arcsoft\esinter\bin\eservutil.exe

Is ArcSoft or PCTV aware that you are running Windows 8? Did they say the drivers listed on the support page are Windows 8 compatible?

Did Driver Verifier actually flag ArcSec.sys?

mimi123 said:
The system crash (BSOD) every time I run TotalMedia5.
Driver ARCSEC.sys failed.

I unistalled TMT5 and continue running Driver Verifier.
Click to expand...

http://www.carrona.org/drivers/driver.php?id=ArcSec.sys

I would suggest re-running Driver Verifier again and see if it flags ArcSec.sys.

Please feel free to zip up the dump & attach so we can have a look. :)

Regards. . .

jcgriff2
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top