W
Wooseong_K
This is the event log file from my laptop. I dont have minidump file as the "error info collection" process do not move on from 0 % and have to force restart all the time. Please help me to find the source of the BSOD problems..
It could be the driver issue, windows issue, or the hardware. None are sure. Just want to find the issue..
Attatched is the unanswered question posted before.
- First Post
Hi, Ive been going through this endless BSOD issue with my samsung laptop for about 8 months now thanks to amazing warranty and customer care provided from Bestbuy and Samsung. Left it for months and finally picked it back up to fix and to save some money.
I defintely reset this laptop multiple times and that didnt help.
I ran virus check and it was clean, obviously bc i reset it.
Focused on kernal data inpage error solution and realized it could be from bad sectors or the physical HDD/RAM.
I have first tried windows event viewer to realize Distributed COM was mainly causing the crashes with the Event ID 10016. Which i was not too sure what it meant and couldnt find.
So i moved on to use cmd and used "chkdsk C: /f /r" to see if i can located bad sectors and hopefully it fixes it by itself. On stage 4, it gave me an error that says "The disc does not have enough space to replace bad clusters"
-> this made me want to believe that the HDD has failed. If its other systemical issue or the Ram issue it would be way more difficult (+Ram is soldered and i will need to replace the entire motherboard which I have never done and is way more expensive).
I have found the compatible HDD for my laptop and I am a step away from ordering it. Am I in the right track to do this?
Tl;dr
Would an error message from chkdsk enough for me to conclude that it is the faulty HDD that causes endless and more frequent than before BSOD?
I really have no access to other people who have knowledge about this stuff to discuss about the issue. I really need an advice. Thanks.
- Second post
Hello, thank you very much for your response.
Sorry for the late reply, as I was trying to locate the minidump files for a while.
Then I realized that my laptop never was able to create dump files as it would always stick at 0% BSOD and would never move further. I had to force shut down and power in the laptop everytime BSOD happens. So yes, I dont have any minidump files.
While I was struggling with locating minidump file, here are some new stuffs i found.
- I did the built in Windows Memory Diagnositc, and after going through 2 stages(?) it didnt give me any errors. Then it automatically began chkdsk process. At stage 5, at around 45%, BSOD happened. Of course, I had to force restart, and it re-began chkdsk process and stuck at stage 5 and BSOD popped up. Highly assuming that this is a disk issue.
- I also had a new error code from BSOD. 0xc0000225 error code. Doing some research told me that this is an error that pops up when the windows update thing is interrupted.
- Now that I recall, I had BSOD happening since this January.
- Windows update was interupted, had it fixed through warranty, brought it out without completing windows update that they had to do as I needed it immediately, and now can't get out of BSOD loop.
- Following is the complete error codes list that I experienced.
- 0xc0000225
- Kernel_Data_Inpage_Error
- System_Service_Exception
- Critical_Process_Died (Most common)
- "Bad_System_Config_Info"(Additional BSOD for stage 4)
Do you think these can happen because of incomplete windows update? Or should I just replace SDD and hope it gets fixed.
P.S.
BSOD happens anytime. Sometimes so much like 10 times in 20 minutes, then sometimes it can last without BSOD for days. Restarting the computer properly seem to help increase the length of it staying well without BSOD, but not all the time.
________________________________________________________________________________________________________________________________________________________________
Any help would be appreciated. I have been struggling with this faulty laptop since last november. Want to end this now..
Continue reading...