random bsod


Noob Whisperer
Well there seems to be something going on with your dump files;
111311-49779-01.dmp 11/13/2011 10:47:20 AM looks pretty much like what might be expected regarding drivers
but then a couple hours earlier
111311-26052-01.dmp 11/13/2011 8:22:20 AM I'm looking at 25 pre-Windows 7 RTM, drivers, some dating back to 2005 /2006
And I can't account for that. Nor can I account for the fact that all your dump files appear to be dated on November 13, 2011, what have you been doing in the meantime or prior to that date to prevent BSODs. So......
Let's start by removing (uninstalling) Norton. Use the programs uninstaller if available or the programs and features applet in the control panel if not. Follow that up by running the vendor specific proprietary removal tool from here
Install Microsoft Security Essentials as a substitute for now.
After removing norton please take some time and Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally double check and make sure your system is still writing .dmp files to the correct location
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Good luck


New Member
View attachment 120411-21949-01.dmp Thanks I made the changes, here is an earlier one (attached) I had about 6 hours earlier on the same day. I havent been doing anything to provoke these installed a few new pieces of USB hardware but thats it.


Noob Whisperer
Thanks I made the changes, here is an earlier one (attached) I had about 6 hours earlier on the same day. I havent been doing anything to provoke these installed a few new pieces of USB hardware but thats it.
That most recent .dmp indicated an issue with rdyboost.sys. So.....
If any of the new USB hardware that you installed as noted above includes the Ready Boost feature (and many if not most do) you might consider checking with the vendor for any software/driver or firmware updates for those particular pieces of hardware. Or consider removing the ReadyBoost feature as it applies to that particular device. See attachment
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 82e53c62, 8dd52964, 0}
[COLOR=#ff0000][U][B]Probably caused by : rdyboost.sys ( rdyboost!SmdIoTreeIoComplete+a0 )[/B][/U][/COLOR]
Followup: MachineOwner
3: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
Arg1: c000001d, The exception code that was not handled
Arg2: 82e53c62, The address that the exception occurred at
Arg3: 8dd52964, Trap Frame
Arg4: 00000000
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
82e53c62 c3              ret
TRAP_FRAME:  8dd52964 -- (.trap 0xffffffff8dd52964)
ErrCode = 00000000
eax=865fa008 ebx=865f6b00 ecx=00000004 edx=00000000 esi=865fa000 edi=865f5090
eip=82e53c62 esp=8dd529d8 ebp=8dd529fc iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210286
82e53c62 c3              ret
Resetting default scope
LAST_CONTROL_TRANSFER:  from 8c00a2b6 to 82e53c62
82e53c62 c3              ret
8dd529fc 8c00a2b6 865f6af8 865f6b00 00000001 nt!memmove+0x162
8dd52a18 8c00a3c1 865f6af4 02d52a84 00000010 [B][U][COLOR=#ff0000]rdyboost[/COLOR][/U][/B]!SmdIoTreeIoComplete+0xa0
8dd52a50 8c00abbb 8c01c0b0 865f6af4 00000000 [COLOR=#ff0000][U][B]rdyboost[/B][/U][/COLOR]!SmdAddIoToStores+0xf1
8dd52a98 8c0014ab 865f6a50 0000000a 865f6af4 [COLOR=#ff0000][U][B]rdyboost[/B][/U][/COLOR]!SmdProcessReadWriteCompletion+0x19f
8dd52af0 8c00aca0 865f6a50 865f6520 86870f90 [B][U][COLOR=#ff0000]rdyboost[/COLOR][/U][/B]!SmdRBReadWriteCompletion+0x18b
8dd52b20 8c0071c4 865f6a50 00000000 865f6a70 [B][U][COLOR=#ff0000]rdyboost[/COLOR][/U][/B]!SmdProcessReadWriteCompletion+0x284
8dd52b4c 82e92913 865f6998 865f6520 86870f90 [COLOR=#ff0000][U][B]rdyboost[/B][/U][/COLOR]!SmdReadWriteCompletion+0x50
8dd52b90 8bf9f498 8dd52bc4 8bf9fabd 865ef340 nt!IopfCompleteRequest+0x128
8dd52b98 8bf9fabd 865ef340 865f6520 00000001 CLASSPNP!ClassCompleteRequest+0x11
8dd52bc4 82e92913 00000000 865f2100 005f55c8 CLASSPNP!TransferPktComplete+0x2e4
8dd52c0c 8bb869f9 85590a48 8dd52c50 8bb95e1c nt!IopfCompleteRequest+0x128
8dd52c18 8bb95e1c 865f2100 00000001 00000000 storport!RaidCompleteRequestEx+0x1c
8dd52c50 8bb8731e 85590a48 85ecc0a4 8dd3b884 storport!RaidUnitCompleteRequest+0xc2
8dd52c78 82e921b5 85ecc0a4 85ecc030 00000000 storport!RaidpAdapterDpcRoutine+0x51
8dd52cd4 82e92018 8dd36120 8dd3b800 00000000 nt!KiExecuteAllDpcs+0xf9
8dd52d20 82e91e38 00000000 0000000e ffffffff nt!KiRetireDpcList+0xd5
8dd52d24 00000000 0000000e ffffffff ffdfffff nt!KiIdleLoop+0x38
8c00a2b6 8a550f          mov     dl,byte ptr [ebp+0Fh]
SYMBOL_NAME:  [COLOR=#ff0000][U][B]rdyboost[/B][/U][/COLOR]!SmdIoTreeIoComplete+a0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [U][B][COLOR=#ff0000]rdyboost[/COLOR][/B][/U]
IMAGE_NAME:  [U][B][COLOR=#ff0000]rdyboost.sys[/COLOR][/B][/U]
FAILURE_BUCKET_ID:  0x8E_BAD_IP_[COLOR=#ff0000][U][B]rdyboost[/B][/U][/COLOR]!SmdIoTreeIoComplete+a0
BUCKET_ID:  0x8E_BAD_IP_[COLOR=#ff0000][U][B]rdyboost[/B][/U][/COLOR]!SmdIoTreeIoComplete+a0
Followup: MachineOwner

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