BSOD even in Safe Mode!??

[nirdle_phogi]

---

mga brod, naa laptop sa akong friend ba gihatud nako para iyahang ipa-reformat, duda lang ko kung hardware or sa OS lang ang diperensya ani kay bsan ako i-safe mode, dili man kasud sa windows. XP iyahang OS. After sa windows logo sa bootscreen mag BSOD man nya dili sad ko kahibaw sa error message kay kalit ra man nya mo-restart dayon ang laptop? Any ideas bro kung unsa jud ang problema ani??

[poldopunk]

F8 sa bro then disable automatic restart and then post here the stop error code.

[yugi]

Memory is the suspected one!

[personalmgt]

Memory is the suspected one!

possible. since everything in safe mode is almost disabled. it could be the memory or the video card, since safe mode also uses a bit of your video card even if its in safe mode.

[istoryanimo]

Recovery CD imong gamit? hmmm.. Please post the model of your notebook so we can help you to solve the BSOD problem.

[poldopunk]

Memory is the suspected one!

kadali raba naka assume. you need to get the stop error before making assumptions and even if makuha nimo ang code, you still can't assume which is which.

there are malware infections that causes stop errors even when attempting in safe mode, specially if ang target sa infection is ang windows kernel.

[KizoneC]

i try kono og re install ang OS.

[yugi]

kadali raba naka assume. you need to get the stop error before making assumptions and even if makuha nimo ang code, you still can't assume which is which.

there are malware infections that causes stop errors even when attempting in safe mode, specially if ang target sa infection is ang windows kernel.

ASSUME is very different to what I said SUSPECTED visit dictionary.com if pareho ba ug meaning. No offense ha. You also have point even all of us have point pero maski mag assume or dili we still dont know the truth about it and besides the thread starter mentioned EVEN in SAFEMODE still encounter BSOD, its most likely MEMORY is the problem I encounteer that before, you dont need to be specific in error trappings to troubleshoot hardware its only useful to programmers.. and I think its no use.

Microsoft ERROR UTILITIES are not all reliable for EX: My PC shutdown, hanging like what I have mentioned sa akong thread sa problem nako sa garbage display, in the computer management I NEVER seen even one RECORD or LOGS of it. Even it keeps on repeating, REFORMATTING use different OS wa jud mo logs. Thats why I dont trust and use MSoft Utilities.

Its my opinion bro...hope u dont mind!

[poldopunk]

which is exactly why you need to retrieve the stop error code before spitting out possible defective parts. get your english straight, then we won't have any problems.

[poldopunk]

off topic:

4 words: welcome to teh internetzzz!

Microsoft ERROR UTILITIES are not all reliable for EX: My PC shutdown, hanging like what I have mentioned sa akong thread sa problem nako sa garbage display, in the computer management I NEVER seen even one RECORD or LOGS of it. Even it keeps on repeating, REFORMATTING use different OS wa jud mo logs. Thats why I dont trust and use MSoft Utilities.

when windows crashes specially if its a stop error, it leaves an information of what was in the memory when the crash happened. depending on the setting, it may leave an entire memory imprint or a simple log that contains what programs were running or drivers that may have caused the stop error in a file called minidump.

minidump then can be used for a debug which in turn would completely isolate the program that is causing this. debug can be performed on the computer if the system can boot to safe mode with networking, or the minidump can be retrieved through different means where the debug will be performed in a different computer.

this is why addressing a stop error code with an operating system reinstallation isn't a complete fix, since you do not know what caused the issue and that there is a good chance where it may recur again.