[BSOD] Frequent crash on Win7 64 bits

Hi all,

I got a lot of BSOD on Windows 7 64 bits.

I have updated the video cards drivers and all the others drivers windows update suggest and it didn't really help.

I have run the Windows 7 mem test 2 times without any error.

The weird thing is that the stop code change a lot.

Here is the computer spec:
HP Pavilion a6318f PC (GX769AA) specifications - HP Home & Home Office Products
With a 8800 GT geforce 4 instead of the default card and 3 gigs instead of 2.

Any suggestion?

For now, I'm thinking of trying another video card or doing a windows repair. But I would like if someone that know how to read dmp file could point me in the right direction.

Thank you.


Unable to load image SiWinAcc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SiWinAcc.sys
*** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys

Lose SiWinAcc.sys, whatever it is
Debugging tools for windows 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Johnny\Desktop\fordumps\dmp\dmp\110410-23134-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols\*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]

Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Thu Nov  4 16:02:05.372 2010 (UTC + 1:00)
System Uptime: 0 days 13:03:45.214
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002b36f0d, fffff880033c4cf0, 0}
Unable to load image SiWinAcc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SiWinAcc.sys
*** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
Probably caused by : fileinfo.sys ( fileinfo!FIPostReadWriteCallback+f2 )
Followup: MachineOwner
0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
An exception happened while executing a system service routine.
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002b36f0d, Address of the instruction which caused the bugcheck
Arg3: fffff880033c4cf0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
nt! ?? ::FNODOBFM::`string'+316e7
fffff800`02b36f0d 3303            xor     eax,dword ptr [rbx]
CONTEXT:  fffff880033c4cf0 -- (.cxr 0xfffff880033c4cf0)
rax=0000000000000013 rbx=ffff0080057d7820 rcx=ffff0080057d7830
rdx=fffff880033c5730 rsi=0000000000000028 rdi=0000000000000040
rip=fffff80002b36f0d rsp=fffff880033c56c0 rbp=fffff880033c5730
 r8=0000000000000028  r9=0000000000000040 r10=fffff80002c53670
r11=fffffa80057d77f0 r12=000000001213f060 r13=000000000000000a
r14=fffffa8003079500 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010213
nt! ?? ::FNODOBFM::`string'+0x316e7:
fffff800`02b36f0d 3303            xor     eax,dword ptr [rbx] ds:002b:ffff0080`057d7820=????????
Resetting default scope
PROCESS_NAME:  cmd.exe
LAST_CONTROL_TRANSFER:  from fffff80002bbc10c to fffff80002b36f0d
fffff880`033c56c0 fffff800`02bbc10c : 00000000`00000000 fffff880`033c5820 00000000`00000001 fffffa80`030795f0 : nt! ?? ::FNODOBFM::`string'+0x316e7
fffff880`033c5710 fffff800`02be6531 : 00000000`00000000 00000000`0000001c 00000000`00000000 00000000`00000000 : nt!PfLogFileDataAccess+0xdc
fffff880`033c5770 fffff880`011aa3e6 : 00000000`00000000 00000000`00000000 fffffa80`034520c0 00000000`00000000 : nt!PfFileInfoNotify+0x521
fffff880`033c5800 fffff880`01161242 : fffff880`033c59b0 fffffa80`034521c8 00000000`00000000 fffffa80`03452010 : fileinfo!FIPostReadWriteCallback+0xf2
fffff880`033c5870 fffff880`01161bc1 : fffff880`033c59b0 fffffa80`03452160 fffffa80`034521c8 fffffa80`03d80820 : fltmgr!FltpPerformPostCallbacks+0x392
fffff880`033c5940 fffff880`0117f5f0 : fffffa80`030795f0 00000000`00000000 fffff880`033c5b40 00000000`00000200 : fltmgr!FltpPassThroughFastIo+0x71
fffff880`033c5980 fffff880`011bea75 : 00000000`00000074 00000000`003aeb0c 00000000`00000008 fffffa80`03079500 : fltmgr!FltpFastIoRead+0x1d0
fffff880`033c5a20 00000000`00000074 : 00000000`003aeb0c 00000000`00000008 fffffa80`03079500 00000000`00000000 : SiWinAcc+0x1a75
fffff880`033c5a28 00000000`003aeb0c : 00000000`00000008 fffffa80`03079500 00000000`00000000 00000000`4a596600 : 0x74
fffff880`033c5a30 00000000`00000008 : fffffa80`03079500 00000000`00000000 00000000`4a596600 fffff880`033c5b40 : 0x3aeb0c
fffff880`033c5a38 fffffa80`03079500 : 00000000`00000000 00000000`4a596600 fffff880`033c5b40 fffffa80`03a35aa0 : 0x8
fffff880`033c5a40 00000000`00000000 : 00000000`4a596600 fffff880`033c5b40 fffffa80`03a35aa0 00000000`0000000e : 0xfffffa80`03079500

fffff880`011aa3e6 4c8d5c2460      lea     r11,[rsp+60h]
SYMBOL_NAME:  fileinfo!FIPostReadWriteCallback+f2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: fileinfo
IMAGE_NAME:  fileinfo.sys
STACK_COMMAND:  .cxr 0xfffff880033c4cf0 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_fileinfo!FIPostReadWriteCallback+f2
BUCKET_ID:  X64_0x3B_fileinfo!FIPostReadWriteCallback+f2
Followup: MachineOwner

Unable to load image \SystemRoot\system32\DRIVERS\Si3132r5.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Si3132r5.sys
*** ERROR: Module load completed but symbols could not be loaded for Si3132r5.sys
Probably caused by : Si3132r5.sys ( Si3132r5+dba4 )
This one too???

Unable to load image \SystemRoot\system32\DRIVERS\avgntflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
Could not read faulting driver name
Probably caused by : avgntflt.sys ( avgntflt+14919 )

Or this one???

Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
This one too!

So we have a bunch of suspicious drivers. Please consider their age and how common they are. Please remove, update, or roll back. Also look at the video driver, which was also implicated.

This could also be a memory issue. Do a memtest86+ or the one included in windows for 4+ hours.

Last edited by a moderator:
Welcome Koutousov. Do not roll back, uninstall. Please follow this for success.

JMV, thanks for the help here but if you would like to continue doing so, please be accurate and direct in the advice unless you will confuse the members and lead them unwell. (It is not a memory issue.)

1) Update your Silicon Image storage card drivers from the following link. Make sure you download RAID version:


Si3132r5 Si3132r5.sys Fri Jun 01 13:08:28 2007
SiWinAcc SiWinAcc.sys Mon Nov 01 15:23:29 2004

2) Update your Conexant modem drivers from the manufacturer's site or hardware vendor's site:

XAudio64 XAudio64.sys Wed Apr 29 14:21:07 2009
CAX_DP CAX_DP.sys Fri Feb 13 16:18:25 2009
CAX_CNXT CAX_CNXT.sys Fri Feb 13 16:19:32 2009
CAXHWBS2 CAXHWBS2.sys Fri Feb 13 16:21:18 2009

3) Update Realtek HD Audio driver. Run the download once, reboot, then run it again:

RTKVHD64 RTKVHD64.sys Tue Aug 04 05:50:52 2009


4) Update you NVIDIA chipset drivers from your motherboard manufacturer's site:

nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008
nvstor nvstor.sys Wed May 20 02:45:37 2009

Let me know which motherboard you have if you run into trouble with this.

5) Navigate to C:\Windows\System32\drivers and rename lirsgt.sys to lirsgt.BAK.


Lose SiWinAcc.sys, whatever it is
Please research your advice before you give it, if you aren't sure. In this case, it would render the user's machine to have no ability to use the add-on Silicon Image storage card. Not good.

Yes, Master

I do not appreciate the sarcastic remark. It takes more knowledge to repair bsods correctly than simply opening a crash dump and telling a user to remove a driver, as is obvious in what happened above here.

Your advice would obviously have been harmful to the OP if he had followed. We have an excellent standard of bsod alleviation here and I do not wish to see it lessened by any degree.

That being said, welcome to the forum. :) I look forward to seeing better posts from you in the future. :)

Also, please refrain from making many posts consecutively. Rather, edit the first post if you wish to add something else to it. An exception is when the addition is completely foreign to the original post you've made:


19. Post Counting: Do not post messages solely to increase the number of posts you have, nor your standing on the website itself.

Last edited:
I fully agree with you. I hope you can take a joke.

I also hope that the OP (what does that even mean) would be wise enough to recognise the importance of a driver, and not actually remove it before considering the consequences.

I also know this is not true.

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