BSOD after clean format, new experience!

#1
Hello everyone!
I have never experienced the BSOD and I am concerned, idk exactly what caused the problem but apparently it was windows ready boost service. Funny thing is I was not using it and never have on this clean format.
Here is my CPU-Z sheet and dump file for analysis:

View attachment Win7 Mini Dump.rar
 


Captain Jack

Extraordinary Member
#2
Hello and Welcome!

Seems like the dump files wasn't very help it's pointing to a System file i.e rdyboost. So I would recommend to disconnect all the external storage devices. Then follow this document and run a complete Hardware Diagnostic Hardware Diagnostic | Captain Debugger

Code:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000001236, The subtype of the bugcheck.
Arg2: fffffa8003691c80
Arg3: fffffa8003691cb0
Arg4: 0000000000058c68

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


BUGCHECK_STR:  0x1a_1236

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000317adeb to fffff8000308ad00

STACK_TEXT:  
fffff880`061027b8 fffff800`0317adeb : 00000000`0000001a 00000000`00001236 fffffa80`03691c80 fffffa80`03691cb0 : nt!KeBugCheckEx
fffff880`061027c0 fffff880`01ba7eb2 : 00000000`000003c3 fffffa80`03691c80 fffffa80`04003118 00000000`000003c4 : nt!MmFreePagesFromMdl+0x31b
fffff880`06102820 fffff880`01ba77df : fffffa80`04003118 00000000`00000000 fffffa80`04762ff4 fffffa80`00000000 : rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x4e
fffff880`06102880 fffff880`01ba64ce : fffffa80`040030b0 00000000`00000001 fffffa80`040030b0 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCleanup+0x183
fffff880`061028c0 fffff880`01ba5a27 : fffffa80`040030b0 00000000`00000001 fffffa80`040030b0 fffff880`06102ca0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStCleanup+0x7a
fffff880`06102900 fffff880`01ba598a : fffff880`01bc88f0 00000000`00000008 fffffa80`040030b0 fffff880`01bc8870 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmStoreMgrCallback+0x4b
fffff880`06102940 fffff880`01bcc4b8 : fffff880`01bc8870 fffff880`06102ca0 00000000`00000000 fffffa80`045f3c68 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmCleanup+0x9a
fffff880`06102970 fffff880`01badb26 : fffffa80`06968b20 fffffa80`06968b20 00000000`00000000 00000000`00000000 : rdyboost!SmdRBContextShutdown+0x94
fffff880`061029b0 fffff800`033a5127 : 00000000`00000000 fffffa80`05d012d0 fffffa80`05d013e8 fffffa80`06968b20 : rdyboost!SmdDispatchDeviceControl+0x3ce
fffff880`06102a10 fffff800`033a5986 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`06102b40 fffff800`03089f93 : fffffa80`00000000 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`06102bb0 00000000`76db138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0179eda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76db138a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e
fffff880`01ba7eb2 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e

FAILURE_BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

Followup: MachineOwner
 


#3
Hello and Welcome!

Seems like the dump files wasn't very help it's pointing to a System file i.e rdyboost. So I would recommend to disconnect all the external storage devices. Then follow this document and run a complete Hardware Diagnostic Hardware Diagnostic | Captain Debugger

Code:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000001236, The subtype of the bugcheck.
Arg2: fffffa8003691c80
Arg3: fffffa8003691cb0
Arg4: 0000000000058c68

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


BUGCHECK_STR:  0x1a_1236

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000317adeb to fffff8000308ad00

STACK_TEXT:  
fffff880`061027b8 fffff800`0317adeb : 00000000`0000001a 00000000`00001236 fffffa80`03691c80 fffffa80`03691cb0 : nt!KeBugCheckEx
fffff880`061027c0 fffff880`01ba7eb2 : 00000000`000003c3 fffffa80`03691c80 fffffa80`04003118 00000000`000003c4 : nt!MmFreePagesFromMdl+0x31b
fffff880`06102820 fffff880`01ba77df : fffffa80`04003118 00000000`00000000 fffffa80`04762ff4 fffffa80`00000000 : rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+0x4e
fffff880`06102880 fffff880`01ba64ce : fffffa80`040030b0 00000000`00000001 fffffa80`040030b0 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmCleanup+0x183
fffff880`061028c0 fffff880`01ba5a27 : fffffa80`040030b0 00000000`00000001 fffffa80`040030b0 fffff880`06102ca0 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStCleanup+0x7a
fffff880`06102900 fffff880`01ba598a : fffff880`01bc88f0 00000000`00000008 fffffa80`040030b0 fffff880`01bc8870 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmStoreMgrCallback+0x4b
fffff880`06102940 fffff880`01bcc4b8 : fffff880`01bc8870 fffff880`06102ca0 00000000`00000000 fffffa80`045f3c68 : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmCleanup+0x9a
fffff880`06102970 fffff880`01badb26 : fffffa80`06968b20 fffffa80`06968b20 00000000`00000000 00000000`00000000 : rdyboost!SmdRBContextShutdown+0x94
fffff880`061029b0 fffff800`033a5127 : 00000000`00000000 fffffa80`05d012d0 fffffa80`05d013e8 fffffa80`06968b20 : rdyboost!SmdDispatchDeviceControl+0x3ce
fffff880`06102a10 fffff800`033a5986 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`06102b40 fffff800`03089f93 : fffffa80`00000000 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`06102bb0 00000000`76db138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0179eda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76db138a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e
fffff880`01ba7eb2 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e

FAILURE_BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

BUCKET_ID:  X64_0x1a_1236_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e

Followup: MachineOwner
Thank you for the help!
Well i ran a hardware diagnostics using my PC's built in diagnostic tool (shown at startup) and everything checked out ok. I also believe that the BSOD was caused by the windows kernel? Well the time the crash occurred I was dealing with a program called "Core Temp" and it kept running multiple instances of itself and *pop* theres the BSOD, I dont quite recall what it said because I was in shock xD. I have not experienced the BSOD after uninstalling the program core temp and deleting all of its data. Hopefully it stays that way :)
 


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