also @ TechSpot: Updated Microsoft EULA prohibits class action lawsuits

TechSpot
Register now for a live online demo to see how the Office 365 suite of tools
- professional email, calendars, video conferencing, and file sharing -

Reason Code: 0x805000f Getting BSOD! Need help!!

Discussion in 'Windows BSOD, Freezing, Restarting Help' started by naries, Jun 20, 2007.

Thread Status:
Not open for further replies.

  1. naries Newcomer, in training

    It is a terminal server with windows 2003 x64 r2

    I have been receiving this error code every couple days. It will be fine for 2-3-4 days then it will lock up and we will power it up and then it typically crashes again and after we power it back up it will be fine for a few days again. We cant seem to track down this issue, any help will be extremely appreciated!

    Reason Code: 0x805000f
    Bug ID:
    Bugcheck String: 0x00000050 (0xfffff97ff3df5000, 0x0000000000000000, 0xfffff97fff017563, 0x0000000000000000)
    Comment: 0x00000050 (0xfffff97ff3df5000, 0x0000000000000000, 0xfffff97fff017563, 0x0000000000000000)

    I have attached the .dmp files. Thank you again for any help you can provide!

    Travis

    Attached Files:

    naries, Jun 20, 2007
    #1

  2. cpc2004 Newcomer, in training

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    Probably it is hardware problem. Either the ram is bad or PSU is faulty. Run memtest to stress test the ram.
    cpc2004, Jun 21, 2007
    #2
Thread Status:
Not open for further replies.