[SOLVED] BSOD 0x0000003B SYSTEM_SERVICE_EXCEPTION

W

WildAnalog

Member
Joined
Jan 21, 2019
Posts
18
Good evening. I bought a used Dell Precision 690 a couple years ago. It did not come with the Windows 7 Ultimate disc to enable to do a fresh boot of the OS. The computer worked great for some time. I stupidly started messing with drivers and firmware. I then started to receive the BSOD. This was a year or so ago. I got frustratted with it and haven't turned it back on until last night. It also will not let me create a System Restore Point or to recover from one. The previous owner did not change the Admin or give me the password to chamge it to my information. I am desperate for help as I am about to start school and can't afford to get a new computer or pay an expensive technician to come repair it. I will be most grateful for any assistance.

Windows 7 Ultimate 64 Bit
I believe the native OS was Windows XP Pro
I am unaware of the age of hardware and OS installation. I can't get in touch with the seller now.
Intel Xeon 5160 @ 3.00 GHZ (4 CPUs)
Dell Precisioin 690
Desktop
DXDiag isn't showing my graphics card. Possibly because I am in safe mode.

After I ran Verifier I received a BSOD with a different error. This one read SCSIPORT.SYS.
 

Attachments

Code: 
0: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`082a0888 fffff800`03cde429 nt!KeBugCheckEx
01 fffff880`082a0890 fffff800`03cdd0a0 nt!KiBugCheckDispatch+0x69
02 fffff880`082a09d0 fffff800`03d08532 nt!KiPageFault+0x260
03 fffff880`082a0b60 fffff800`03d197b1 nt!RtlDispatchException+0x122
04 fffff880`082a1240 fffff800`03cde502 nt!KiDispatchException+0x135
05 fffff880`082a18e0 fffff800`03cdc334 nt!KiExceptionDispatch+0xc2
06 fffff880`082a1ac0 fffff800`03cd6c91 nt!KiBreakpointTrap+0xf4
07 fffff880`082a1c58 fffff880`0122e060 nt!DbgBreakPoint+0x1
08 fffff880`082a1c60 fffff880`02fdf0c8 mv91xx+0x5060
09 fffff880`082a1c68 fffff880`02fdf0c8 0xfffff880`02fdf0c8
0a fffff880`082a1c70 00000000`00000200 0xfffff880`02fdf0c8
0b fffff880`082a1c78 00000000`00000000 0x200

The Marvell MV91xx AHCI/RAID driver called the nt!DbgBreakPoint+0x1 function to set a breakpoint (why????). It wasn't handled properly/something went wrong because the exception per the break caused a bugcheck and your system crashed.

Code: 
    Loaded symbol image file: mv91xx.sys
    Image path: mv91xx.sys
    Image name: mv91xx.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Dec 24 22:45:39 2009

It's *really* old. Look for any updates for your Marvell AHCI/RAID driver(s) or get rid of it completely. It's obviously old and buggy as hell because it's setting breakpoints in kernel mode and not handling the exceptions.


Just to explain why you're getting 0x3B as well:

Code: 
Bugcheck code 0000003B
Arguments 00000000`80000003 fffff800`03c8ac90 fffff880`0570c510 00000000`00000000

0x3B is raised per Windows when there's an exception while executing a system service routine. Exceptions are totally normal parts of Windows and occur in both user/kernel mode all the time, but it's when they aren't supposed to happen and when they are supposed to but something goes wrong is when it's bad/when systems crash. With the 0x3B crashes, the 1st parameter tells us what kind of exception occured:

The 1st parameter per the code block above is '00000000`80000003', which is a breakpoint exception. Something set a breakpoint and an exception occurred. If we want to find out more, we check the context record of the exception which is in the 3rd parameter.

Code: 
rax=0000000000000001 rbx=fffff880030100e8 rcx=3cf7991241fb0000
rdx=000000000000003b rsi=0000000000000000 rdi=0000000000000100
rip=fffff80003c8ac90 rsp=fffff8800570cef8 rbp=0000000000000100
 r8=0000000000000065  r9=0000000000000000 r10=0000000000000000
r11=fffff8800570cab0 r12=fffffa800aea1a00 r13=fffffa800a9bb8c0
r14=fffffa800a9cc890 r15=0000000000000020
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000286
nt!DbgBreakPoint:
fffff800`03c8ac90 cc              int     3

int 3 is the opcode of the breakpoint instruction (nt!DbgBreakPoint).. so we know a driver set a breakpoint and we can also see it here. We can dump the stack from the context:

Code: 
0: kd> k
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 fffff880`0570cef8 fffff880`01005060 nt!DbgBreakPoint
01 fffff880`0570cf00 fffff880`030100e8 mv91xx+0x5060
02 fffff880`0570cf08 fffff880`030100e8 0xfffff880`030100e8
03 fffff880`0570cf10 00000000`00000200 0xfffff880`030100e8
04 fffff880`0570cf18 00000000`00000000 0x200

There's our Marvell driver again, doing what it does best (setting breakpoints that are never handled????)
 
Also, even though I'm sure we found the problem and you're on your way to fixing it, this is one of those scenarios that I rarely see that I'd like to take a deeper look into for research on why this driver is doing this.

There should be a MEMORY.DMP file inside your C:\Windows directory. It's basically a much more informative version of the small memory dumps that the collection app grabs for us to look at. If you don't mind uploading it somewhere and pasting the link (any drive site works best), that'd be awesome.
 
A bit off topic but useful to the OP.
Manual can be downloaded here sorry link won't paste. I'll try code tags.
Code: 
https://www.dell.com/support/home/us/en/04/product-support/product/precision-690/manuals

There are no drivers for Windows 7 only XP and Vista.
 
Patrick said:
Also, even though I'm sure we found the problem and you're on your way to fixing it, this is one of those scenarios that I rarely see that I'd like to take a deeper look into for research on why this driver is doing this.

There should be a MEMORY.DMP file inside your C:\Windows directory. It's basically a much more informative version of the small memory dumps that the collection app grabs for us to look at. If you don't mind uploading it somewhere and pasting the link (any drive site works best), that'd be awesome.
Click to expand...

It was stable for a day after updating some drivers through Driver Booster but it is crashing again. I am pretty desperate for help. School starts soon and I need to start training on some stuff.
 
Hey, checking the dump now.

Sorry, you tried to send me a PM but I don't have anymore space, lol. Getting that solved.
 
Not what I'm looking for but I don't like what I'm reading here:

It was stable for a day after updating some drivers through Driver Booster
Click to expand...

Don't use automatic driver updating software. It literally makes no sense and you're probably downloading buggy drivers. Who is to say that the developers behind that software are...

#1 Truly grabbing the latest pushed drivers

#2 Not pushing you garbageware/malware

#3 Installing the drivers properly whatsoever

#4 Even downloading the right drivers

If you need driver updates, go to your manufacturer's website and download the drivers from there directly. For ex, if I had a Dell Model #1234, I'd go to Dell's website and download drivers for my Model #1234.
 
Patrick said:
Hey, checking the dump now.

Sorry, you tried to send me a PM but I don't have anymore space, lol. Getting that solved.
Click to expand...

Thank you! I also have a System Event log. Thank you for the warning on driver software. It is no excuse but I was desperate at that point.
 
Here's what I would do in your situation...

There's no telling how many drivers are messed up considering I have to guess you just told the software to "update" whatever it found was necessary to "update"?

Is backing up your important documents and reinstalling Windows a plausible option? If not, your best bet is to quite literally just install the most up to date drivers from your manufacturer's website and see what results it yields.
 
I would definitely reinstall Windows but the seller didn't provide a copy with my computer. He isn't responding to my communications either.
 
It's a Dell so it should typically have a recovery partition rather than installation media. Does yours not?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top