Blue screen daily

[blackwillie]

Hello Fred,
maybe we are!!
=)
I raised the verifier and pointed me to a file that causes the dump
the file is asopio.sys
in other sites indicate a possible problem with this file, so I uninstalled all programs asus supplied (those of AI II suit).
I raised the verifier without selecting that file, and the pc NO crashed.
=)
the file is still physically in the PC, but I do not think it is used by any program.
Now I run the PC for a while 'and I keep you updated ...
thank you very much
If you have ideas or suggestions let me know
=)

 

[FredeGail]

Excellent news. Glad this driver shows up now. If it still shows after the uninstallation, you might want to take a look at this--

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, asopio.sys, or in general AI II Suit (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 asopio.sys driver and rename it to asopio.BAD

Then reboot and see if it's removed.

 

[blackwillie]

nothing ...
has just crashed ...
I do not know where to turn ...
I'm really tired ...
= (

I feel, however, to completely uninstall AI II ... but I do not think that's the problem because the new dump file did not indicate that

 

[blackwillie]

I ran autoruns and found no more file asopio.sys
uninstallation must have had an effect ... but the dump is ... I do not know what to do ...
if it was the RAM, buy the pen again and just ... I do not know what the hell is ...

 

[blackwillie]

I reactivated the verifier ...
now is active and has not crashed ...
the system will feel a little '"burdened" with the verifier on ...
=)
I hope to be able to give me more info to see what the problem is ...
as suggerivi, I keep active a couple of days in hopes of finding the possible cause of the crush ... but I do not know if it will help ...
=(

 

[blackwillie]

a new funny crash!
=)
the second in under 30 minutes!
This time it was active verifier ... but gave no new information ...
are at the end ...
= (
buy new RAM?
I do not know what to do!!

 

[FredeGail]

Have you tried a 32-bit system?

Ubuntu
For a trial, try downloading a copy of Ubuntu and see if your system will crash.
By that, we'd have an idea if Windows 7's drivers and system is broken. You can try it out on a
flash drive if you so desire.
Go to Ubuntu.com | Download the image | See how to create a bootable flash drive
Leave it running for some time and report your results.

Best Regards,
Frederik.

 

[blackwillie]

Hello Fred,
I contacted Corsair (supplier of ram) and they told me to turn on XMP mode in bios.
I turned on (I now correctly detects the ram to 1866) and I launched memtest ... for over 5 hours!!
=)
did not find any problem ...

At this point, I would rule out the ram with some confidence ...

Another possible "guilty" could be the motherboard ... I requested a contact from ASUS to get some suggestions from them and when I say something I must tell you ...
From last dump file last night (the one with the "verifier" active) you could not find anything interesting?

 

[FredeGail]

Hello again!

Glad you got XMP enabled. The previous crash did not reveal anything dramatic. Have you had any crashes since then? And is your verifier still on?

Best Regards,
Frederik.

 

[blackwillie]

Hello Fred,
since then (crossing fingers (I do not know if it is used as an expression)) is no longer crashed ...
the "verifier" I turned off (I slowed down a bit 'pc) but if you think it might help the revived ...
do you think is better?

 

[FredeGail]

Hello again!

If corsair gave you those recommendations, maybe your issues are fixed, who knows. Let verifier be turned off as it does more harm than good right now. Computers may be a bit sluggish and slow after those BSOD nightmares, rule number one is just to use it. It works like a human sickness. Imagine you've been ill, and then turn fresh again. It's not many cases that you're completely fresh afterwards.
Windows will place sectors in order, sort of like an automatic defrag -- that'd make your computer faster over time. Just use your computer as you're used to, without doing demanding things such as hardcore gaming.

Crossed fingers is a common expression, I certainly has mine crossed. BTW Corsair is probably one of the best communities of support, they'd gladly aid your system as it has been proven earlier.

Good job mate!
Frederik.

 

[blackwillie]

Hello Fred,
crash again ... they were two days that did not happen ...
I reactivated the verifier if recapitalization ... we'll see if it says something more ...
Anyway I ran memtest for 6 hours in a row and the ram has no problem ...
cmq I think it's a hardware problem ...

 

[blackwillie]

hi fred...
i have a stamp of last error (take with bluescreen viewer...

important?

 

[blackwillie]

from bluescreen viewer tell me that the error came from adress "ntoskrnl.exe+7f1c0"
is the same for the last 4 dump...what is it?

 

[FredeGail]

BSOD ANALYSE

DRIVER_VERIFIER_VIOLATION

_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000118, Handle value being referenced.
Arg3: fffffa8010c84060, Address of the current process.
Arg4: fffff88004f6f766, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  PEUpdater.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000374e3dc to fffff800032c81c0

STACK_TEXT:  
fffff880`0a9d7448 fffff800`0374e3dc : 00000000`000000c4 00000000`000000f6 00000000`00000118 fffffa80`10c84060 : nt!KeBugCheckEx
fffff880`0a9d7450 fffff800`03763ae4 : 00000000`00000118 fffffa80`10c84060 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a9d7490 fffff800`0351aff0 : 00000000`00000000 fffff880`0a9d76c0 00000000`00000000 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`0a9d7570 fffff800`0359df65 : 00000000`00000000 0000007f`000f001f 00000000`00000000 fffff800`032e5200 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0a9d7640 fffff800`03763878 : 00000000`00000001 00000000`00000002 fffff880`0a9d7730 fffff800`032c3a10 : nt!ObReferenceObjectByHandle+0x25
fffff880`0a9d7690 fffff880`04f6f766 : 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`0374e14e : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a9d76e0 00000000`00000000 : 00000000`00000002 00000000`00000001 fffff800`0374e14e fffff880`0a9d7768 : AsUpIO+0x1766


STACK_COMMAND:  kb

FOLLOWUP_IP: 
AsUpIO+1766
fffff880`04f6f766 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  AsUpIO+1766

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AsUpIO

IMAGE_NAME:  AsUpIO.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c57835f

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_AsUpIO+1766

BUCKET_ID:  X64_0xc4_f6_VRF_AsUpIO+1766

Followup: MachineOwner
---------
0: kd> !thread
GetPointerFromAddress: unable to read from fffff800034f7000
THREAD fffffa8010c84b50  Cid 0d5c.0d68  Teb: 000000007efdb000 Win32Thread: fffff900c21fec20 RUNNING on processor 0
IRP List:
    Unable to read nt!_IRP @ fffff98017362ee0
Not impersonating
GetUlongFromAddress: unable to read from fffff80003436ba4
Owning Process            fffffa8010c84060       Image:         PEUpdater.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      2332         
Context Switch Count      389            IdealProcessor: 0                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x0000000000402456
Stack Init fffff8800a9d7c70 Current fffff8800a9d6e80
Base fffff8800a9d8000 Limit fffff8800a9d0000 Call 0
Priority 6 BasePriority 6 UnusualBoost 0 ForegroundBoost 0 IoPriority 1 PagePriority 3
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0a9d7448 fffff800`0374e3dc : 00000000`000000c4 00000000`000000f6 00000000`00000118 fffffa80`10c84060 : nt!KeBugCheckEx
fffff880`0a9d7450 fffff800`03763ae4 : 00000000`00000118 fffffa80`10c84060 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a9d7490 fffff800`0351aff0 : 00000000`00000000 fffff880`0a9d76c0 00000000`00000000 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`0a9d7570 fffff800`0359df65 : 00000000`00000000 0000007f`000f001f 00000000`00000000 fffff800`032e5200 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0a9d7640 fffff800`03763878 : 00000000`00000001 00000000`00000002 fffff880`0a9d7730 fffff800`032c3a10 : nt!ObReferenceObjectByHandle+0x25
fffff880`0a9d7690 fffff880`04f6f766 : 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`0374e14e : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a9d76e0 00000000`00000000 : 00000000`00000002 00000000`00000001 fffff800`0374e14e fffff880`0a9d7768 : AsUpIO+0x1766

0: kd> dps fffff8800a9d0000 fffff8800a9d8000
fffff880`0a9d7448  fffff800`0374e3dc nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0a9d7450  00000000`000000c4
fffff880`0a9d7458  00000000`000000f6
fffff880`0a9d7460  00000000`00000118
fffff880`0a9d7468  fffffa80`10c84060
fffff880`0a9d7470  fffff880`04f6f766 AsUpIO+0x1766
fffff880`0a9d7478  00000000`00000018
fffff880`0a9d7480  fffffa80`10c84060
fffff880`0a9d7488  fffff800`03763ae4 nt!VfCheckUserHandle+0x1b4
fffff880`0a9d7490  00000000`00000118
fffff880`0a9d7498  fffffa80`10c84060
fffff880`0a9d74a0  00000000`00000002
fffff880`0a9d74a8  00000000`00000000
fffff880`0a9d74b0  fffff880`04f6f766 AsUpIO+0x1766
fffff880`0a9d74b8  00000000`00000000
fffff880`0a9d74c0  fffff8a0`0000e8b0
fffff880`0a9d74c8  00000000`00000020
fffff880`0a9d74d0  fffff800`0359df65 nt!ObReferenceObjectByHandle+0x25
fffff880`0a9d74d8  fffff800`03763878 nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a9d74e0  fffff880`04f6f766 AsUpIO+0x1766
fffff880`0a9d74e8  fffff880`04f6fe59 AsUpIO+0x1e59
fffff880`0a9d74f0  fffff800`0376ac16 nt!IovCallDriver+0x566
fffff880`0a9d74f8  fffff800`035de717 nt!IopXxxControlFile+0x607
fffff880`0a9d7500  fffff800`035def76 nt!NtDeviceIoControlFile+0x56
fffff880`0a9d7508  fffff800`032c7453 nt!KiSystemServiceCopyEnd+0x13
fffff880`0a9d7510  fffff880`0010000e
fffff880`0a9d7518  fffff880`0a9d7520
fffff880`0a9d7520  00740063`00650053
fffff880`0a9d7528  0000006e`006f0069
fffff880`0a9d7530  fffffa80`10c84b50
fffff880`0a9d7538  fffff800`032c7453 nt!KiSystemServiceCopyEnd+0x13
fffff880`0a9d7540  00000000`00000000
fffff880`0a9d7548  00000000`00000000
fffff880`0a9d7550  ffffc205`8f8094bc
fffff880`0a9d7558  fffff780`00000000
fffff880`0a9d7560  fffffa80`10c84b50
fffff880`0a9d7568  fffff800`0351aff0 nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`0a9d7570  00000000`00000000
fffff880`0a9d7578  fffff880`0a9d76c0
fffff880`0a9d7580  00000000`00000000
fffff880`0a9d7588  00000000`00000000
fffff880`0a9d7590  00000000`0033d896
fffff880`0a9d7598  00000000`00000100
fffff880`0a9d75a0  00000000`00004481
fffff880`0a9d75a8  00000000`00000001
fffff880`0a9d75b0  fffff880`0a9d7600
fffff880`0a9d75b8  fffff800`033c7b22 nt!MmAllocateSpecialPool+0x722
fffff880`0a9d75c0  00000000`00000863
fffff880`0a9d75c8  00000000`00000963
fffff880`0a9d75d0  00000003`3d896963
fffff880`0a9d75d8  00000000`00000001
fffff880`0a9d75e0  fffffa80`000a19a0
fffff880`0a9d75e8  00000000`00000000
fffff880`0a9d75f0  0df00000`035de121
fffff880`0a9d75f8  00000000`00000000
fffff880`0a9d7600  00000000`00000000
fffff880`0a9d7608  fffff980`192aafe0
fffff880`0a9d7610  00000000`000f001f
fffff880`0a9d7618  00000000`00000118
fffff880`0a9d7620  00000000`00000000
fffff880`0a9d7628  00000000`00000000
fffff880`0a9d7630  00000000`000f001f
fffff880`0a9d7638  fffff800`0359df65 nt!ObReferenceObjectByHandle+0x25
fffff880`0a9d7640  00000000`00000000
fffff880`0a9d7648  0000007f`000f001f
fffff880`0a9d7650  00000000`00000000
fffff880`0a9d7658  fffff800`032e5200 nt!MiDispatchFault+0x920
fffff880`0a9d7660  00000000`746c6644
fffff880`0a9d7668  fffff880`0a9d76c0
fffff880`0a9d7670  00000000`00000000
fffff880`0a9d7678  fffff880`0a9d7ae0
fffff880`0a9d7680  00000000`c0000002
fffff880`0a9d7688  fffff800`03763878 nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0a9d7690  00000000`00000001
fffff880`0a9d7698  00000000`00000002
fffff880`0a9d76a0  fffff880`0a9d7730
fffff880`0a9d76a8  fffff800`032c3a10 nt!KiServiceLinkage
fffff880`0a9d76b0  fffff880`0a9d76c0
fffff880`0a9d76b8  00000000`00000000
fffff880`0a9d76c0  00000000`00000000
fffff880`0a9d76c8  fffff980`17362fb0
fffff880`0a9d76d0  fffff980`192aafe0
fffff880`0a9d76d8  fffff880`04f6f766 AsUpIO+0x1766
fffff880`0a9d76e0  00000000`00000000
fffff880`0a9d76e8  00000000`00000002
fffff880`0a9d76f0  00000000`00000001
fffff880`0a9d76f8  fffff800`0374e14e nt!VfMajorVerifyIrpStackDownward+0xae
fffff880`0a9d7700  fffff880`0a9d7768
fffff880`0a9d7708  00000000`00000000
fffff880`0a9d7710  00000000`00000000
fffff880`0a9d7718  fffff800`00000000
fffff880`0a9d7720  fffffa80`00000001
fffff880`0a9d7728  fffffa80`124c50d8
fffff880`0a9d7730  00000000`00000118
fffff880`0a9d7738  fffff800`00000000
fffff880`0a9d7740  fffffa80`10c825d0
fffff880`0a9d7748  fffff800`035de717 nt!IopXxxControlFile+0x607
fffff880`0a9d7750  00000000`00000000
fffff880`0a9d7758  fffff800`03766bcc nt!IovpCallDriver1+0x51c
fffff880`0a9d77c0  fffff880`04f6f980 AsUpIO+0x1980
fffff880`0a9d77c8  00000000`00000000
fffff880`0a9d77d0  00000000`00000000
fffff880`0a9d77d8  00000000`00000001
fffff880`0a9d77e0  00000000`00000001
fffff880`0a9d77e8  fffffa80`10ae53c0
fffff880`0a9d77f0  fffff980`17362ee0
fffff880`0a9d77f8  00000000`00000001
fffff880`0a9d7800  00000000`c0000002
fffff880`0a9d7808  fffff880`04f6fe59 AsUpIO+0x1e59
fffff880`0a9d7810  00000000`00000001
fffff880`0a9d7818  fffffa80`00000001
fffff880`0a9d7820  fffffa80`00000001
fffff880`0a9d7828  fffff800`035de717 nt!IopXxxControlFile+0x607
fffff880`0a9d7830  fffff880`0a9d78e8
fffff880`0a9d7838  fffff800`037572a7 nt!VfIrpAllocateCallDriverData+0x47
fffff880`0a9d7868  fffff800`0376ac16 nt!IovCallDriver+0x566
fffff880`0a9d78c8  fffff800`035de717 nt!IopXxxControlFile+0x607
fffff880`0a9d79f8  fffff800`035def76 nt!NtDeviceIoControlFile+0x56
fffff880`0a9d7a68  fffff800`032c7453 nt!KiSystemServiceCopyEnd+0x13
fffff880`0a9d7ad8  fffff800`032c7453 nt!KiSystemServiceCopyEnd+0x13

AsUpIO.sys caused. Uninstall ASUS hardware monitoring software.

Best Regards,
Frederik.

 

[blackwillie]

Hello Fred,
I uninstalled, arrested and locked services "asus" and rename the file in asupio.sys asupio.bck ...
I leave the verifier active in the coming days and see if the problem reoccurs ...
asus programs are uninstalled all but the files were not removed ... I do not know if there is a more effective method to uninstall ...
now, however, let him turn a bit 'so and see if the problem reoccurs!
thank you very much!!
=)

 

[FredeGail]

Great! Here's a little side-note on removing drivers. In this case it's sptd.sys but it's just the general idea of it.

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, Sptd, or in general Daemon Tools (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 sptd.sys driver and rename it to sptd.BAD

Then reboot and see if it's removed.

Best Regards,
Frederik.

 

[blackwillie]

Hello Fred,
crash again =)
the verifier was active, but does not give me additional information ... I am attaching the file. rar ...
= (
the bluescreen viewer does not tell me anything new ... the usual ...
you say you do?

thank you very much

 

[FredeGail]

Disable verifier.

Best Regards,
Frederik.

 

[blackwillie]

Only disable verifier?
why?
was that to generate the crash?
=)