BSOD need help.

#1
Hello I need help with my computer. I'v been having these screens that turn blue in the middle of me using the computer and at 1st I thought it was nothing but now its gotten worst, now ever time I turn on the computer it just restarts at the Windows 7 Starting screen. I have a Progam that can read the blue screens called "Blue Screen Viewer" and it says I have problems with "ntoskrnl.exe", "hal.dll" and "win32k.sys". Please help and thanks.

(My .dmp files)
View attachment Files.zip
 


Sonny

Excellent Member
#2
I don't know if this will help. You might check and try this. Change the RAM timing from "Optimal" to "Sync", My friend had a ge force card and once he did that everything seemed to be ok.

I hope everything works out for you. If this does not work there are many on here who should be able to help.
 


Last edited:

Trouble

Noob Whisperer
#3
compkewl1:
Hello and welcome to the forums.
You have several older drivers which may need some attention especially a few that involve a Conexant Modem, but we can come back to them later.
First we need to know if you can boot the machine in normal or safemode in order to uninstall AVG. Lets start there use the programs and features applet in the control panel to uninstall it and follow up with the vendor specific proprietary removal tool, located in this list here.
Consider replacing it with MSE
DUMP:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000002, A list entry was corrupt
Arg2: 00073a04, entry in list being removed
Arg3: 0007f7ef, highest physical page number
Arg4: 00000001, reference count of entry being removed
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for avgmfx86.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#b22222][U][B]avgmfx86.sys
[/B][/U][/COLOR]*** WARNING: Unable to verify timestamp for[COLOR=#b22222][U][B] AVGIDSFilter.Sys
[/B][/U][/COLOR]*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#b22222][U][B]AVGIDSFilter.Sys
[/B][/U][/COLOR]BUGCHECK_STR:  0x4E_2
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from 828e3497 to 82921490
STACK_TEXT:  
afbe367c 828e3497 0000004e 00000002 00073a04 nt!KeBugCheckEx+0x1e
afbe36bc 828b6d75 00000000 86d5a438 afbe38d0 nt!MiUnlinkPageFromLockedList+0x51
afbe37dc 828eba2e ae9e4008 ae9e4708 86744998 nt!MiFlushSectionInternal+0x6d3
afbe3844 828b7562 00297ef8 00000000 00000001 nt!MmFlushSection+0xc2
afbe38dc 896df549 86297ef8 00000000 00000000 nt!CcFlushCache+0x156
WARNING: Stack unwind information not available. Following frames may be wrong.
afbe3900 896dd756 86761630 856b08b0 8652e2a8 [COLOR=#b22222][U][B]avgmfx86[/B][/U][/COLOR]+0x3549
afbe3950 896dd919 86761630 b0acee9c 00000060 [COLOR=#b22222][U][B]avgmfx86[/B][/U][/COLOR]+0x1756
afbe3978 88f86aeb b0acee9c afbe3998 afbe39c4 [COLOR=#b22222][U][B]avgmfx86[/B][/U][/COLOR]+0x1919
afbe39e4 88f899f0 afbe3a28 84a368d8 00000000 fltmgr!FltpPerformPreCallbacks+0x34d
afbe39fc 88f9d1fe afbe3a28 88fa0f3c 00000000 fltmgr!FltpPassThroughInternal+0x40
afbe3a10 88f9d8b7 afbe3a28 84a368d8 868c1230 fltmgr!FltpCreateInternal+0x24
afbe3a54 8287ef34 856b6c98 85cc6880 868c1230 fltmgr!FltpCreate+0x2c9
afbe3a6c 90f85f63 8652e2a8 868c1230 84a368d8 nt!IofCallDriver+0x63
afbe3a88 8287ef34 868c1230 84a368d8 8652e304 [COLOR=#b22222][U][B]AVGIDSFilter[/B][/U][/COLOR]+0x1f63
afbe3aa0 82a52b0d b23bb211 afbe3c48 00000000 nt!IofCallDriver+0x63
afbe3b78 82a55ce8 8561e510 858b1f78 867aed20 nt!IopParseDevice+0xed7
afbe3bf4 82a946d2 00000000 afbe3c48 00000040 nt!ObpLookupObjectName+0x4fa
afbe3c50 82a500ae 0020ef58 848b1f78 00000001 nt!ObOpenObjectByName+0x165
afbe3ccc 82aa62d3 0020efb8 00100021 0020ef58 nt!IopCreateFile+0x673
afbe3d14 8288575a 0020efb8 00100021 0020ef58 nt!NtOpenFile+0x2a
afbe3d14 77f06344 0020efb8 00100021 0020ef58 nt!KiFastCallEntry+0x12a
0020ef28 00000000 00000000 00000000 00000000 0x77f06344

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+51
828e3497 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+51
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fd8fa
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  0x4E_2_nt!MiUnlinkPageFromLockedList+51
BUCKET_ID:  0x4E_2_nt!MiUnlinkPageFromLockedList+51
Followup: MachineOwner
DRIVERS: Update or uninstall and or rename as a last resort.
Code:
Rtnicxp.sys 5/30/2008 (very old RealTek network interface card driver)
VSTCNXT3.SYS 10/15/2008 SoftK54 Modem Driver from Conexant Systems Inc.
VSTBS23.SYS 10/15/2008 SoftK54 Modem Driver from Conexant Systems Inc.
VSTDPV3.SYS 10/15/2008 SoftK54 Modem Driver from Conexant Systems Inc.
 


#4
Ok so I can enter safe mode (Im in safe mode at the moment) and I can enter normal mode too but It is still restarting. Also I have uninstalled AVG and installed MSE.

Latest .dmp Files
 


Attachments

#5
How do I do this?
I don't know if this will help. You might check and try this. Change the RAM timing from "Optimal" to "Sync", My friend had a ge force card and once he did that everything seemed to be ok.

I hope everything works out for you. If this does not work there are many on here who should be able to help.
 


Sonny

Excellent Member
#6
I am not real sure how he did it. I believe he went into his bios to change the settings. I will look at my bios and see if maybe that is it and let you know if I found the right place.
 


Sonny

Excellent Member
#7
I did check my Bios and there are some settings for changing. However the wording in mine was different. Check your bios and see what settings they have for your ram.
 


#8
Ill try and tell you if it works or not.
I did check my Bios and there are some settings for changing. However the wording in mine was different. Check your bios and see what settings they have for your ram.
 


Sonny

Excellent Member
#9
I hope that will take care of your problem.
 


#10
Ok so I did it and when I restarted the computer I login and and it didn't restart. Ill inform you if it keeps giveing me the BSOD
 


Sonny

Excellent Member
#11
Ok so I did it and when I restarted the computer I login and and it didn't restart. Ill inform you if it keeps giveing me the BSOD
That would be great! I hope the problem of BSOD is fixed.
 


Trouble

Noob Whisperer
#12
Ok so I can enter safe mode (Im in safe mode at the moment) and I can enter normal mode too but It is still restarting. Also I have uninstalled AVG and installed MSE.
First you need to followup on the last old driver that I mentioned in my initial post
Rtnicxp.sys 5/30/2008 (very old RealTek network interface card driver)
Your latest crash dump (062411-23625-01.dmp dated 6/24/2011 at 7:17:30 AM) is still showing AVG installed
AVGIDSEH.Sys
avgfwd6x.sys
avgrkx86.sys
avgtdix.sys
This would indicate that the above statement is not true or that you ignored my suggestion to follow up the uninstall with the vendor specific proprietary removal tool that I linked to originally.
Second you need to read these two sticky post in the root of the BSOD forum
http://windows7forums.com/blue-scre...mportant-every-thread-starter-please-see.html follow the instruction regarding all slots referenceing the SPD Tab as well as the Memory tab and zipping and uploading the export html report from RAMMon.
And do this one again also
http://windows7forums.com/blue-screen-death-bsod/55603-sf-diagnostic-tool.html follow the instructions regarding right clicking the executeable and choosing to run as administrator.
Feel free to post any new dump files after you tend to the above suggestions if they occur.
Regards
Randy
 


nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#14
Can we please have a system spec which would make nailing down the problem alittle easier. A must though is that you upgrade all your drivers to the latest versions.
 


Sonny

Excellent Member
#15
I am sorry to hear that. I do agree with nmsuk and trouble. Make sure you have the latest drivers. Sorry for not being able to help you.
 


#16
I did uninstall AVG. The .dmp files were from before you told me to uninstall it. Look at the new Files.
 


#17
Where can I go to get my system specs?
 


Sonny

Excellent Member
#18
Where can I go to get my system specs?
You can find your system specs if you go to start-control panel-system security and then system. I think that is what you mean. If you want to find out more, try downloading Belarc Advisor. That will tell you everything that is in your system. Including missing updates.
 


Last edited:

Trouble

Noob Whisperer
#19
Please followup with my suggestion from the post above
Important! Every thread starter please see. follow the instruction regarding all slots referenceing the SPD Tab as well as the Memory tab and zipping and uploading the export html report from RAMMon.
And do this one again also
SF Diagnostic Tool follow the instructions regarding right clicking the executeable and choosing to run as administrator.
Both of the two most recent .dmp files you posted are identifiing Memory Corruption as the issue so we need to take a look at your memory settings or you can identify your particular memory manufacturer, model name and number, and check their website for the proper settings in reference to frequencies, voltages and timings. Of course if you are overclocking anything (memory, cpu, graphics card, etc.,) now would be a good time to reset everything to default settings (setup defaults, optimized defaults, performance defaults) something like that depending on your BIOS.
Your drivers look pretty good right now even though the debugger is still indicating that a driver might be responsible, this could also be an issue with your onboard memory so you should probably use MemTest86 download the latest zipped ISO (4.20) extract it and burn the ISO to a CD, boot the PC from the CD and test each stick individually (7 to 10 passes). Onces you have found a stick that passes flawlessly, use that stick to test each individual memory slot 7 to 10 passes.
DUMPS:
Code:
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000C5, {6300012, 2, 1, 8251e5a0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 06300012, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8251e5a0, address which referenced memory
Debugging Details:
------------------

BUGCHECK_STR:  0xC5_2
CURRENT_IRQL:  2
FAULTING_IP: 
nt!ExAllocatePoolWithTag+596
8251e5a0 8902            mov     dword ptr [edx],eax
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  csrss.exe
LAST_CONTROL_TRANSFER:  from 8246f770 to 8251e5a0
STACK_TEXT:  
80df9be8 8246f770 00000000 000001fc 20707249 nt!ExAllocatePoolWithTag+0x596
80df9c1c 8248ca8a 0000000b 00000000 824ad6f0 nt!IopAllocateIrpPrivate+0x148
80df9c30 824ad6f0 0000000b 00000000 85680640 nt!IoAllocateIrp+0x14
80df9c54 824b301e 85745958 00000043 85680648 nt!IoPageRead+0x60
80df9cac 82467264 85afac30 776c1000 85680611 nt!MiIssueHardFault+0x28c
80df9d1c 8243eaa8 00000000 776c1000 00000001 nt!MmAccessFault+0x25b9
80df9d1c 778055c0 00000000 776c1000 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0028f1f4 00000000 00000000 00000000 00000000 0x778055c0

STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    8251e0d0 - nt!ExAllocatePoolWithTag+cb
 [ 89:88 ]
1 error : !nt (8251e0d0)
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
Code:
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 9011a733, The address that the exception occurred at
Arg3: 81617c08, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
win32k!zzzSetFMouseMoved+8
9011a733 0000            add     byte ptr [eax],al
TRAP_FRAME:  81617c08 -- (.trap 0xffffffff81617c08)
ErrCode = 00000002
eax=00003400 ebx=00000000 ecx=ff1df470 edx=ff5d0578 esi=ff1df470 edi=00000000
eip=9011a733 esp=81617c7c ebp=81617c7c iopl=0         nv up ei pl nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010213
win32k!zzzSetFMouseMoved+0x8:
9011a733 0000            add     byte ptr [eax],al          ds:0023:00003400=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x8E
PROCESS_NAME:  csrss.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 900e7aed to 9011a733
STACK_TEXT:  
81617c7c 900e7aed 00000000 8247d674 00000001 win32k!zzzSetFMouseMoved+0x8
81617cc8 9009d33e 00000004 0085fd28 901629aa win32k!ProcessQueuedMouseEvents+0x1a3
81617d04 900ad7b7 00000004 00000002 80e0d400 win32k!RawInputThread+0x55d
81617d18 901629c5 00000004 0085fd28 81617d34 win32k!xxxCreateSystemThreads+0x4a
81617d28 8247f8ba 00000004 0085fd68 771e70b4 win32k!NtUserCallNoParam+0x1b
81617d28 771e70b4 00000004 0085fd68 771e70b4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0085fd68 00000000 00000000 00000000 00000000 0x771e70b4

STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    9011a730 - win32k!zzzSetFMouseMoved+5
 [ 81:80 ]
1 error : !win32k (9011a730)
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
 


Last edited:
#20
Here are the CPU-Z pictures.
Please followup with my suggestion from the post above
Important! Every thread starter please see. follow the instruction regarding all slots referenceing the SPD Tab as well as the Memory tab and zipping and uploading the export html report from RAMMon.
And do this one again also
SF Diagnostic Tool follow the instructions regarding right clicking the executeable and choosing to run as administrator.
Both of the two most recent .dmp files you posted are identifiing Memory Corruption as the issue so we need to take a look at your memory settings or you can identify your particular memory manufacturer, model name and number, and check their website for the proper settings in reference to frequencies, voltages and timings. Of course if you are overclocking anything (memory, cpu, graphics card, etc.,) now would be a good time to reset everything to default settings (setup defaults, optimized defaults, performance defaults) something like that depending on your BIOS.
Your drivers look pretty good right now even though the debugger is still indicating that a driver might be responsible, this could also be an issue with your onboard memory so you should probably use MemTest86 download the latest zipped ISO (4.20) extract it and burn the ISO to a CD, boot the PC from the CD and test each stick individually (7 to 10 passes). Onces you have found a stick that passes flawlessly, use that stick to test each individual memory slot 7 to 10 passes.
DUMPS:
Code:
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000C5, {6300012, 2, 1, 8251e5a0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 06300012, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8251e5a0, address which referenced memory
Debugging Details:
------------------

BUGCHECK_STR:  0xC5_2
CURRENT_IRQL:  2
FAULTING_IP: 
nt!ExAllocatePoolWithTag+596
8251e5a0 8902            mov     dword ptr [edx],eax
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  csrss.exe
LAST_CONTROL_TRANSFER:  from 8246f770 to 8251e5a0
STACK_TEXT:  
80df9be8 8246f770 00000000 000001fc 20707249 nt!ExAllocatePoolWithTag+0x596
80df9c1c 8248ca8a 0000000b 00000000 824ad6f0 nt!IopAllocateIrpPrivate+0x148
80df9c30 824ad6f0 0000000b 00000000 85680640 nt!IoAllocateIrp+0x14
80df9c54 824b301e 85745958 00000043 85680648 nt!IoPageRead+0x60
80df9cac 82467264 85afac30 776c1000 85680611 nt!MiIssueHardFault+0x28c
80df9d1c 8243eaa8 00000000 776c1000 00000001 nt!MmAccessFault+0x25b9
80df9d1c 778055c0 00000000 776c1000 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0028f1f4 00000000 00000000 00000000 00000000 0x778055c0

STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    8251e0d0 - nt!ExAllocatePoolWithTag+cb
 [ 89:88 ]
1 error : !nt (8251e0d0)
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
Code:
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 9011a733, The address that the exception occurred at
Arg3: 81617c08, Trap Frame
Arg4: 00000000
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
win32k!zzzSetFMouseMoved+8
9011a733 0000            add     byte ptr [eax],al
TRAP_FRAME:  81617c08 -- (.trap 0xffffffff81617c08)
ErrCode = 00000002
eax=00003400 ebx=00000000 ecx=ff1df470 edx=ff5d0578 esi=ff1df470 edi=00000000
eip=9011a733 esp=81617c7c ebp=81617c7c iopl=0         nv up ei pl nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010213
win32k!zzzSetFMouseMoved+0x8:
9011a733 0000            add     byte ptr [eax],al          ds:0023:00003400=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x8E
PROCESS_NAME:  csrss.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 900e7aed to 9011a733
STACK_TEXT:  
81617c7c 900e7aed 00000000 8247d674 00000001 win32k!zzzSetFMouseMoved+0x8
81617cc8 9009d33e 00000004 0085fd28 901629aa win32k!ProcessQueuedMouseEvents+0x1a3
81617d04 900ad7b7 00000004 00000002 80e0d400 win32k!RawInputThread+0x55d
81617d18 901629c5 00000004 0085fd28 81617d34 win32k!xxxCreateSystemThreads+0x4a
81617d28 8247f8ba 00000004 0085fd68 771e70b4 win32k!NtUserCallNoParam+0x1b
81617d28 771e70b4 00000004 0085fd68 771e70b4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0085fd68 00000000 00000000 00000000 00000000 0x771e70b4

STACK_COMMAND:  kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    9011a730 - win32k!zzzSetFMouseMoved+5
 [ 81:80 ]
1 error : !win32k (9011a730)
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
 


Attachments

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.