New
#21
Ok no response in a week and I've had several more crashes tonight.
If I upload the new minidump data am I going to get some help or will this thread just descend into oblivion like my first one did ?
Continuous BSOD
-
-
New #22
Please remember that you are not the only user that needs help ... especially in this section ... if you need to, you can always "bump" a thread so that it goes to the top ... Also keep in mind that no one here gets paid for doing BSOD analysis, they have lives that sometimes take priority over volunteering their time to solve problems...
Nuff said..
-
New #23
You are absolutely right, and I really really appreciate all the help I got with the first issues.
I bumped my old thread (it was about a month ago) 3 or 4 times over the course of 3 days, and never once got a response.
The problems started again, so I made this thread and got a reply instantly, with great help. The part I don't understand is, after coming back and saying "ok issues again" why the thread just dies off.
If it's just that people are busy, fine, but why are there responses in the other 500 threads that people post up here ?
If I've offended somebody or said something stupid (I know alot of "usuals" that frequent forums get tired of people posting stuff that's been covered, as an example) then why just ignore my posts and not help ?
I don't mean to imply that I should be helped right now because I'm me and I demand it. If that's how it came across I apologize. This place is an unbelievable fountain of knowledge and I know I can get help here. However, if I'm not going to get any answers, then I'd rather not waste my time coming back every couple of hours, and not waste anybody else's time by bumping/posting in my own thread constantly.
-
-
New #25
While trying to upload the new .rar, it crashed on me twice in safe mode (I couldn't even load windows in regular boot).
I'm now trying again like 3 hours later and there's no issue. This is starting more and more to look like a hardware problem to me.
And again I apologize for being a a douchebag for a minute there. I really do appreciate the help that you guys are giving out to the less knowledgeable like myself.
-
New #26
Hi,
Most of your dmp files have SYSTEM_SERVICE_EXCEPTION (3b) bugcheck.
It's usually caused by 3rd drivers, then I see you have many old drivers that must be updated.
Then perform system file checker:Code:iirsp.sys Tue Dec 13 13:47:54 2005 -> Intel Raid StorPort Driver nfrd960.sys Tue Jun 06 14:11:48 2006 -> IBM ServeRAID Controller Driver arc.sys Thu May 24 14:27:55 2007 -> Adaptec RAID Storport Driver adpu320.sys Tue Feb 27 16:04:15 2007 -> Adaptec .NET Ultra320 Driver adpahci.sys Tue May 01 10:30:09 2007 -> Adaptec Windows SATA Storport Driver adp94xx.sys Fri Dec 05 15:54:42 2008 -> Adaptec HostRAID SAS Driver sisraid4.sys Wed Oct 01 14:56:04 2008 -> SiS AHCI Stor-Miniport Driver SiSRaid2.sys Wed Sep 24 11:28:20 2008 -> SiS RAID Stor Miniport Driver nvraid.sys Tue May 19 23:39:40 2009 -> nVidia nForce RAID Driver nvstor.sys Tue May 19 23:45:37 2009 -> nVidia Storage Drivers ManyCam_x64.sys Wed Mar 12 23:46:01 2008 -> ManyCam Virtual Webcam Rt64win7.sys Fri May 22 07:52:30 2009 -> Realtek NIC driver lsi_fc.sys Tue Dec 09 14:46:09 2008 -> LSI Logic Fusion-MPT FC Driver (StorPort)
Right click Command Prompt -> run as admin -> sfc /scannow
LogCode:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002fca97b, fffff88008e11da0, 0} Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+9b ) Followup: MachineOwner --------- 1: 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: fffff80002fca97b, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88008e11da0, 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!ObpLookupDirectoryEntry+9b fffff800`02fca97b 0fb717 movzx edx,word ptr [rdi] CONTEXT: fffff88008e11da0 -- (.cxr 0xfffff88008e11da0) rax=0000000000000001 rbx=0000000000000000 rcx=fffff8a001cd3eb0 rdx=fffff88008e12870 rsi=fffffa8005c62cc8 rdi=0000000000f8003c rip=fffff80002fca97b rsp=fffff88008e12770 rbp=0000000000000040 r8=0000000000000040 r9=0000000000000001 r10=fffff8a001cd3eb0 r11=0000000000000002 r12=fffff88008e12870 r13=fffff88008e129b0 r14=fffff8a001cd3eb0 r15=fffff8a001cd3eb0 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!ObpLookupDirectoryEntry+0x9b: fffff800`02fca97b 0fb717 movzx edx,word ptr [rdi] ds:002b:00000000`00f8003c=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: CLMLSvc.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002fca97b STACK_TEXT: fffff880`08e12770 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpLookupDirectoryEntry+0x9b FOLLOWUP_IP: nt!ObpLookupDirectoryEntry+9b fffff800`02fca97b 0fb717 movzx edx,word ptr [rdi] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ObpLookupDirectoryEntry+9b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff88008e11da0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ObpLookupDirectoryEntry+9b BUCKET_ID: X64_0x3B_nt!ObpLookupDirectoryEntry+9b Followup: MachineOwner ---------
-
New #27
So I need to update all those drivers ?
I don't even know what those are for, and nobody mentioned those the first go round here. lol
I don't even HAVE manycam anymore.
Also, the past two crashes (last night and today) had something for "ftlmgr.exe" or flt. What is that and does it being in the blue screen mean that's what caused the crash ?
-
New #28
I'm trying to update those drivers but when I search on the sites that are linked, I don't know enough about what they are to know if the results are right.
Any help I can get with figuring out what to get would be appreciated.
-
New #29
How To Find Drivers:- - The most common drivers are listed on this page: Driver Reference Driver Reference- 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.
- - Driver manufacturer links are on this page: Drivers and Downloads
-
New #30
Yea that's great, if you know what you're looking for.
I've searched by the IDENTICAL listing of what Wish posted, and there was a couple different results for each one, with no EXACT matches. Since I don't know exactly what I need, I can't determine which one to get.
Also, going through the list of most common drivers doesn't help, because again, I have no idea what those drivers are for.
I don't even know what the "Adaptec RAID Storport" is to get the driver.
I mean if searching for the exact phrasing that Wish gave didn't get what I needed (or I just don't know that that's what I need), I have no idea how to go about downloading the needed stuff.
Quote
Related Discussions