Achilles2k

New Member
Joined
Jun 18, 2012
Messages
2
Hi Guys
New to this forum but fairly experienced with PC. Currently pulling out my hair with this one :mad:... apologies for the lengthy post. . . I will attach SF Diags and CPU-Z snips. . .

System is randomly crashing but no dumps.Crashes are NOT BSOD. (but see further down). There are two versions of the crash - first is a spontaneous re-start, like the reset button has been pressed. The second is the screen get completely corrupted and the PC locks-up, have to power off/on. In both cases there is NO DUMP file produced. Event viewer has the default (useless) "41 Kernel-Power" entry. This is driving me NUTS! It has been going on for weeks now.:mad: I have replaced the PSU with brand new 530W. Swapped RAM (DDR3) with another machine. Run DiskChecking on all drives (HD Tune) - No Errors. Taken out the graphics card and used onboard graphics. Done a complete clean out of system - clean re-install windows 7 Pro SP1. Updated BIOS. Updated all drivers. Device Manager is clear of all issues. Crashes still happening - randomly. Can be 3 in an hour or up to two days in between. Happen when I am stressing it or when it is idle.
I noticed that in the event viewer most of the crashes I have been having coincide with an error in the event log - "Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D". Followed instructions form other forums - like uninstalling MS Security Essentials - but no change.

Today I even swapped out the motherboard for an identical one from ebay. Got it all installed and working - and it is STILL crashing.

HOWEVER - I did get 2 BSoDs (about 10 mins apart) - and two dumps. Bug Check points to "Memory_Managent". (also event viewer showed "Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D" again).

I am completely at a loss now :confused:. ALL of my hair has been pulled out and ANY help from you experts would be much appreciated. . .



 


Attachments

  • Seven Forums.zip
    Seven Forums.zip
    592.8 KB · Views: 272
  • CPU-Z CPU.webp
    CPU-Z CPU.webp
    33 KB · Views: 337
  • CPU-Z Mainboard.webp
    CPU-Z Mainboard.webp
    18.8 KB · Views: 341
  • CPU-Z Memory.webp
    CPU-Z Memory.webp
    22 KB · Views: 315
  • CPU-Z SPD #1.webp
    CPU-Z SPD #1.webp
    28.1 KB · Views: 344
  • CPU-Z SPD #2.webp
    CPU-Z SPD #2.webp
    28.9 KB · Views: 338
Solution
It sounds like you've been through quite a lot of troubleshooting already. Random crashes can indeed be frustrating, especially when they occur without clear error messages or dump files. Here are a few steps you might consider taking to further diagnose and potentially resolve the issue:
  1. Memory Issues:
    • Since you've encountered a "Memory_Management" BSOD, it's essential to thoroughly test your RAM modules. You can use Windows Memory Diagnostic or Memtest86 to check for any memory-related problems.
    []Overheating:
    • Check your system's temperatures using monitoring software like HWMonitor to ensure that overheating is not the cause of these crashes. Dust buildup in the system can sometimes lead to...
It sounds like you've been through quite a lot of troubleshooting already. Random crashes can indeed be frustrating, especially when they occur without clear error messages or dump files. Here are a few steps you might consider taking to further diagnose and potentially resolve the issue:
  1. Memory Issues:
    • Since you've encountered a "Memory_Management" BSOD, it's essential to thoroughly test your RAM modules. You can use Windows Memory Diagnostic or Memtest86 to check for any memory-related problems.
    []Overheating:
    • Check your system's temperatures using monitoring software like HWMonitor to ensure that overheating is not the cause of these crashes. Dust buildup in the system can sometimes lead to overheating issues.
    [
    ]Power Supply:
    • While you've replaced the PSU, it's still worth double-checking to ensure that it's providing stable power to all components.
    []Driver Issues:
    • Even though you've updated drivers, conflicts can still occur. Consider using software like Driver Verifier to identify problematic drivers.
    [
    ]BIOS Settings:
    • Check your BIOS settings for any misconfigurations that could potentially cause instability.
    []System File Corruption:
    • Run a system file check to ensure that all Windows system files are intact. Open a Command Prompt as an administrator and run the command sfc /scannow.
    [
    ]Check for Malware:
    • The error related to "Microsoft Security Client OOBE" could indicate malware interference. Perform a thorough scan with a reputable antivirus tool.
    []Event Viewer Analysis:
    • Dig deeper into the Event Viewer for any recurring patterns or specific errors that might provide more insight into the root cause of the crashes.
    [
    ]System Stress Test:
    • Consider stress testing your system using tools like Prime95 or Furmark to see if you can replicate the crashes under heavy load. Once you've gone through these steps, you may have a clearer picture of what could be causing the crashes. Feel free to share any updates or additional information for further assistance!
 


Solution
Back
Top