BSOD when starting up

[ArmenMM]

When im turning on my pc, Im getting blue screen which is disappearing after few seconds and showing up 'Start windows normally' page. This isn't first time of getting blue screen. After selecting Start windows normally its starting up without problems and running well.

Got this on desktop:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 50
BCP1: FFFFF88049FC61EE
BCP2: 0000000000000000
BCP3: FFFFF88049FC61EE
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\120813-62525-01.dmp
C:\Users\User\AppData\Local\Temp\WER-96861-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[Arc]

Hi ArmenMM.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the keyboard driver.
5. Apply > OK
6. Accept then restart.

Let us know the results.

________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88049fc61ee, 0, fffff88049fc61ee, 5}


Could not read faulting driver name
Probably caused by : rdyboost.sys ( rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE<SMD_TRAITS>::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeRedistribute+292 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88049fc61ee, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88049fc61ee, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bc100
GetUlongFromAddress: unable to read from fffff800034bc1c0
 fffff88049fc61ee Nonpaged pool

FAULTING_IP: 
+0
fffff880`49fc61ee ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003706840 -- (.trap 0xfffff88003706840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800349a000 rbx=0000000000000000 rcx=0000000000002e5a
rdx=ffffffffff747bf4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88049fc61ee rsp=fffff880037069d8 rbp=fffffa800349a000
 r8=0000000000000000  r9=0000000000000000 r10=00171c6000000000
r11=fffffa800349a010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff880`49fc61ee ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800033015b3 to fffff80003284bc0

FAILED_INSTRUCTION_ADDRESS: 
+0
fffff880`49fc61ee ??              ???

STACK_TEXT:  
fffff880`037066d8 fffff800`033015b3 : 00000000`00000050 fffff880`49fc61ee 00000000`00000000 fffff880`03706840 : nt!KeBugCheckEx
fffff880`037066e0 fffff800`03282cee : 00000000`00000000 fffff880`49fc61ee 00000000`00000000 00000000`00000033 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`03706840 fffff880`49fc61ee : fffff880`018c3d92 fffff880`03706a58 fffffa80`027e8c40 fffffa80`028f2140 : nt!KiPageFault+0x16e
fffff880`037069d8 fffff880`018c3d92 : fffff880`03706a58 fffffa80`027e8c40 fffffa80`028f2140 fffffa80`0279a0d8 : 0xfffff880`49fc61ee
fffff880`037069e0 fffff880`018cfa26 : 00000000`00000023 fffffa80`0349a010 fffffa80`0349a000 00000000`00000000 : rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE<SMD_TRAITS>::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeRedistribute+0x292
fffff880`03706a50 fffff880`018ce499 : 00000000`00000000 fffff880`0c5e8000 00000000`c0000225 00000000`0000000b : rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE<SMD_TRAITS>::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeInsertEx+0x142
fffff880`03706aa0 fffff880`018cc782 : fffffa80`0279a078 fffff880`0c5e8000 00000000`0000000b 00000000`00000001 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageInsert+0x75
fffff880`03706b20 fffff880`018cb773 : fffffa80`035b8b50 fffffa80`02bfe530 00000000`00000000 fffffa80`0279a078 : rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageAdd+0x212
fffff880`03706be0 fffff880`018cb62e : fffffa80`035b8b50 00000000`0000b000 00000000`00000080 fffffa80`0279a010 : rdyboost!ST_STORE<SMD_TRAITS>::StDmPageAdd+0xe3
fffff880`03706c40 fffff880`018ca41a : fffffa80`035b8b50 00000000`00000080 00000000`00000080 fffffa80`0279aee8 : rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x23a
fffff880`03706ca0 fffff800`035212ea : 00000000`00000000 fffff800`00000000 fffffa80`02799b50 fffffa80`018ad890 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x152
fffff880`03706d00 fffff800`032758e6 : fffff800`033ffe80 fffffa80`02799b50 fffff800`0340dcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03706d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE<SMD_TRAITS>::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeRedistribute+292
fffff880`018c3d92 83c430          add     esp,30h

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  rdyboost!B_TREE<_SMD_STORE_KEY,ST_STORE<SMD_TRAITS>::_ST_PAGE_ENTRY,4096,NP_CONTEXT>::BTreeRedistribute+292

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e

FAILURE_BUCKET_ID:  X64_0x50_CODE_AV_BAD_IP_rdyboost!B_TREE__SMD_STORE_KEY,ST_STORE_SMD_TRAITS_::_ST_PAGE_ENTRY,4096,NP_CONTEXT_::BTreeRedistribute+292

BUCKET_ID:  X64_0x50_CODE_AV_BAD_IP_rdyboost!B_TREE__SMD_STORE_KEY,ST_STORE_SMD_TRAITS_::_ST_PAGE_ENTRY,4096,NP_CONTEXT_::BTreeRedistribute+292

Followup: MachineOwner
---------

http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

[ArmenMM]

The Uninstall button was grayed out, uninstalled daemon tool, unchecked non-system(Antivirus also) startups, But still facing the problem.

2 questions
What's in the code?
Should I check back cleaner programs from startup?

 

[Arc]

Lol, questions are always welcome

• There is nothing very useful in the crash dump, that is ... the code. Before going to our next stages, we are trying to take the environment into shape, and these two steps you have followed are th very initial of that attempt.
• No, dont check anything back. They need not to auto start at all. If you want to use them, call them from Start> All programs.

You say you still face the problem, even after cleaning startup?

Publish a Speccy snapshot: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

 

[ArmenMM]

Speccy: http://speccy.piriform.com/results/HytD8SpWVw2KTm2A0M0lIdT

How many hours will take Memtest and is there any way it can damage my computer in any way?
The test will launch in the morning anyways

 

[Arc]

I believe that your RAM is not enough for running 64 bit Ultimate. With 2 GB you should run 32 bit home premium; or 32 bit home basic; and nothing higher. And that may be the cause for the cold boot BSOD, apparently.

Still I am asking for some expert opinion here.

Usually memtest needs to run for at least 7-8 passes. An overnight run will be enough for your RAM volume.

And Memtest will not anyhow harm/damage your computer.

The expert opinions will come shortly. You run memtest in between.

View attachment 296789

 

[Layback Bear]

The OP ram is set at 1.8v (as per Speccy). I can't verify if that is correct because I can't find the specs for ram that old. My old Kingston ram voltage specs is 1.8v.
The OP only has one stick of ram but there is 2 ram slots.
With that motherboard the OP is running Single channel on a motherboard that can use Dual channel. To use Dual channel one must use both memory slot on the motherboard.
_______________
Now to get down to a little honesty. Their isn't much one can do with that system because of it's age.
If it was mine and I was trying to get it alive all I would do is install 2 matching sticks of ram that are designed for that motherboard and pray. Max. ram for this board is 4 gigs. Old ram sometimes comes with a premium price.
Hope this helps Arc.

 

[Arc]

Now to get down to a little honesty. Their isn't much one can do with that system because of it's age.
If it was mine and I was trying to get it alive all I would do is install 2 matching sticks of ram that are designed for that motherboard and pray. Max. ram for this board is 4 gigs. Old ram sometimes comes with a premium price.
Hope this helps Arc.

Tough, but that is the nature of truth! Thank you for pointing it out.

 

[ICIT2LOL]

My 2 cents Arc the OP should or could try Tradesman at the G Skill forum he is a whizz with memory not that we do not have our own people but that is just about all he does.

ArmenMM try here Welcome to the G.SKILL TECH FORUM