BSOD 124 at seemingly random times - Vista x86

T

tmacman

New member
Joined
Aug 6, 2015
Posts
4
OS- Vista
32bit
Original OS
Pre-installed
7 years old (GPU is 4 years old)
OS - 7 years old

CPU- Intel Q6600 2.4GHz
GPU- Nvidia GTS 450
Motherboard - MSI ??? (I'll give it a search and see if I find out)

Manufacturer - Medion
Model - Akoya ??? (I'll give that a search as well)

Desktop

Hello,

So I'm been having the dreaded BSOD 124 hardware (probably) error for about 2 weeks now, according to bluescreenview. I've been getting the bluescreens at seemingly random times daily. I'm not 100% sure as to what is common factor that is regularly causing it. All I can tell you is they don't seem to occur when idle.

I can give you a list of situations they occur in, but I can go and do the exact same thing, and it wont happen again. I simply can't recreate them.

The exact nature of the bluescreen is a freeze, with sound stutter, then the sound of a fan audibly switching off, BSOD, reboot. Sometimes it'll just freeze without a BSOD and reboot. I'd say I've had about 5 or so more crashes than the dumps would indicate.

I've run windows memory diagnostic with 8 passes, no probs. Tried chkdsk, no probs. Prime95, no probs. Furmark, no probs (although I only ran it for a couple of minutes). And HWmonitor shows no concerning temperatures.

I clean the inside of dust relatively frequently, and didn't occur anywhere near the last time I did it, about 4 months ago. I've done it again, since the BSODs starting appearing, and of course, no change.

One last thing of note is that I did have some problems with my graphics card recently, a card I used to upgrade 4 years ago, in which I wouldn't get a display after starting sleep mode on occasion, and sometimes getting the error beeps (1 long, 2 short) indicative of graphics card failure. Those have since, completely dissappeared
huh.gif
. This was only a week ago. So it might be that, but I don't know.

Lastly, I'd usually take my PC to the repair for fault I couldn't figure out (I've got the know how to swap parts, but I completely lack the facilities), but with this being so intermittent and not replicable, I just don't know if anything would happen.

You can find the asked for files attached


View attachment 15170View attachment perfmon report.zip
 
Code: 
[COLOR=#ff0000]BugCheck 1000007E[/COLOR], {[COLOR=#008000]c0000005[/COLOR], 93d7e503, 82b90aa0, 82b9079c}

Probably caused by : [COLOR=#ff0000]xusb21.sys[/COLOR] ( xusb21+1503 )

I would suggest you remove the Xbox Wireless Controller driver from your system, it is known to cause issues like BSODs.

Code: 
3: kd> [COLOR=#008000]lmvm xusb21[/COLOR]

start    end        module name
93d7d000 93d89c80   xusb21   T (no symbols)           
    Loaded symbol image file: xusb21.sys
    Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
    Image name: xusb21.sys
    Timestamp:        [COLOR=#ff0000]Sat Feb 17 02:22:28 2007[/COLOR] (45D666E4)
    CheckSum:         0001955A
    ImageSize:        0000CC80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The MotionInJoy Xbox 360 Controller Simulator appears to have present within the stack too, I suggest you update or remove this driver as well.

Code: 
3: kd> [COLOR=#008000]lmvm MijXfilt[/COLOR]

start    end        module name
93d6c000 93d7d000   MijXfilt T (no symbols)           
    Loaded symbol image file: MijXfilt.sys
    Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys
    Image name: MijXfilt.sys
    Timestamp:        [COLOR=#ff0000]Thu Mar 18 10:59:17 2010[/COLOR] (4BA20785)
    CheckSum:         0000CCB4
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code: 
3: kd>[COLOR=#008000] knL[/COLOR]
 # ChildEBP RetAddr  
WARNING: Stack unwind information not available. Following frames may be wrong.
00 82b90b74 93d7e59a [COLOR=#800080]xusb21+0x1503[/COLOR] <-- Exception Address
01 82b90b84 80619ea5 [COLOR=#800080]xusb21+0x159a[/COLOR]
02 82b90bb0 8062e317 Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+0x3c
03 82b90bdc 80612c36 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
04 82b90bf8 80612cde Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
05 82b90c08 85c33984 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
06 82b90c2c 85cc11fb nt!IopUnloadSafeCompletion+0x44
07 82b90c64 8062bd6b nt!IopfCompleteRequest+0x11d
08 82b90c8c 8061e983 Wdf01000!FxRequest::CompleteInternal+0x379
09 82b90ca4 93d72eec Wdf01000!imp_WdfRequestCompleteWithInformation+0x114
0a 82b90cf4 93d6e1d9 [COLOR=#ff0000]MijXfilt+0x6eec[/COLOR]
0b 82b90d08 80633042 [COLOR=#ff0000]MijXfilt+0x21d9[/COLOR]
0c 82b90d24 806330aa Wdf01000!FxWorkItem::WorkItemHandler+0xad
0d 82b90d30 85e27919 Wdf01000!FxWorkItem::WorkItemThunk+0x19
0e 82b90d44 85cbfe22 nt!IopProcessWorkItem+0x23
0f 82b90d7c 85defc42 nt!ExpWorkerThread+0xfd
10 82b90dc0 85c58f4e nt!PspSystemThreadStartup+0x9d
11 00000000 00000000 nt!KiThreadStartup+0x16

I found the following string in the stack too:

Code: 
3: kd> [COLOR=#008000]!procdumpext.da 80661c00[/COLOR]
d:\w7rtm\minkernel\wdf\framework\kmdf\src\core\[COLOR=#ff0000]fxrequest.cpp[/COLOR]

The exception record of the crash, a standard memory access error:

Code: 
3: kd> [COLOR=#008000].exr 0xffffffff82b90aa0[/COLOR]
ExceptionAddress: 93d7e503 ([COLOR=#0000ff]xusb21+0x00001503[/COLOR])
   ExceptionCode: [COLOR=#ff0000]c0000005 (Access violation)[/COLOR]
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000000
Attempt to read from address 00000000

Here's the context:

Code: 
3: kd> [COLOR=#008000].frame /r 00[/COLOR]
00 82b90b74 93d7e59a xusb21+0x1503
[COLOR=#0000cd]eax=00000000[/COLOR] ebx=8bdeacc0 ecx=00360001 edx=8bdea84c esi=8bdeca70 edi=8bdf7d20
eip=93d7e503 esp=82b90b68 ebp=82b90b74 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
[COLOR=#ff0000]xusb21+0x1503[/COLOR]:
93d7e503 ff10            call    dword ptr [eax]      ds:0023:00000000=????????
 
Are you analysing the most recent BSODs?


Because I know motionjoy adapted controllers can cause bluescreens on occassion, namely when I unplug them. I haven't had a bluescreen of that nature occur for a while now. There was also never a freeze and sound stutter when those occurred.

Any who, I've deleted the motion joy related drivers, hopefully you're right.
 
Just as I thought, unrelated. Got another bluescreen, same as the others over the last 2 weeks.

Motionjoy controller BSODs have never caused a 124 error, so that's unsurprising.

If there's anything else I'm missing from your post, feel free to tell me.
 
tmacman said:
Here you go, a whole new BSOD collection:

View attachment 15277
Click to expand...
Hi Tmacman ^_^,


Really sorry for the delay in responding to you. Do you still need help? I would be more than happy to help you out :)
In case you still need help, all you need to do is simply reply to this thread. I am instantly replied via email and will try my best to get back to you within 48 hours.



-Pranav
 

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

Back
Top