Sign in with
Sign up | Sign in
Your question
Solved

BSOD almost everytime i boot !!!

Last response: in Windows 7
Share
June 18, 2013 2:49:13 AM

Almost every time i boot , i am getting in Windows and after 3 - 5 sec i get BSOD

Here is my Dump Analysis:
  1. Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
  2. Online Crash Dump Analysis Service
  3. See http://www.osronline.com for more information
  4. Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
  5. Product: WinNt, suite: TerminalServer SingleUserTS
  6. Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
  7. Machine Name:
  8. Kernel base = 0xfffff800`0361e000 PsLoadedModuleList = 0xfffff800`03862670
  9. Debug session time: Tue Jun 18 04:43:15.632 2013 (UTC - 4:00)
  10. System Uptime: 0 days 0:01:24.349
  11. *******************************************************************************
  12. * *
  13. * Bugcheck Analysis *
  14. * *
  15. *******************************************************************************
  16.  
  17. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  18. This is a very common bugcheck. Usually the exception address pinpoints
  19. the driver/function that caused the problem. Always note this address
  20. as well as the link date of the driver/image that contains this address.
  21. Some common problems are exception code 0x80000003. This means a hard
  22. coded breakpoint or assertion was hit, but this system was booted
  23. /NODEBUG. This is not supposed to happen as developers should never have
  24. hardcoded breakpoints in retail code, but ...
  25. If this happens, make sure a debugger gets connected, and the
  26. system is booted /DEBUG. This will let us see why this breakpoint is
  27. happening.
  28. Arguments:
  29. Arg1: ffffffffc0000005, The exception code that was not handled
  30. Arg2: fffff88001c03b0f, The address that the exception occurred at
  31. Arg3: fffff88003b06868, Exception Record Address
  32. Arg4: fffff88003b060c0, Context Record Address
  33.  
  34. Debugging Details:
  35. ------------------
  36.  
  37. TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
  38.  
  39. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
  40.  
  41. FAULTING_IP:
  42. rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+9f
  43. fffff880`01c03b0f 410fb710 movzx edx,word ptr [r8]
  44.  
  45. EXCEPTION_RECORD: fffff88003b06868 -- (.exr 0xfffff88003b06868)
  46. ExceptionAddress: fffff88001c03b0f (rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x000000000000009f)
  47. ExceptionCode: c0000005 (Access violation)
  48. ExceptionFlags: 00000000
  49. NumberParameters: 2
  50. Parameter[0]: 0000000000000000
  51. Parameter[1]: 0000000000000000
  52. Attempt to read from address 0000000000000000
  53.  
  54. CONTEXT: fffff88003b060c0 -- (.cxr 0xfffff88003b060c0)
  55. rax=00000000084adcad rbx=0000000000000000 rcx=00000000000000cb
  56. rdx=fffffa8003017cb8 rsi=fffffa8002acf090 rdi=fffffa8002b513b0
  57. rip=fffff88001c03b0f rsp=fffff88003b06aa0 rbp=0000000000000000
  58. r8=0000000000000000 r9=0000000000000194 r10=0000000000000002
  59. r11=00000000000000ca r12=00000000000000ca r13=0000000000000001
  60. r14=0000000000000040 r15=fffffa8002acf078
  61. iopl=0 nv up ei ng nz ac po cy
  62. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297
  63. rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x9f:
  64. fffff880`01c03b0f 410fb710 movzx edx,word ptr [r8] ds:002b:00000000`00000000=????
  65. Resetting default scope
  66.  
  67. DEFAULT_BUCKET_ID: NULL_DEREFERENCE
  68.  
  69. PROCESS_NAME: System
  70.  
  71. CURRENT_IRQL: 0
  72.  
  73. ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
  74.  
  75. EXCEPTION_PARAMETER1: 0000000000000000
  76.  
  77. EXCEPTION_PARAMETER2: 0000000000000000
  78.  
  79. READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038cc100
  80. GetUlongFromAddress: unable to read from fffff800038cc1c0
  81. 0000000000000000 Nonpaged pool
  82.  
  83. FOLLOWUP_IP:
  84. rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+9f
  85. fffff880`01c03b0f 410fb710 movzx edx,word ptr [r8]
  86.  
  87. BUGCHECK_STR: 0x7E
  88.  
  89. LAST_CONTROL_TRANSFER: from fffff88001c05bb5 to fffff88001c03b0f
  90.  
  91. STACK_TEXT:
  92. fffff880`03b06aa0 fffff880`01c05bb5 : 00000000`00000000 00000000`084adcad 00000000`00000000 fffffa80`02acf078 : rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+0x9f
  93. fffff880`03b06af0 fffff880`01c11901 : fffffa80`00000000 fffff880`00b05000 00000000`000000ce fffff880`091c1000 : rdyboost!ST_STORE::StCompactRegions+0x1f9
  94. fffff880`03b06ba0 fffff880`01c0fd98 : fffffa80`00000004 00000000`000000d1 00000000`000000ce fffffa80`02ad3000 : rdyboost!ST_STORE::StCompactionPerformInMem+0x23d
  95. fffff880`03b06c30 fffff880`01c0f4b4 : fffffa80`02acf398 00000000`00000080 fffffa80`02acf398 fffff800`00b76080 : rdyboost!ST_STORE::StCompactionWorker+0x68
  96. fffff880`03b06c80 fffff880`01c0e41a : fffffa80`02acf398 fffff880`03b06d20 00000000`00000080 fffffa80`00000000 : rdyboost!ST_STORE::StWorkItemProcess+0xc0
  97. fffff880`03b06ce0 fffff800`03933e6a : 00000000`00000000 fffff800`00000000 fffffa80`02ace2c0 fffffa80`018c50b0 : rdyboost!SMKM_STORE::SmStWorker+0x152
  98. fffff880`03b06d40 fffff800`0368df06 : fffff800`0380fe80 fffffa80`02ace2c0 fffff800`0381dcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
  99. fffff880`03b06d80 00000000`00000000 : fffff880`03b07000 fffff880`03b01000 fffff880`03b06810 00000000`00000000 : nt!KiStartSystemThread+0x16
  100.  
  101.  
  102. SYMBOL_STACK_INDEX: 0
  103.  
  104. SYMBOL_NAME: rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeSearchKey+9f
  105.  
  106. FOLLOWUP_NAME: MachineOwner
  107.  
  108. MODULE_NAME: rdyboost
  109.  
  110. IMAGE_NAME: rdyboost.sys
  111.  
  112. DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7982e
  113.  
  114. STACK_COMMAND: .cxr 0xfffff88003b060c0 ; kb
  115.  
  116. FAILURE_BUCKET_ID: X64_0x7E_rdyboost!B_TREE__SMD_STORE_KEY,ST_STORE_SMD_TRAITS_::_ST_PAGE_ENTRY,4096,NP_CONTEXT_::BTreeSearchKey+9f
  117.  
  118. BUCKET_ID: X64_0x7E_rdyboost!B_TREE__SMD_STORE_KEY,ST_STORE_SMD_TRAITS_::_ST_PAGE_ENTRY,4096,NP_CONTEXT_::BTreeSearchKey+9f
  119.  
  120. Followup: MachineOwner

More about : bsod everytime boot

June 18, 2013 5:18:46 AM

New build or pc that been running fine. If it an older pc run memtest on it. If it a new build start with one dimm and check that your mb bios is up to date.
m
0
l
June 18, 2013 5:42:15 AM

Looks like a driver issue. Do you get any problems booting into safe mode?
m
0
l
Related resources
June 18, 2013 6:10:14 AM

smorizio said:
New build or pc that been running fine. If it an older pc run memtest on it. If it a new build start with one dimm and check that your mb bios is up to date.


No errors found on Memory by Memtest !!

wanderer11 said:
Looks like a driver issue. Do you get any problems booting into safe mode?


I am booting into safe mode without problems !!
m
0
l

Best solution

June 18, 2013 3:48:50 PM

Ok so it almost positively a driver issue or virus then. Do you feel like biting the bullet and formatting/reinstalling Windows? If not then this may take longer to figure out the problem. First off lets run a virus check with Malware Bytes. If that doesn't work then what was the last thing you installed? Can you uninstall it? Start disabling everything from startup and uninstalling what you don't need and trying to boot. Eventually you will find the culprit.
Share
June 18, 2013 4:19:09 PM

wanderer11 said:
Ok so it almost positively a driver issue or virus then. Do you feel like biting the bullet and formatting/reinstalling Windows? If not then this may take longer to figure out the problem. First off lets run a virus check with Malware Bytes. If that doesn't work then what was the last thing you installed? Can you uninstall it? Start disabling everything from startup and uninstalling what you don't need and trying to boot. Eventually you will find the culprit.


I will scan for viruses with malwareBytes and Spybot if it doesn't help ,then i will live with it untill i do a format ;) 
Thanks !!
m
0
l
!