BSOD! attempt to write to read-only memory

Gordan · 03 Nov 2010

I am going to post a new theme for this problem, because it doesn't appear in news (In BSoD Help and Support). It considers a old theme. So you can delete this.

usasma · 03 Nov 2010

2 STOP 0xBE in MSINFO32 report - one blames OS Kernel, one blames video
Please update your webcam, and your modem as their drivers are from 2007 and 2008 respectively.

Since you've already tested the memory, I'd suggest running Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Nov  3 19:25:40.673 2010 (UTC - 4:00)
System Uptime: 0 days 9:01:15.515
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  mbamservice.ex
Bugcheck code 000000BE
Arguments 9694f008 89ba5101 b2e23adc 0000000a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Gordan · 04 Nov 2010

usasma said:

2 STOP 0xBE in MSINFO32 report - one blames OS Kernel, one blames video
Please update your webcam, and your modem as their drivers are from 2007 and 2008 respectively.

Since you've already tested the memory, I'd suggest running Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Wed Nov  3 19:25:40.673 2010 (UTC - 4:00)
System Uptime: 0 days 9:01:15.515
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  mbamservice.ex
Bugcheck code 000000BE
Arguments 9694f008 89ba5101 b2e23adc 0000000a
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

I made it all this suggestions for you. After the first restart when show windows 7 logo the laptop was freeze and it didn't work. Then i restart again and the windows is restarted normally whithout any freeze or crash. I haven't BSoD after the restarts. Now i should wait 36 hours to continue the operation or i should now to select "Delete existing settings"? Thanks usasma again.

usasma · 04 Nov 2010

Wait 36 hours.
Check the C:\Windows\Minidump folder to see if there are more memory dump error files (and upload them if there are).

Gordan · 04 Nov 2010

usasma said:

Wait 36 hours.
Check the C:\Windows\Minidump folder to see if there are more memory dump error files (and upload them if there are).

Yes it has files in Minidump folder. Here is the attachment.

usasma · 04 Nov 2010

This is the same memory dump as noted above. Please wait the 36 hours and then see if there's a new one there.

Gordan · 04 Nov 2010

usasma said:

This is the same memory dump as noted above. Please wait the 36 hours and then see if there's a new one there.

Okay usasma, i will wait 36 hours and than i will post the files in Minidump here again.
Cheers, Gordan.

Gordan · 05 Nov 2010

usasma said:

This is the same memory dump as noted above. Please wait the 36 hours and then see if there's a new one there.

Hello again mate.
I have BSoD again before 10 minutes, and it say: Special Pool Memory Corruption. I don't wait 36 hours, i was waiting about 10 hours and i have bsod.
Here is the new Minidump files from this new BSoD.
What i should do now?

Thanks.

zigzag3143 · 05 Nov 2010

Gordan said:

usasma said:

This is the same memory dump as noted above. Please wait the 36 hours and then see if there's a new one there.

Hello again mate.
I have BSoD again before 10 minutes, and it say: Special Pool Memory Corruption. I don't wait 36 hours, i was waiting about 10 hours and i have bsod.
Here is the new Minidump files from this new BSoD.
What i should do now?

Thanks.

This one was blamed on nsiproxy.sys (dont think that is the true cause however).

I would

1-Update all the old drivers listed below

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

2-run a system file check to verify and repair the OS files

SFC /SCANNOW Command - System File Checker

3-Remove sptd.sys (used by daemon tools/alcohol)

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

4-run memtest to test your memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Old drivers

Code:

OEM02Vfx.sys        0x967d2d00    0x00001d00    3/5/2007 06:45:03            0x45ebf4af    0x967d1000                
OEM02Dev.sys        0x947f5880    0x00039880    10/10/2007 22:29:05            0x470d8a71    0x947bc000                
VSTCNXT3.SYS        0x966d7000    0x000b5000    10/15/2008 20:29:13            0x48f68ad9    0x96622000                
VSTAZL3.SYS        0x946ba000    0x0003d000    10/15/2008 20:30:03            0x48f68b0b    0x9467d000                
VSTDPV3.SYS        0x947bc000    0x00102000    10/15/2008 20:32:04            0x48f68b84    0x946ba000                
Apfiltr.sys        0x8f595000    0x00035000    3/24/2009 12:25:22            0x49c90972    0x8f560000                
ssmdrv.sys        0x8cf2ea00    0x00005a00    5/5/2009 06:05:18            0x4a000f5e    0x8cf29000                
spldr.sys        0x86249000    0x00008000    5/11/2009 12:13:47            0x4a084ebb    0x86241000                
amdxata.sys        0x85cbf000    0x00009000    5/19/2009 13:57:35            0x4a12f30f    0x85cb6000                
rimsptsk.sys        0x8f4f6000    0x00014000    6/25/2009 03:10:46            0x4a4322f6    0x8f4e2000                
rixdptsk.sys        0x8f548000    0x00052000    6/25/2009 03:25:57            0x4a432685    0x8f4f6000                
rimmptsk.sys        0x8f4e2000    0x00011000    6/25/2009 03:58:09            0x4a432e11    0x8f4d1000                
bcmwl6.sys        0x8f482000    0x00267000    7/7/2009 20:44:47            0x4a53ebff    0x8f21b000

Analysis

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\110510-20264-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c4e000 PsLoadedModuleList = 0x82d96810
Debug session time: Fri Nov  5 13:08:38.791 2010 (GMT-4)
System Uptime: 0 days 1:52:21.633
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
..........
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: c96ccf68, address trying to free
Arg2: 00000000, bytes requested
Arg3: 00000098, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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


BUGCHECK_STR:  0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE:  22

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  1

IRP_ADDRESS:  016ccf68

LAST_CONTROL_TRANSFER:  from 82d34ae5 to 82d2ad10

STACK_TEXT:  
b7c4793c 82d34ae5 000000c1 c96ccf68 00000000 nt!KeBugCheckEx+0x1e
b7c47a2c 82d6d0db c96ccf68 b23cec40 b23cec40 nt!MmFreeSpecialPool+0x6c
b7c47a94 82f82992 c96ccf68 00000000 b7c47abc nt!ExFreePoolWithTag+0xd6
b7c47aa4 82f82ace c96ccf68 00000000 c96ccf68 nt!ViIrpFree+0xf
b7c47abc 82f7d1c0 82cf054f c96ccf68 b7c47b14 nt!VfIoFreeIrp+0xd3
b7c47acc 82cf054f c96ccf68 98433831 00002000 nt!IovFreeIrpPrivate+0x47
b7c47b14 82cb6dbf 016ccfa8 b7c47b5c 00000000 nt!IopCompleteRequest+0x429
b7c47b64 82f7db64 c96ccf68 00000000 8bade5b0 nt!IopfCompleteRequest+0x3b4
b7c47bcc 8cf73044 afd867f8 c96ccf68 b7c47c00 nt!IovCompleteRequest+0x133
b7c47bdc 82f7d6c3 8bade5b0 c96ccf68 b4dff500 nsiproxy!NsippDispatch+0x92
b7c47c00 82c8a473 00000000 c96ccf68 8bade5b0 nt!IovCallDriver+0x258
b7c47c14 82e8bf6e b4dff500 c96ccf68 c96ccfd8 nt!IofCallDriver+0x1b
b7c47c34 82ea8d5f 8bade5b0 b4dff500 00000000 nt!IopSynchronousServiceTail+0x1f8
b7c47cd0 82eab53a 8bade5b0 c96ccf68 00000000 nt!IopXxxControlFile+0x6aa
b7c47d04 82c9144a 00000128 00000280 00000000 nt!NtDeviceIoControlFile+0x2a
b7c47d04 774164f4 00000128 00000280 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
089ff124 00000000 00000000 00000000 00000000 0x774164f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nsiproxy!NsippDispatch+92
8cf73044 5f              pop     edi

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  nsiproxy!NsippDispatch+92

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nsiproxy

IMAGE_NAME:  nsiproxy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf48

FAILURE_BUCKET_ID:  0xC1_22_VRF_nsiproxy!NsippDispatch+92

BUCKET_ID:  0xC1_22_VRF_nsiproxy!NsippDispatch+92

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

Gordan · 05 Nov 2010

zigzag3143 said:

Gordan said:

usasma said:

This is the same memory dump as noted above. Please wait the 36 hours and then see if there's a new one there.

Hello again mate.
I have BSoD again before 10 minutes, and it say: Special Pool Memory Corruption. I don't wait 36 hours, i was waiting about 10 hours and i have bsod.
Here is the new Minidump files from this new BSoD.
What i should do now?

Thanks.

This one was blamed on nsiproxy.sys (dont think that is the true cause however).

I would

1-Update all the old drivers listed below

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

2-run a system file check to verify and repair the OS files

SFC /SCANNOW Command - System File Checker

3-Remove sptd.sys (used by daemon tools/alcohol)

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

4-run memtest to test your memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Old drivers

Code:

OEM02Vfx.sys        0x967d2d00    0x00001d00    3/5/2007 06:45:03            0x45ebf4af    0x967d1000                
OEM02Dev.sys        0x947f5880    0x00039880    10/10/2007 22:29:05            0x470d8a71    0x947bc000                
VSTCNXT3.SYS        0x966d7000    0x000b5000    10/15/2008 20:29:13            0x48f68ad9    0x96622000                
VSTAZL3.SYS        0x946ba000    0x0003d000    10/15/2008 20:30:03            0x48f68b0b    0x9467d000                
VSTDPV3.SYS        0x947bc000    0x00102000    10/15/2008 20:32:04            0x48f68b84    0x946ba000                
Apfiltr.sys        0x8f595000    0x00035000    3/24/2009 12:25:22            0x49c90972    0x8f560000                
ssmdrv.sys        0x8cf2ea00    0x00005a00    5/5/2009 06:05:18            0x4a000f5e    0x8cf29000                
spldr.sys        0x86249000    0x00008000    5/11/2009 12:13:47            0x4a084ebb    0x86241000                
amdxata.sys        0x85cbf000    0x00009000    5/19/2009 13:57:35            0x4a12f30f    0x85cb6000                
rimsptsk.sys        0x8f4f6000    0x00014000    6/25/2009 03:10:46            0x4a4322f6    0x8f4e2000                
rixdptsk.sys        0x8f548000    0x00052000    6/25/2009 03:25:57            0x4a432685    0x8f4f6000                
rimmptsk.sys        0x8f4e2000    0x00011000    6/25/2009 03:58:09            0x4a432e11    0x8f4d1000                
bcmwl6.sys        0x8f482000    0x00267000    7/7/2009 20:44:47            0x4a53ebff    0x8f21b000

Analysis

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\110510-20264-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c4e000 PsLoadedModuleList = 0x82d96810
Debug session time: Fri Nov  5 13:08:38.791 2010 (GMT-4)
System Uptime: 0 days 1:52:21.633
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
..........
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: c96ccf68, address trying to free
Arg2: 00000000, bytes requested
Arg3: 00000098, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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


BUGCHECK_STR:  0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE:  22

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  1

IRP_ADDRESS:  016ccf68

LAST_CONTROL_TRANSFER:  from 82d34ae5 to 82d2ad10

STACK_TEXT:  
b7c4793c 82d34ae5 000000c1 c96ccf68 00000000 nt!KeBugCheckEx+0x1e
b7c47a2c 82d6d0db c96ccf68 b23cec40 b23cec40 nt!MmFreeSpecialPool+0x6c
b7c47a94 82f82992 c96ccf68 00000000 b7c47abc nt!ExFreePoolWithTag+0xd6
b7c47aa4 82f82ace c96ccf68 00000000 c96ccf68 nt!ViIrpFree+0xf
b7c47abc 82f7d1c0 82cf054f c96ccf68 b7c47b14 nt!VfIoFreeIrp+0xd3
b7c47acc 82cf054f c96ccf68 98433831 00002000 nt!IovFreeIrpPrivate+0x47
b7c47b14 82cb6dbf 016ccfa8 b7c47b5c 00000000 nt!IopCompleteRequest+0x429
b7c47b64 82f7db64 c96ccf68 00000000 8bade5b0 nt!IopfCompleteRequest+0x3b4
b7c47bcc 8cf73044 afd867f8 c96ccf68 b7c47c00 nt!IovCompleteRequest+0x133
b7c47bdc 82f7d6c3 8bade5b0 c96ccf68 b4dff500 nsiproxy!NsippDispatch+0x92
b7c47c00 82c8a473 00000000 c96ccf68 8bade5b0 nt!IovCallDriver+0x258
b7c47c14 82e8bf6e b4dff500 c96ccf68 c96ccfd8 nt!IofCallDriver+0x1b
b7c47c34 82ea8d5f 8bade5b0 b4dff500 00000000 nt!IopSynchronousServiceTail+0x1f8
b7c47cd0 82eab53a 8bade5b0 c96ccf68 00000000 nt!IopXxxControlFile+0x6aa
b7c47d04 82c9144a 00000128 00000280 00000000 nt!NtDeviceIoControlFile+0x2a
b7c47d04 774164f4 00000128 00000280 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
089ff124 00000000 00000000 00000000 00000000 0x774164f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nsiproxy!NsippDispatch+92
8cf73044 5f              pop     edi

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  nsiproxy!NsippDispatch+92

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nsiproxy

IMAGE_NAME:  nsiproxy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf48

FAILURE_BUCKET_ID:  0xC1_22_VRF_nsiproxy!NsippDispatch+92

BUCKET_ID:  0xC1_22_VRF_nsiproxy!NsippDispatch+92

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

- I tested the memory with the program of Dell when the windows will boot up. I think it is called Windows Memory Diagnostic. The result is that i haven't any errors on memory.
- In device manager, all the drivers was fully updated. Where to find a program to update all the old drivers ? I don't know who is my old drivers because here said that is fully updated.
- I checked the sfc previous month and i have one error who don't want to repair
- Now from the post of usasma, i will "Delete existing settings" on the verifier.
- Yes i have Daemon Tools and i will be delete now.
Thanks again.

BSOD! attempt to write to read-only memory

BSoD Random