Windows 8 Random freezes + BSODs

jcgriff2 said:
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..? No, I use Windows Media Center.

Which PCTV DVB-T device do you have? PCTV Dual DVB-T Pro PCI (2000i)

[TD="align: left"][/TD]
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. No there isn´t Windows 8 drivers. I install windows 7 drivers, run Driver Verifier for more than 24 hours and all is OK (TMT5 not installed yet).

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? I never contact with PCTV. Arcsoft TotalMedia 5 is Windows 8 compatible.

Did Driver Verifier actually flag ArcSec.sys? Is uninstalled.
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.

Driver Verifier is continuosly working for two days. I´m adding suspects malfunction software (Elby, TV card drivers and TMT5) one by one and adding all new drivers (not Microfsoft) to Driver Verifier.

I install Totalmounter and the system crash. Then uninstall Totalmounter and install Daemon tools. At this moment all is OK, with Driver Verifier working.

In a few hours I will install TMT5 and add new drivers to Driver Verifier.

I will post results.


Please feel free to zip up the dump & attach so we can have a look. :) Of course here they are:
View attachment 3 Windows7_Vista_jcgriff2.zip

Last four BSODs are caused by Totalmounter.

Regards. . .

jcgriff2
Click to expand...
 
Daemon tools (DAEMONToolsPro520-0348) did not work when I use this PC by remote desktop.

I have uninstalled Daemon and install Virtual Clone (SetupVirtualCloneDrive5450). Fingers closed and drivers added to Driver Verifier :rofl12:

For now all is well.

Testing the system...
 
mimi123 said:
jcgriff2 said:
Please feel free to zip up the dump & attach so we can have a look. :)
Click to expand...

Of course here they are:
View attachment 2518

Last four BSODs are caused by Totalmounter.
Click to expand...

Hi Mimi -

Very nice -- Thank you for the VERIFIER_ENABLED dumps & for running them and providing the answers too!!

Code: 
[font=lucida console]KSPrt64.sys                 Thu Aug 25 18:52:43 2011 (4E56D23B)[/font]
http://carrona.org/drivers/driver.php?id=KSPrt64.sys

Can I help with anything here? :lol:

Virtual devices have been involved with BSODs going back to Vista. This is a new one for me to see. I usually find Daemon, Alcohol, Elby involved; often not actually named as the probable cause, but Driver Verifier got this one.

Great work!

I hope you find one that works for you.

Regards. . .

John
 
TMT5 installed. Every time I run TMT5 I have a BSOD referred to ArcSec.sys.

I uninstall Virtual Clone reboot and TMT5 crash the same.

I try to disable TV card and I get a BSOD referred to Tv card drivers. I had to remove TV card drivers from Driver Verifier to disable TV card. I don´t know if this is normal but if TV card works OK I will never have to disable it.

Well, without TV card the same. Every time I run TMT5 I have a BSOD from Arsec.sys.

I like TMT5 but for the moment I uninstall it. I think my system is stable without TMT5.

Data at this moment View attachment 4 Windows7_Vista_jcgriff2.zip

Any suggestions?
 
Did they say this driver was compatible with Windows 8 x64?

Code: 
4: kd> [B]lmvm RoyalTS64[/B]
start             end                 module name
fffff880`057d8000 fffff880`057fd200   RoyalTS64   (no symbols)           
    Loaded symbol image file: RoyalTS64.sys
    Image path: \SystemRoot\system32\DRIVERS\[COLOR="#FF0000"]RoyalTS64.sys[/COLOR]
    Image name: RoyalTS64.sys
    Timestamp:        Thu [COLOR="#FF0000"]Sep 14[/COLOR] 02:23:12 [COLOR="#FF0000"]2006 [/COLOR](4508F550)
    CheckSum:         00028FF9
    ImageSize:        00025200
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

https://www.sysnative.com/drivers/driver.php?id=RoyalTS64.sys

It was written while XP SP2 was the latest version of Windows.

Driver Verifier flags it every time with a 0xc4 bugcheck.

The solution here is that they need to update that driver for Windows 8 x64 & stop telling people that the 2006 version works.

-- Just my opinion.
 
Last edited:
Now I can not enable TV card. Windows says (Can not find the required files)

I restore the system to the point before installing TMT5 and all is OK.

Windows Update find an interesting update:

Update for Windows 8 for x64-based Systems (KB2756872)

Download size: 162.9 MB

You may need to restart your computer for this update to take effect.

Update type: Important

Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.

More information:
http://support.microsoft.com/kb/2756872

Help and Support:
http://support.microsoft.com
Click to expand...

Installing and testing...

Regards.
 
jcgriff2 said:
Did they say this driver was compatible with Windows 8 x64? No, they say it is compatible with Windows 7 x64. This driver only crash when I try to disable it, to test TMT5, while it was running Driver Verifier.

Code: 
4: kd> [B]lmvm RoyalTS64[/B]
start             end                 module name
fffff880`057d8000 fffff880`057fd200   RoyalTS64   (no symbols)           
    Loaded symbol image file: RoyalTS64.sys
    Image path: \SystemRoot\system32\DRIVERS\[COLOR=#FF0000]RoyalTS64.sys[/COLOR]
    Image name: RoyalTS64.sys
    Timestamp:        Thu [COLOR=#FF0000]Sep 14[/COLOR] 02:23:12 [COLOR=#FF0000]2006 [/COLOR](4508F550)
    CheckSum:         00028FF9
    ImageSize:        00025200
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

https://www.sysnative.com/drivers/driver.php?id=RoyalTS64.sys

It was written while XP SP2 was the latest version of Windows. Upps! :banghead:

Driver Verifier flags it every time with a 0xc4 bugcheck.

The solution here is that they need to update that driver for Windows 8 x64 & stop telling people that the 2006 version works. Yes :thumbsup2:

-- Just my opinion.
Click to expand...
 
jcgriff2 said:
•Improved application and driver compatibility with Windows 8
Click to expand...

You never know!

After the kb installs - please run perfmon /report - does it say anything about the device?
Click to expand...

Perfmon report is very different now. I think all is OK.

What do you think?

Now I´m running Driver Verifier to test all well.
What is the problem for running Driver Verifier all the time?
 

Attachments

PERFMON is not showing any errors.

Would you please run msinfo32 - save as an NFO file; zip up & attach?

Thanks,

John
 
mimi123 said:
Yes the question is: how long run Driver Verifier? And why not forever?
Click to expand...

You can run Driver Verifier anytime you wish. I usually recommend a minimum of 24-36 hours. You can always check status -
- 1st screen "Display information about drivers being verified...."
- from a CMD prompt -
Code: 
verifier /query

Driver Verifier is very system resource intensive, so running it 24/7 is likely to slow your system down. Furthermore, there is no reason to continually run it, especially in your case as we know it will force a BSOD on - https://www.sysnative.com/drivers/driver.php?id=RoyalTS64.sys


RE: msinfo32 - thank you for the NFO file.

You can see the app crashes and BSODs by expanding "Software Environment"; select "Windows Error Reporting". A few selected entries -
Code: 
11/17/2012 01:16    Windows Error Reporting    Fault bucket [COLOR=blue]0xc4_f6_VRF_ArcSec[/COLOR]+28a4e, type 0
Event Name: [COLOR=blue]BlueScreen[/COLOR]
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\111612-19296-01.dmp
C:\Users\Miguel Angel\AppData\Local\Temp\WER-34234-0.sysdata.xml
C:\Users\Miguel Angel\AppData\Local\Temp\WER3FB9.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_03bc400c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 111612-19296-01
Report Status: 0
Hashed bucket:
11/17/2012 00:58    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: No disponible
Cab Id: 0

Problem signature:
P1: x64
P2: [COLOR=red]PCI\VEN_11BD&DEV_0041&SUBSYS_004411BD&REV_00[/COLOR]
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_ee323aa840f047bd4325c181c1198b434ed85c71_03f194e6

Analysis symbol: 
Rechecking for solution: 0
Report Id: e3cd2031-3051-11e2-beb8-002522dc4c46
Report Status: 4
Hashed bucket:
11/17/2012 00:58    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: No disponible
Cab Id: 0

Problem signature:
P1: x64
P2: [COLOR=red]PCI\VEN_11BD&DEV_0042&SUBSYS_004411BD&REV_00[/COLOR]
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_24568592d1623e3fcb7f9b1979cd139e631483_03f194c7

Analysis symbol: 
Rechecking for solution: 0
Report Id: e3cd2030-3051-11e2-beb8-002522dc4c46
Report Status: 4
Hashed bucket:
11/16/2012 23:52    Windows Error Reporting    Fault bucket [COLOR=blue]0xc4_f6_VRF_ArcSec[/COLOR]+28a4e, type 0
Event Name: [COLOR=blue]BlueScreen[/COLOR]
Response: Not available
Cab Id: 0

Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
C:\Windows\Minidump\111612-19296-01.dmp
C:\Users\Miguel Angel\AppData\Local\Temp\WER-34234-0.sysdata.xml
C:\Windows\MEMORY.DMP
C:\Users\Miguel Angel\AppData\Local\Temp\WER3FB9.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0d464c28

Analysis symbol: 
Rechecking for solution: 0
Report Id: 111612-19296-01
Report Status: 384
Hashed bucket:
11/16/2012 23:29    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: No disponible
Cab Id: 0

Problem signature:
P1: x64
P2: [COLOR=red]PCI\VEN_11BD&DEV_0042&SUBSYS_004411BD&REV_00[/COLOR]
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_24568592d1623e3fcb7f9b1979cd139e631483_03846daa

Analysis symbol: 
Rechecking for solution: 0
Report Id: 84588404-3045-11e2-beb7-002522dc4c46
Report Status: 4
Hashed bucket:
11/16/2012 23:29    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: No disponible
Cab Id: 0

Problem signature:
P1: x64
P2: [COLOR=red]PCI\VEN_11BD&DEV_0041&SUBSYS_004411BD&REV_00[/COLOR]
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_ee323aa840f047bd4325c181c1198b434ed85c71_03846daa

Analysis symbol: 
Rechecking for solution: 0
Report Id: 84588403-3045-11e2-beb7-002522dc4c46
Report Status: 4
Hashed bucket:
11/16/2012 23:29    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: No disponible
Cab Id: 0

Problem signature:
P1: x64
P2: [COLOR=red]PCI\VEN_11BD&DEV_0040&SUBSYS_004411BD&REV_00[/COLOR]
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_ce7dc1177949fcaeff5d5099bd6b19986573c8b_03846d9b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 84588402-3045-11e2-beb7-002522dc4c46
Report Status: 4
Hashed bucket:
11/16/2012 23:26    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: No disponible
Cab Id: 0

Problem signature:
P1: x64
P2: [COLOR=red]PCI\VEN_11BD&DEV_0042&SUBSYS_004411BD&REV_00[/COLOR]
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_24568592d1623e3fcb7f9b1979cd139e631483_0381778c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 10a90b53-3045-11e2-beb7-002522dc4c46
Report Status: 4
Hashed bucket:
1. blue = BSODs - bugcheck 0xc4 (0xf6,,,) = Driver Verifier detected a violation
2. Scroll to the right and you'll see entries like this in red - recorded because Windows is looking for a driver for the device --
Code: 
PCI\VEN_11BD&DEV_0041&SUBSYS_004411BD&REV_00
PCI\VEN_11BD&DEV_0040&SUBSYS_004411BD&REV_00
PCI\VEN_[COLOR=#FF0000]11BD[/COLOR]&DEV_[COLOR=#FF0000]0042[/COLOR]&SUBSYS_004411BD&REV_00

Looking up that info:
Code: 
Vendor = [B]11bd[/B]
Device = [B]0042[/B]

PCI DB confirms the Vendor ID as Pinnacle systems - http://www.pcidatabase.com/vendor_details.php?id=975

Microsoft Update Catalog - http://catalog.update.microsoft.com...updateid=d3f3afc2-7f40-4280-8639-d46459fbe264

- shows a Windows XP x64 era driver -
Code: 
Description: Pinnacle Systems Sound sofware update released in August, 2006 
Architecture: AMD64 
Classification: Drivers 
Supported products: [COLOR=#FF0000]Windows XP 64-Bit Edition Version 2003 [/COLOR]
Supported languages: English

Code: 
Company: Pinnacle Systems 
Driver Manufacturer: Pinnacle Systems 
Driver Class: Other Hardware 
Driver Model: Pinnacle PCTV DVB-T Dual Common 
Driver Provider: Pinnacle Systems 
Version: 4.[COLOR=#FF0000]0.5.0 [/COLOR]
Version Date: [COLOR=#FF0000]8/17/2006 [/COLOR]
More information: 
[URL]http://winqual.microsoft.com/support/?driverid=20006263[/URL] 
Support Url: n/a


A cab file named AMD64-en-20006263_2774214e05d9bf7dc97cd3c0d3ebcb73e109e497.cab is downloaded to folder -
Pinnacle Systems - Sound - Pinnacle PCTV DVB-T Dual Common
​

Inside the CAB file - the 2006 x64 drivers for Windows XP -
Code: 
royalts64.cat	8556  	08/22/2006	14:20:18	A	
[COLOR="#FF0000"]RoyalTS64.sys[/COLOR]	195072	08/17/2006	10:46:22	A	
RoyalTS64.inf	6470  	08/17/2006	10:39:04	A
https://www.sysnative.com/drivers/driver.php?id=RoyalTS64.sys

Contents of the INF file:
Read More:

I'm sorry, but I don't see other options for you with this device + Windows 8.

Regards. . .

jcgriff2
 
Thanks for all.


I have bad news. The system froze one time. I have not new BSOD. How can I determine the cause?

I´m thinking to buy a new TV DVB card if we are sure the problem is this.

At this point I install and uninstall many programs, have many BSODs freezes etc... It is a good idea to format and to do a fresh install or maybe wait until we find out what is the cuse of the freeze?
 
Hi -

If you are in a position where reinstalling Windows 8 x64 is not a major inconvenience, I would do so.

I think a fresh install, given all you've tested in this thread alone would likely help us figure out if hardware or software is the culprit.

Upon reaching Desktop, allow ALL Windows updates to install -

www.update.microsoft.com

If the system freezes during that time, hardware failure is the likely cause.

Did the system come with Windows 7 x64?

Regards. . .

jcgriff2
 
OK
I will do a fresh install of Windows8 x64, no problem.

The system come with none OS. Before I installed Windows7 x64 and I had problems too, I think the same than with W8.
But here the big question...
If my problem is hardware related, how can I determine the bad part?
Maybe TV card, but how can I be sure?
 
Windows 8x64 fresh install done. All Windows updates installed. No freeze and no BSOD. Is my hardware OK?

I think now is a good time to make a hard disk image.

At this time...

Unknown devices:
1- ACPI\VEN_INT&DEV_33A0
2- PCI\VEN_11BD&DEV_0041&SUBSYS_004411BD&REV_00
3- PCI\VEN_11BD&DEV_0040&SUBSYS_004411BD&REV_00
4- PCI\VEN_11BD&DEV_0042&SUBSYS_004411BD&REV_00

And some drivers are outdated.


I´m looking for new drivers and installing them.
 
Unknown devices:
  1. Intel Smart Connect Technology Device
  2. Pinnacle Systems PCTV tuner Device
  3. Pinnacle Systems PCTV tuner Device
  4. Pinnacle Systems PCTV tuner Device
 
writhziden said:
Unknown devices:
  1. Intel Smart Connect Technology Device
  2. Pinnacle Systems PCTV tuner Device
  3. Pinnacle Systems PCTV tuner Device
  4. Pinnacle Systems PCTV tuner Device
Click to expand...

Very Thanks Writhziden.

If I do not use "Intel Smart Connect Technology Device" and to avoid BSODs, is it better to install these drivers or not necessary?
 

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

Back
Top