Seemingly Random BSODS for as long as I can remember...

Ohme

New Member
#1
Hey guys. I bought my computer from ARBICO in the UK and since day one its been getting blue screens. I first told ARBICO about it and they were no help at all. I attached the 4 latest minidump files (plenty more where they came from). I get different error messages often, its rarely the same error over and over, although they do re-occur.

I also attached the CPUZ images to show what my system is made up of.

I would LOVE for any help on this as its been going on for about 2 years! since i first bought my machine! sigh....

Also, I have ran checkdisk and the memory diagnostic tool for about 6 passes on all my RAM sticks. No errors were shown. I was thinking about maybe flashing my BIOS but I'm scared as I need this computer to do work (even though it does crash, its better than having a PC that doesnt work at all!)

thanks !

Ohme
 


Attachments

Saltgrass

Excellent Member
Microsoft Community Contributor
#2
Your dump files point at different things, but two seem related to the video. Whether something is causing them to have problems, or you need an update, hard to tell.

But there are some files that really don't look like they belong. You can check the net, but if you know what they are for you would understand what you find better than I.

atksgt.sys Mon Oct 20 02:50:38 2008
lirsgt.sys Sat Mar 06 13:53:01 2004
 


Ohme

New Member
#3
Hmmm, So you think its a whole bunch of rivers that have been corrupted? I forgot to mention that at one point, the power supply completely broke, and my PC wouldnt turn on. I sent it back to ARBICO and they replaced the power supply. My PC then turned on but the ever frequent blue screens still remained. They replaced it with the same power supply. Could that be the cause of these recent BSODS do you think? seems more logical to me than a load of faulty files. The system is fairly knew.
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#4
If you think it might be the power supply, can you replace it yourself?

Otherwise, analyzing blue screens is a non-standard operation. You look for anything that might be involved.

If you wait for a while, someone else may come by to offer an opinion.
 


Ohme

New Member
#5
umm I could try swapping it!

Yeah tell me about it, I've been trying to deduce what the problem(s) could be for well, years. No one seems to know :(

Thanks for your input and time though! Hopefully someone will shed some light. Should I upload more minidumps? I have many !
 


Trouble

Noob Whisperer
#6
Could you take some time and re-run CPUz and this time take snips of all the tabs, including all the slots separately under the SPD tab and download and run RAMMon export the html report to your desktop put everything into a single folder zip it up and attach it to your next post.
Thanks
Randy
 


Ohme

New Member
#7
Hey. Heres what you asked for....

Cheers!
 


Attachments

Ohme

New Member
#8
Hey, PC just crashed, got this BSOD...

Cheers, Ohme
 


Attachments

nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#9
Hi
In your bios can you change the TRAS setting to 25 and set the memory speed to 800(1600)
Also boost the DDR Voltage to 1.55V. I'd also boost the NB-SB Voltage by 0.10V if possible and see how it goes.

NmsUK
 


Ohme

New Member
#10
Hey
Thanks for the quick reply, I will certainly try what you have said... but I'm kind of scared. Is there any risk this will destroy my system? I've heard bad things about BIOS stuff... I basically need this PC working and wont be able to get any new hardware should it completely break...

Sorry for the hesitation, just had to ask

Steve
 


nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#11
Simple answer NO!
 


Trouble

Noob Whisperer
#12
Was holding off until nmsuk had a chance to take a look at your memory settings. Thanks Rich.
Additionally update the following drivers
lirsgt.sys 3/6/2004 and atksgt.sys 10/20/2008 both seem to be associated with Tages Protection System from Tages SA update, uninstall or rename for testing.
and
Rt64win7.sys 2/26/2009 from here Realtek check the list to confirm your card is mentioned, otherwise use the navigation menu on the left of that page to find the latest driver for your particular card.
Your most recent dump seems to indicated that luafv.sys may be causing a problem (that I believe is a Microsoft System file for File Virtualization Filter Driver and is not likely the actual problem, but BdSpy.sys was also caught in the stack and might be the more likely candidate. It seems to be associated with a file monitor driver for a product called BullGuard by BullGuard Ltd. and we have seen our share of security suites causing BSODs although I am not familiar with this particular product.
DUMP:
Code:
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800032cfb65, fffff8800557d370, 0}
Unable to load image[COLOR=#ff0000][U][B] BdSpy.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for BdSpy.sys
*** ERROR: Module load completed but symbols could not be loaded for BdSpy.sys
Probably caused by : luafv.sys ( luafv!LuafvNormalizeNameComponentEx+fa )
Followup: MachineOwner
---------
0: kd> !analyze -v;r;kv;lmtn;lmtsmn
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032cfb65, Address of the instruction which caused the bugcheck
Arg3: fffff8800557d370, 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.
FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`032cfb65 498b08          mov     rcx,qword ptr [r8]
CONTEXT:  fffff8800557d370 -- (.cxr 0xfffff8800557d370)
rax=00000006cc330003 rbx=fffff880010f1540 rcx=fffff880010f1540
rdx=f7fffa8007a1acd1 rsi=00000000000000a8 rdi=0000000000000042
rip=fffff800032cfb65 rsp=fffff8800557dd50 rbp=0000000000000000
 r8=f7fffa8007a1acd0  r9=0000000000000000 r10=fffff880010f1540
r11=0000000000000060 r12=fffff880010e7890 r13=fffffa8007359c01
r14=fffffa8006ab8010 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!ExpInterlockedPopEntrySListFault16:
fffff800`032cfb65 498b08          mov     rcx,qword ptr [r8] ds:002b:f7fffa80`07a1acd0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80003586dae to fffff800032cfb65
STACK_TEXT:  
fffff880`0557dd50 fffff800`03586dae : fffffa80`08a13740 fffff800`03586d04 fffff8a0`0f89cec0 fffff880`010f890e : nt!ExpInterlockedPopEntrySListFault16
fffff880`0557dd60 fffff880`010f7e0a : fffffa80`08a13740 00000000`00000008 fffff880`0557deb8 00000000`00000000 : nt!FsRtlAllocateExtraCreateParameterFromLookasideList+0x5e
fffff880`0557dda0 fffff880`010f83e1 : 00000000`00000000 fffffa80`07350950 00000000`00000017 fffff800`035d5438 : fltmgr!TargetedIOCtrlGenerateECP+0x7a
fffff880`0557de10 fffff880`0643ed26 : fffffa80`07350950 00000000`00000020 fffff880`0557dfa0 fffff880`0557e030 : fltmgr!FltCreateFileEx2+0xd1
fffff880`0557df20 fffff880`010f78c2 : 00000000`0000005f fffffa80`099c3c90 00000000`00000030 00000000`00000000 : luafv!LuafvNormalizeNameComponentEx+0xfa
fffff880`0557e020 fffff880`010f7afe : 00000000`00000003 00000000`0000005f 00000000`00000000 00000000`000007ff : fltmgr!FltpCallNormalizeNameComponentHandler+0x82
fffff880`0557e080 fffff880`010f8f81 : 00000000`00000093 00000000`00000093 00000000`00000060 00000000`00000000 : fltmgr!FltpExpandShortNames+0x14e
fffff880`0557e0e0 fffff880`010f8e1e : fffffa80`099c3c90 00000000`00000000 00000000`00000000 fffff980`26ec0500 : fltmgr!FltpGetNormalizedFileNameWorker+0xc1
fffff880`0557e120 fffff880`010e4b9d : c00000bb`00004000 00000000`00000000 fffffa80`08a35b00 fffff880`0557f000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`0557e180 fffff880`010debf6 : fffffa80`06ab7000 fffffa80`08a35010 fffffa80`079f0108 00000000`00000000 : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`0557e1c0 fffff880`010e5b44 : fffffa80`07611000 00000000`00000000 fffffa80`08a35010 00000000`00000101 : fltmgr! ?? ::FNODOBFM::`string'+0x30f3
fffff880`0557e240 fffff880`016b0c34 : fffffa80`099c3c90 fffff880`0557e5c8 fffff880`0557e320 00000000`00000001 : fltmgr!FltGetFileNameInformation+0x184
fffff880`0557e2d0 fffffa80`099c3c90 : fffff880`0557e5c8 fffff880`0557e320 00000000`00000001 fffff8a0`021e9670 :[U][B][COLOR=#ff0000] BdSpy+0x2c34[/COLOR][/B][/U]
fffff880`0557e2d8 fffff880`0557e5c8 : fffff880`0557e320 00000000`00000001 fffff8a0`021e9670 00000000`00000110 : 0xfffffa80`099c3c90
fffff880`0557e2e0 fffff880`0557e320 : 00000000`00000001 fffff8a0`021e9670 00000000`00000110 fffffa80`095ae010 : 0xfffff880`0557e5c8
fffff880`0557e2e8 00000000`00000001 : fffff8a0`021e9670 00000000`00000110 fffffa80`095ae010 00000000`000007ff : 0xfffff880`0557e320
fffff880`0557e2f0 fffff8a0`021e9670 : 00000000`00000110 fffffa80`095ae010 00000000`000007ff fffffa80`088f2010 : 0x1
fffff880`0557e2f8 00000000`00000110 : fffffa80`095ae010 00000000`000007ff fffffa80`088f2010 00000000`00000001 : 0xfffff8a0`021e9670
fffff880`0557e300 fffffa80`095ae010 : 00000000`000007ff fffffa80`088f2010 00000000`00000001 00000000`00000001 : 0x110
fffff880`0557e308 00000000`000007ff : fffffa80`088f2010 00000000`00000001 00000000`00000001 00000000`00000000 : 0xfffffa80`095ae010
fffff880`0557e310 fffffa80`088f2010 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : 0x7ff
fffff880`0557e318 00000000`00000001 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`010e7a00 : 0xfffffa80`088f2010
fffff880`0557e320 00000000`00000001 : 00000000`00000000 00000000`00000000 fffff880`010e7a00 fffffa80`07b7ebb0 : 0x1
fffff880`0557e328 00000000`00000000 : 00000000`00000000 fffff880`010e7a00 fffffa80`07b7ebb0 fffffa80`076110c0 : 0x1
FOLLOWUP_IP: 
luafv!LuafvNormalizeNameComponentEx+fa
fffff880`0643ed26 8bd8            mov     ebx,eax
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  luafv!LuafvNormalizeNameComponentEx+fa
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: luafv
IMAGE_NAME:  luafv.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc295
STACK_COMMAND:  .cxr 0xfffff8800557d370 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_luafv!LuafvNormalizeNameComponentEx+fa
BUCKET_ID:  X64_0x3B_luafv!LuafvNormalizeNameComponentEx+fa
Followup: MachineOwner
Follow up on nmsuk's suggestions regarding you memory settings. I have some personal experience with this type of problem as it relates to having all four memory slots populated with 1333 memory and the need to bump the controller voltage a bit to compensate or dumb down the memory settings to 1066. You can read about it here http://windows7forums.com/blogs/trouble/436-my-bsod-odyssey.html and the link at the bottom of that Blog is where I found my solution
Regards
Randy
 


Ohme

New Member
#13
Awesome, thanks both.

I will try it all and report back.... wish me luck
 


Ohme

New Member
#14
Hey guys I changed my bios settings to:

DDR Voltage = 1.55V
NB = 1.200V
SB = 1.300V
Memory Speed = (Couldn't find this setting anywhere...)
RAS = 25t

I have updated the Tages and Realtek netwrok drivers. Will post my next mini dump if and when it happens!

Fingers Crossed....

Ohme
 


Ohme

New Member
#15
Hey guys, after all the BIOS fiddling and driver updating, just got a BSOD while playing Battlefield 3...


here's the minidump...

:'(

Ohme
 


Attachments

Elmer

Extraordinary Member
#16
OK to chip in with my tuppence worth?

Can I ask what AV you are running?

I saw BdSpy.sys which is Bulldog File Monitor in your dmp file. Can I suggest that while you are having bsod issues that you uninstall your current AV, (let us know, you may need to run a clean up tool) and replace it with Microsoft Security Essentials. Once your system is settled you can re-try your current AV.
 


Ohme

New Member
#17
OK to chip in with my tuppence worth?

Can I ask what AV you are running?

I saw BdSpy.sys which is Bulldog File Monitor in your dmp file. Can I suggest that while you are having bsod issues that you uninstall your current AV, (let us know, you may need to run a clean up tool) and replace it with Microsoft Security Essentials. Once your system is settled you can re-try your current AV.

Have just done what you asked, will re-post with minidump if any crashes happen!

Ohme
 


#18
Hey guys

I thought i was in the clear after removing Bullguard, however just recieved this BSOD while playing APB.

Any thoughts would be very welcome
 


Attachments

#19
Just BlueScreened again with this error. Different from the one earlier today I think...

Any elders of knowledge able to tell me whats up?

Ohme
 


Attachments

Elmer

Extraordinary Member
#20
Sat Dec 10 12:04:05.313 2011
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes:
System service, Device driver, graphics driver, ?memory.

Bugcheck Analysis:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880010bf039, fffff8800a552990, 0}

Probably caused by : [COLOR=#ff0000][B]fileinfo.sys [/B][/COLOR]( fileinfo!FIStreamGet+52 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880010bf039, Address of the instruction which caused the bugcheck
Arg3: fffff8800a552990, 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.

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`010bf039 488b4820        mov     rcx,qword ptr [rax+20h]

CONTEXT:  fffff8800a552990 -- (.cxr 0xfffff8800a552990)
rax=f7fff8a00c0c4f68 rbx=0000000000000000 rcx=fffffa8007b4a6d0
rdx=fffffa80075b7bb0 rsi=fffffa8007b4a720 rdi=fffffa8007b4a6d0
rip=fffff880010bf039 rsp=fffff8800a553370 rbp=fffff8800a5534b0
 r8=0000000000000000  r9=fffff8800a5534a8 r10=fffffa8007b4a6d8
r11=0000000000000011 r12=fffff8800a5534a8 r13=fffffa8008ecccf0
r14=0000000000000000 r15=fffffa80075b7bb0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
fltmgr!GetContextFromStreamList+0x99:
fffff880`010bf039 488b4820        mov     rcx,qword ptr [rax+20h] ds:002b:f7fff8a0`0c0c4f88=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME: [B][COLOR=#ff0000] APB.exe[/COLOR][/B]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880010c9dbe to fffff880010bf039

FOLLOWUP_IP: 
fileinfo!FIStreamGet+52
fffff880`0110f052 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  fileinfo!FIStreamGet+52

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME:  fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc481

STACK_COMMAND:  .cxr 0xfffff8800a552990 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_fileinfo!FIStreamGet+52

BUCKET_ID:  X64_0x3B_fileinfo!FIStreamGet+52

Sat Dec 10 13:21:16.956 2011
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:
Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Bugcheck Analysis:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by :[B][COLOR=#ff0000] ntkrnlmp.exe[/COLOR][/B] ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3038383932623437
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME: [B][COLOR=#ff0000] APB.exe[/COLOR][/B]

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880009b05d8 -- (.exr 0xfffff880009b05d8)
ExceptionAddress: fffff800032e14f9 (nt!KiProcessExpiredTimerList+0x0000000000000129)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880009b0680 -- (.trap 0xfffff880009b0680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80086343e8 rbx=0000000000000000 rcx=f7fffa80086343e8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032e14f9 rsp=fffff880009b0810 rbp=fffffa8007de5688
 r8=fffff88002fd7301  r9=0000000000000002 r10=000000000000009b
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`032e14f9 48894108        mov     qword ptr [rcx+8],rax ds:f7fffa80`086343f0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032cd5fe to fffff800032d5c10

STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`032cd5fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
There's nothing jumping out at me in your latest dump files. APB.exe is mentioned in both dump files though. As hard as it may be, can you steer clear of cleaning up the streets for a while to see if you still get a blue screen? Say, give it a miss for 8 hours. Then try to play and see what happens.

After about 4 hours of no play you may want to enable driver verifier so that if there is a rogue driver, we can flush it out.

To start Driver Verifier:
- Create a restore point!!
- GoTo Start and in the Search or a Run... Window type verifier 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 every option EXCEPT for Low Resource Simulation and click Next.
- Select Select driver names from a list and click Next.
- Select all drivers listed that are 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. If this happens as soon as Windows tries to start then try it in Safe Mode. Continue to use your system normally, if you know what causes the crash, do that repeatedly. The objective is to get the system to crash because Driver Verifier is stressing the drivers out and hopefully create a pattern.
On the extremely rare occasion that you can't get into Safe Mode, use System Restore from your installation DVD / Restore Disc to set the system back to the previous restore point that you created.

To turn off Driver Verifier when finished, Open a Command Prompt or Run... window and type verifier /reset and press Enter/OK.
or
GoTo Start and in the Search or a Run... Window type verifier. Select Delete existing settings and press "Finish".
 


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