How do i patch vista eventid 4226?

Question2 · Sep 29, 2007

All the 4226 patches ive downloaded for vista just causes my computer to bluescreen during the bootup process(0x7F). Has someone managed to patch eventid 4226 on vista successfully?

Question2 · Sep 30, 2007

What the...nobody has done this?

Adrynalyne · Sep 30, 2007

Not I. But if tis cuasing a stop error, its an incompatible driver (the tcpip.sys) for your system, or its conflicting with another.

Feel free to peruse the How To on BSOD to see if this indeed is the culprit.

Question2 · Sep 30, 2007

I still cant get the debugger to work. I downloaded the huge symbols file from microsoft and pointed the debugger to it but it is STILL insisting the symbols are incorrect.

Code:

Loading Dump File [C:\Windows\Minidump\Mini092607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols
Executable search path is: 
Map \SystemRoot\system32\ntkrnlpa.exe:
  Image region 800:e4a00 does not fit in mapping
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x82400000 PsLoadedModuleList = 0x82511db0
Debug session time: Wed Sep 26 21:25:58.255 2007 (GMT+8)
System Uptime: 0 days 1:13:49.034
Map \SystemRoot\system32\ntkrnlpa.exe:
  Image region 800:e4a00 does not fit in mapping
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 95e2398d, 97d13990, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : win32k.sys ( win32k!vSpDeleteSprite+17 )

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

And i dont seem to have any minidumps from the BSODs during bootup, only one for the 19th and one for the 26th of september, i had at least half a dozen yesterday but the folder only has these two.

Question2 · Oct 1, 2007

bump...so how do i patch eventid 4226?

Question2 · Oct 2, 2007

damnit bump again.

ibbonkers · Oct 2, 2007

according to a google search It has to do with vista home and tcp/ip limiting interfering with torrent clients. here's one workaround to it
http://torrentfreak.com/optimize-vista-for-bittorrent-emule-p2ptv/
I guess ultimate(which is what I use) doesnt have the same limits as home basic

Question2 · Oct 2, 2007

I will try that after work, but from the description that sounds like the one causing me to bluescreen at boot .

Question2 · Oct 17, 2007

The manual one for that just disables my internet completely.

DavidGP · Oct 17, 2007

Why would you be wishing to do this? if its for more speed, then that will not happen with this patch for tcp/ip sockets as while some p2p apps use Raw sockets many dont and just dont use them well, the error 4226 pops up when the app is trying to connect to 10 or more within 1 second of each other, this does not hamper download speeds.

All this error is, is that within 1 second you ave tried to concurrently connect to 10 tcp/ip sockets at once, all this does is hinder malware and not your p2p application as it will try 1 second later and connect, however it will try to connect to 10 more connections and error, half of these connections in p2p ( which lets face it is why many wish to for some reason patch this limit ) are likely anyway to be none responsive computers at any one time.

If downloading do you hit your max bandwidth, this dependent on site or locations restrictions?

But you could try this http://www.securevista.net/2007/04/vista-tcpip-limit-patch.html

Question2 · Oct 18, 2007

Ah the patch doesnt work with a windows update that explains it. Let me see if it works now.

Question2 · Oct 18, 2007

Wait...i dont even have that update .

Are you sure it doesnt affect P2P download speeds at all? I noticed significant improvements on XP when i patched it.

Log in or Sign up

How do i patch vista eventid 4226?

Question2 Private E-2

Question2 Private E-2

Adrynalyne Guest

Question2 Private E-2

Question2 Private E-2

Question2 Private E-2

ibbonkers First Sergeant

Question2 Private E-2

Question2 Private E-2

DavidGP MajorGeeks Forum Administrator - Grand Pooh-Bah Staff Member

Question2 Private E-2

Question2 Private E-2