BSOD bugcheck 0x00000050 (0xfffffa8004ffddd0, 0x0000000000000000,

[Putt4Dough]

Hello,

My windows 7 Pro 64b is crashing and I cannot seem to find why.

Here are the logs. I looked over them but cannot seem to find what is making my PC crash once or twice a day. Please help.

Regards,

 

[Arc]

Hello Putt4Dough.

Your crash dumps are not showing any finite probable cause.

Which antivirus do you use? Scan the system for possible virus infection with the following programs only.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If both of these two comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
________________________________________________________________________
BSOD ANALYSIS:

.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8004ffddd0, 0, fffff80003bc7a5c, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8004ffddd0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003bc7a5c, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cf8100
GetUlongFromAddress: unable to read from fffff80003cf81c0
 fffffa8004ffddd0 Nonpaged pool

FAULTING_IP: 
nt!MiEmptyPageAccessLog+dc
fffff800`03bc7a5c 488b08          mov     rcx,qword ptr [rax]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  TmListen.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800315c8c0 -- (.trap 0xfffff8800315c8c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004ffddd0 rbx=0000000000000000 rcx=0000000000000038
rdx=fffff8a009fa3838 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003bc7a5c rsp=fffff8800315ca50 rbp=0000000000000000
 r8=fffffa8004240008  r9=fffffa8001a39048 r10=fffffa80047aa920
r11=fffffa8004784c80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiEmptyPageAccessLog+0xdc:
fffff800`03bc7a5c 488b08          mov     rcx,qword ptr [rax] ds:fffffa80`04ffddd0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003b3d5d4 to fffff80003ac0c00

STACK_TEXT:  
fffff880`0315c758 fffff800`03b3d5d4 : 00000000`00000050 fffffa80`04ffddd0 00000000`00000000 fffff880`0315c8c0 : nt!KeBugCheckEx
fffff880`0315c760 fffff800`03abed2e : 00000000`00000000 fffffa80`04ffddd0 fffff680`00397d00 00000000`00023408 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`0315c8c0 fffff800`03bc7a5c : 00000000`00000000 fffffa80`047aa960 00000000`00000002 fffff800`03c3c4f0 : nt!KiPageFault+0x16e
fffff880`0315ca50 fffff800`03b41f63 : fffffa80`04246060 00000003`00000000 00000000`00023408 fffffa80`04ffddd0 : nt!MiEmptyPageAccessLog+0xdc
fffff880`0315cac0 fffff800`03aaab16 : 00000000`000062cb 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4c84b
fffff880`0315cb40 fffff800`03aaafc3 : 00000000`00000008 fffff880`0315cbd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`0315cb90 fffff800`03d5eede : fffffa80`0180a660 00000000`00000080 fffffa80`017e3840 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`0315cd00 fffff800`03ab1906 : fffff800`03c3be80 fffffa80`0180a660 fffff800`03c49cc0 f7ff2dfb`de5f6f77 : nt!PspSystemThreadStartup+0x5a
fffff880`0315cd40 00000000`00000000 : fffff880`0315d000 fffff880`03157000 fffff880`0315c6c0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiEmptyPageAccessLog+dc
fffff800`03bc7a5c 488b08          mov     rcx,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiEmptyPageAccessLog+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiEmptyPageAccessLog+dc

BUCKET_ID:  X64_0x50_nt!MiEmptyPageAccessLog+dc

Followup: MachineOwner
---------

 

[Putt4Dough]

Hi,

Thanks for the quick reply. I took some time to test all of this thus the reason for the re post delay.

I use Trend AV up to date and works like a charm.
TDSSKILLER found nothing---Clean PC
Windows Defender Offline full scan found nothing --- Clean PC
Memtes86+ 8 passes no errors and no crashes during the testing.

I’m running Driver verifier now. Will post the results tomorrow.

 

[Putt4Dough]

Hi,

The system was unresponsive after a while following the DV enabled. The screen was black and the mouse and keyboard were unresponsive. I got BSOD at normal reboot. I had to use last know good config to boot up successfully. Here are my new logs. Can you see anything with this new info?

 

[Arc]

Hi,

The system was unresponsive after a while following the DV enabled. The screen was black and the mouse and keyboard were unresponsive. I got BSOD at normal reboot. I had to use last know good config to boot up successfully. Here are my new logs. Can you see anything with this new info?

The crash dump present in the zip contains one new crash dump only, which is not DV enabled. Probably you are failing to get to the desktop with DV enabled.

If you try to enable DV again, dont check any driver provided by "microsoft" and "unknown".

BTW, as per Carrona.org, STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

These tow precautions we should take, I guess.

Uninstall Trend Micro. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Your BIOS version is

BiosVersion = 1102   
BiosReleaseDate = 05/27/2009

You may plan to update to Beta Version 1301 dated 2013.03.28 or Version 1208 dated 2010.07.09; from http://www.asus.com/Motherboards/P5QEM_DO/#support_Download_24

   Warning

BIOS Update is a risky process, and any interruption during the process may damage the motherboard. Take the help of somebody who is aware of such things, or any technician.

:warn: Whatever, you are entering to a BIOS update at your own risk.

Let us know the results.
____________________________________________________________________
BSOD ANALYSIS:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff683fff9fe98, 0, 0, fffff80003a6856b}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff683fff9fe98, memory referenced
Arg2: 0000000000000000, 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: fffff80003a6856b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cb6100
GetUlongFromAddress: unable to read from fffff80003cb61c0
 fffff683fff9fe98 Nonpaged pool

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiAgeWorkingSet+1d1
fffff800`03a6856b 488b19          mov     rbx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031b0780 -- (.trap 0xfffff880031b0780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff683fff9fe98
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a6856b rsp=fffff880031b0910 rbp=00000003fff9fe9e
 r8=0000000000000001  r9=fffffa80017a5c28 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiAgeWorkingSet+0x1d1:
fffff800`03a6856b 488b19          mov     rbx,qword ptr [rcx] ds:fffff683`fff9fe98=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a7e1a9 to fffff80003a7ec00

STACK_TEXT:  
fffff880`031b0638 fffff800`03a7e1a9 : 00000000`0000000a fffff683`fff9fe98 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`031b0640 fffff800`03a7ce20 : 00000000`00000000 fffff683`fff9fe98 00000000`00001000 00000980`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031b0780 fffff800`03a6856b : 00000000`00000002 00000000`00000001 fffff880`031b0b60 00000000`00000054 : nt!KiPageFault+0x260
fffff880`031b0910 fffff800`03afff15 : fffffa80`017a5c28 fffff800`00000001 00000000`00000001 fffff880`031b0b70 : nt!MiAgeWorkingSet+0x1d1
fffff880`031b0ac0 fffff800`03a68b16 : 00000000`000017ea 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
fffff880`031b0b40 fffff800`03a68fc3 : 00000000`00000008 fffff880`031b0bd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`031b0b90 fffff800`03d1cede : fffffa80`024319d0 00000000`00000080 fffffa80`017a5890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`031b0d00 fffff800`03a6f906 : fffff800`03bf9e80 fffffa80`024319d0 fffff800`03c07cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b0d40 00000000`00000000 : fffff880`031b1000 fffff880`031ab000 fffff880`031b06c0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1d1
fffff800`03a6856b 488b19          mov     rbx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+1d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1d1

BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1d1

Followup: MachineOwner
---------

 

[Putt4Dough]

DV was enable for sure but I’m guessing that since I was unable to boot in normal mode after the PC froze, I selected last know good config it might be a good config before DV was enabled. Is that possible? DV is enabled once again and selected all but MS and unknown.

I uninstalled Trend, activated Windows Defender and did a full scan. The PC was clean.
I installed MBAM and did a full scan. The PC was clean.
I honestly don’t think this is a virus or infection issue. Trend does a great job and always have. Nonetheless, it’s clean.

New Beta BIOS updated.

 

[Arc]

I am not saying that the Trend Micro did a bad job at all. I suggested to uninstall it (at least as a test) as it is one of the listed possible cause of your BSOD.

You need not to activate windows Defender (Are you using windows 8? I haven't noticed that part), but install Microsoft Security Essentials from the provided link. The Windows Defender of windows 7 is not a great program (which is not true for the windows 8 version).

If you cannot boot into desktop with DV enabled, boot into safe mode, disable DV and boot back normally ... as included in my previous instruction.

So now you can boot to desktop with DV enabled? Use the computer normally. Perform the most crash prone actions. Let it BSOD a couple of times. Then post following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Putt4Dough]

Yes Windows 7. I enabled Windows Defender while Trend is off.

I'm booted to desktop with DV enabled. No BSOD yet. I'm off for 4 day. Will be back only on Wednesday so I will repost then. Pleas don't close thread.

Have a great weekend.

 

[Arc]

Take your time

But Install Microsoft Security Essentials and Disable Windows Defender. The second one is a spyware protector only, and cannot be the alternative of a real time antivirus.

 

[Putt4Dough]

Hi,

Back after 4 days and leaving my PC running with verifier.exe since Friday. The PC was frozen when I came back, black screen, num-lock on the keyboard was on and unresponsive and the mouse was on (red laser) but unresponsive. I had to manually power off the PC and boot it up. It brought me to the boot selection menu. I selected Normal boot, logged in and a Windows message asked me to check for a solution that I cancelled. Here are the new logs following these steps.

 

[Arc]

The Crash dump you uploaded is not Driver Verifier enabled.

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

1: kd> !verifier
fffff80004c48ac0: Unable to get verifier list.

A 0xC1 BSOD is caused by memory reasons. Either failing RAM, or any driver causing memory fault.

You said you have performed the Memtest ... no RAM failure is there. I believe you.

You say you enabled DV. I am not seeing any stress of an enabled DV in the data.
Moreover, you were suggested to run DV for 24 hours or the occurrence of the next crash, whichever is earlier.You should have thought why that time stipulation is there?

Coz, if DV is not making a crash, we have to check the reasons.

Now, Enable DV again.

• When you are at the driver's list, dont select any driver provided by "microsoft" or "unknown".
• Make it sure DV is actually running. Open a command prompt and give the command
  • verifier /query
  and hit enter. Is it providing a list of drivers?
• Run it as suggested ...for 24 hours or the occurrence of the next crash, whichever is earlier.

Dont take very long to reply, as you need not to run DV for more than 24 hours. No need for 4-5 days.

If it is a failure again, we will supply you the list of drivers to select. But you have to try at first.

 

[Putt4Dough]

Yes Memtest 8 passes no errors. Tested for sure.


That’s weird because I certainly activated verifier both time. I ran it again, as you say it is not running on it now, but it is running. When I ran it, at the end I got a message saying that no changes were made so it is running. I then ran verifier /query to confirm. All the print screens and query info is in the attached word document. Why would the logs say DV is not running when it clearly is?

 

[Arc]

Yes Memtest 8 passes no errors. Tested for sure.


When I ran it, at the end I got a message saying that no changes were made so it is running.

Verifier is active when you get this message

After the restart, verifier takes place.

No changes were made ... means verifier is not running.

 

[Putt4Dough]

Did you look at the print screens? I obviously did all the procedures right an that is the message I get. "No settings were changed". to me if I go through the wizard and I get this message at the end it tells me that the setting are identical to what they are set at the moment thus it up and and running as before. Might be wrong but it's logical. The passed two times it asked me to reboot. Not this time. Just "No settings were changed".

What does query tell you bellow?

  C:\Windows\system32>verifier /query
  7/24/2013, 9:52:16 AM
  Level: 00000FBB
  RaiseIrqls: 0
  AcquireSpinLocks: 114856
  SynchronizeExecutions: 4
  AllocationsAttempted: 4697652
  AllocationsSucceeded: 4697652
  AllocationsSucceededSpecialPool: 4697652
  AllocationsWithNoTag: 39
  AllocationsFailed: 0
  AllocationsFailedDeliberately: 0
  Trims: 470210
  UnTrackedPool: 4599735
   
  Verified drivers:
   
  Name: iusb3hcs.sys, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 0
  CurrentNonPagedPoolAllocations: 0
  PeakPagedPoolAllocations: 0
  PeakNonPagedPoolAllocations: 0
  PagedPoolUsageInBytes: 0
  NonPagedPoolUsageInBytes: 0
  PeakPagedPoolUsageInBytes: 0
  PeakNonPagedPoolUsageInBytes: 0
   
  Name: amdxata.sys, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 0
  CurrentNonPagedPoolAllocations: 0
  PeakPagedPoolAllocations: 0
  PeakNonPagedPoolAllocations: 0
  PagedPoolUsageInBytes: 0
  NonPagedPoolUsageInBytes: 0
  PeakPagedPoolUsageInBytes: 0
  PeakNonPagedPoolUsageInBytes: 0
   
  Name: igdkmd64.sys, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 5
  CurrentNonPagedPoolAllocations: 652
  PeakPagedPoolAllocations: 8
  PeakNonPagedPoolAllocations: 713
  PagedPoolUsageInBytes: 274516
  NonPagedPoolUsageInBytes: 4004272
  PeakPagedPoolUsageInBytes: 309176
  PeakNonPagedPoolUsageInBytes: 4068120
   
  Name: e1k60x64.sys, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 0
  CurrentNonPagedPoolAllocations: 1040
  PeakPagedPoolAllocations: 0
  PeakNonPagedPoolAllocations: 1040
  PagedPoolUsageInBytes: 0
  NonPagedPoolUsageInBytes: 293120
  PeakPagedPoolUsageInBytes: 0
  PeakNonPagedPoolUsageInBytes: 293120
   
  Name: ndis.sys, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 6
  CurrentNonPagedPoolAllocations: 1581
  PeakPagedPoolAllocations: 8
  PeakNonPagedPoolAllocations: 1666
  PagedPoolUsageInBytes: 984
  NonPagedPoolUsageInBytes: 646184
  PeakPagedPoolUsageInBytes: 1296
  PeakNonPagedPoolUsageInBytes: 684016
   
  Name: pppop64.sys, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 0
  CurrentNonPagedPoolAllocations: 0
  PeakPagedPoolAllocations: 0
  PeakNonPagedPoolAllocations: 0
  PagedPoolUsageInBytes: 0
  NonPagedPoolUsageInBytes: 0
  PeakPagedPoolUsageInBytes: 0
  PeakNonPagedPoolUsageInBytes: 0
   
  Name: rtkvhd64.sys, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 0
  CurrentNonPagedPoolAllocations: 1038
  PeakPagedPoolAllocations: 2
  PeakNonPagedPoolAllocations: 1038
  PagedPoolUsageInBytes: 0
  NonPagedPoolUsageInBytes: 807776
  PeakPagedPoolUsageInBytes: 304304
  PeakNonPagedPoolUsageInBytes: 807776
   
  Name: atmfd.dll, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 0
  CurrentNonPagedPoolAllocations: 0
  PeakPagedPoolAllocations: 0
  PeakNonPagedPoolAllocations: 0
  PagedPoolUsageInBytes: 0
  NonPagedPoolUsageInBytes: 0
  PeakPagedPoolUsageInBytes: 0
  PeakNonPagedPoolUsageInBytes: 0
   
  Name: secdrv.sys, loads: 1, unloads: 0
  CurrentPagedPoolAllocations: 1
  CurrentNonPagedPoolAllocations: 0
  PeakPagedPoolAllocations: 3
  PeakNonPagedPoolAllocations: 0
  PagedPoolUsageInBytes: 72
  NonPagedPoolUsageInBytes: 0
  PeakPagedPoolUsageInBytes: 316
  PeakNonPagedPoolUsageInBytes: 0
   
  C:\Windows\system32>

 

[Arc]

Sorry mate. My intention is to help you, not to argue with you. Please dont think that I am passing any information without seeing ant single bit of possible data.

But if you start to think that I am saying anything without seeing the data, it seems that you are not having the needed faith on the helper. It will not reach any goal. For neither of us.

So in this situation I am deciding that it is better for me to revoke myself from your thread. I hope you understand my point.

Wish the early solution of your issue. Bet of luck.

 

[Putt4Dough]

No no don't get me wrong. I'm not arguing. I'm just trying to figure out why I'm getting this message when I know that I activated verifier. See the tests that I just did:

OK so I did a test to see if the message “No settings were changed” after verifier wizard is really because it’s not running or if it tells me that it is already running identically to the previous configuration. I started Verifier and went through the wizard but purposely unselected one driver from the previous configuration and then I got a message asking be to reboot. This logically tells me that verifier is was running and the message “No settings were changed” is to tell me just that.

 

[Putt4Dough]

Does the query log tell you that it's running or otherwise?

 

[Arc]

Is the query log after reboot?

Then the .doc file you uploaded is a critical one to create. Save it upto a point, then restart ... open it again, add the verifier query log, and complete it. Is it what you have done?

If you are running with verifier on, you will come to know yourself that something is going on there. Computer will response at a lag ... things will go slow ..... mouse and cursor will go sticky ...... and shortly it will crash.

 

[Putt4Dough]

No. What I did is ran the verifier and took print screens. then got the message that no changes done. Ran /query right after, no reboot, and sent you the doc. I'm not noticing any lag.

What I can do is deactivate verifier, reboot and then reactivate it, reboot and send you the query. Would that good?

 

[Arc]

You follow the tutorial http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html again ... from the very beginning. Dont miss any single step. When all is done appropriately, it will ask for a reboot itself. And that asking for reboot is the confirmation that you have made your custom verifier settings.

After the reboot .... you need not need me or anybody to point out whether verifier is running or not. It will let you know its existance in a very good manner, and will crash shortly.

So go follow the steps from the beginning.