Windows errors problem RRS feed

  • Question

  • Hi I recently upgraded from windows xp to WIndows 7 64 bit but i m getting some errors and which sometimes causes blue screen problems. 1 of the recent reports were like this:

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80003130711, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 091511-21528-01.

    and another 1 like this:

    Problem signature
    Problem Event Name:    BlueScreen
    OS Version:    6.1.7601.
    Locale ID:    1033

    Files that help describe the problem (some files may no longer be available)

    View a temporary copy of these files
    Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

    Extra information about the problem
    BCCode:    1e
    BCP1:    FFFFFFFFC0000005
    BCP2:    FFFFF80003130711
    BCP3:    0000000000000000
    OS Version:    6_1_7601
    Service Pack:    1_0
    Product:    256_1
    Thursday, September 15, 2011 8:19 AM

All replies

  • Latest error:

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.
      Locale ID:    1033

    Additional information about the problem:
      BCCode:    1e
      BCP1:    FFFFFFFFC0000005
      BCP2:    FFFFF800030ECF00
      BCP3:    0000000000000000
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    256_1

    Files that help describe the problem:

    Thursday, September 15, 2011 8:40 AM
  • Hello can anyone help me with this? Please......
    Friday, September 16, 2011 11:25 AM
  • Hi,


    Please upload the BSOD dump file in forum for further analyzing.


    Use SkyDrive to upload collected files and post screen shot/picture.


    Alex Zhao

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, September 20, 2011 7:39 AM
  • Here are the files:


    Tuesday, September 20, 2011 3:23 PM
  • Hi,


    BugCheck 1e.


    Probably caused by : memory_corruption


    Currently, I suggest you run the memory diagnose tool to check if memory is corrupted:


    1.    Open Memory Diagnostics Tool by clicking the Start button, and then clicking Control Panel. In the search box, type Memory, and then click Diagnose your computer's memory problems. if you're prompted for an administrator password or confirmation, type the password or provide confirmation.


    2.    Choose when to run the tool.


    Meanwhile, please boot into Clean Boot mode to check if this issue still occurs.


    Alex Zhao

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, September 21, 2011 2:49 AM
  • Did everything no problem yet!! I will post if I had any problems thanks for your help!!
    Wednesday, September 21, 2011 9:58 PM
  • yeah I m still having BSOD problems!!
    Thursday, September 22, 2011 1:06 PM
  • Hi,


    You can upload the latest  dump file.




    Alex Zhao

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, September 23, 2011 2:48 AM
  • Hi Alex,

    I'm looking for the answer from this problem too and the last dump file uploaded by dxblaDexd was here:


    Hope the answer will be useful for the others...

    Friday, September 23, 2011 3:48 AM
  • i uploaded all the latest files. So check those out.



    Saturday, September 24, 2011 5:44 AM
  • Hi dxblaDexd,



    An exception happened while executing a system service routine.


    From this minidump file, we can only drop a conclusion: this is caused by memory corruption.


    To find the root cause of this issue, we need to debug the crashed system dump. Unfortunately, this is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.


    To obtain the phone numbers for specific technology request please take a look at the web site listed below:




    I hope the problem will be resolved soon. Thank you for your time and cooperation!


    @socket478; @GokhanS: to avoid the confusion, please start a new thread for help.




    Alex Zhao

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, September 26, 2011 3:28 AM
  • hello,

    sadly I live in Bangladesh the CSS doesnt cover my country yet, So there is nothing for me to do. D:

    Monday, September 26, 2011 6:24 PM
  • Isnt there anyway to help me in this forum? I am losing valuable data for this BSODs. Here are the latest problems:


    Monday, October 17, 2011 6:04 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: fffff88009812528, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff880012f35d2, If non-zero, the instruction address which referenced the bad memory
    Arg4: 0000000000000002, (reserved)
    Debugging Details:
    Could not read faulting driver name
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034cd100
    fffff880`012f35d2 f6838800000210  test    byte ptr [rbx+2000088h],10h
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  hsswd.exe
    TRAP_FRAME:  fffff88007811f60 -- (.trap 0xfffff88007811f60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8a002e9b390 rbx=0000000000000000 rcx=fffff8a002e08010
    rdx=7fffffffffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880012f35d2 rsp=fffff880078120f0 rbp=fffffa8004987c10
     r8=fffffa80048c0ea8  r9=0000000000000000 r10=0000000000000000
    r11=fffff880078120d0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    fffff880`012f35d2 f6838800000210  test    byte ptr [rbx+2000088h],10h ds:00000000`02000088=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800032453f0 to fffff8000329ac40
    fffff880`07811df8 fffff800`032453f0 : 00000000`00000050 fffff880`09812528 00000000`00000000 fffff880`07811f60 : nt!KeBugCheckEx
    fffff880`07811e00 fffff800`03298d6e : 00000000`00000000 fffff880`09812528 fffff880`07811f00 fffff880`078124a0 : nt! ?? ::FNODOBFM::`string'+0x447c6
    fffff880`07811f60 fffff880`012f35d2 : fffffa80`048c0d50 fffff880`078124a0 fffff880`078124a0 fffffa80`048c0d50 : nt!KiPageFault+0x16e
    fffff880`078120f0 fffff880`0125aa3d : fffffa80`048c0d50 fffffa80`04987c10 fffff880`078124a0 00000000`00000000 : Ntfs!NtfsCommonCreate+0x209b
    fffff880`078122d0 fffff800`032a7618 : fffff880`07812410 00000000`00000000 fffff8a0`0b9df750 00000000`00000170 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffff880`07812300 fffff880`0125b1bf : fffff880`0125aa20 fffff880`0125a020 00000000`00000000 fffff880`012fbf00 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`078123e0 fffff880`012f499c : 00000000`00000000 00000000`00000000 fffff880`07812640 fffffa80`04987c10 : Ntfs!NtfsCommonCreateOnNewStack+0x4f
    fffff880`07812440 fffff880`010e6bcf : fffffa80`04e9b030 fffffa80`04987c10 00000000`00000000 fffffa80`04d0a060 : Ntfs!NtfsFsdCreate+0x1ac
    fffff880`078125f0 fffff880`011062b9 : fffffa80`04987c10 fffffa80`04ea7800 fffffa80`04987c00 fffffa80`04d0a060 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`07812680 fffff800`03598f95 : 00000000`00000005 fffffa80`0419a1c8 fffffa80`07d75010 00000000`00000000 : fltmgr!FltpCreate+0x2a9
    fffff880`07812730 fffff800`03595838 : fffffa80`04a83cd0 fffff800`00000000 fffffa80`0419a010 fffffa80`00000001 : nt!IopParseDevice+0x5a5
    fffff880`078128c0 fffff800`03596a56 : 00000000`00000000 fffffa80`0419a010 fffff8a0`00000000 fffffa80`03bce290 : nt!ObpLookupObjectName+0x588
    fffff880`078129b0 fffff800`0359835c : 00000000`00000400 00000000`00000000 fffff880`07812b01 fffff880`00000001 : nt!ObOpenObjectByName+0x306
    fffff880`07812a80 fffff800`03583be4 : 00000000`0022e548 fffff880`00100001 00000000`0022eda0 00000000`0022e4e8 : nt!IopCreateFile+0x2bc
    fffff880`07812b20 fffff800`03299ed3 : fffffa80`05746060 00000000`0022ee18 fffff880`07812bc8 fffff800`035924f4 : nt!NtOpenFile+0x58
    fffff880`07812bb0 00000000`7799164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0022e4a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7799164a
    CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs
    3 errors : !Ntfs (fffff880012f32c7-fffff880012f36d7)
    fffff880012f32c0  02  66  89  42  58  48  8b *c3  30  48  8b  48  60  44  0f  b7 .f.BXH..0H.H`D..
    fffff880012f35d0  04  01  f6  83  88  00  00 *02  10  0f  85  2f  a3  05  00  4c .........../...L
    fffff880012f36d0  70  85  ff  41  0f  99  c5 *46  89  6c  24  20  41  b1  01  44 p..A...F.l$ A..D
    MODULE_NAME: memory_corruption
    IMAGE_NAME:  memory_corruption
    FOLLOWUP_NAME:  memory_corruption
    Followup: memory_corruption
    Run chkdsk /r /f and check results. More in the article I gave.
    The BSOD occured when hostspot shield was running: http://www.whatisexe.com/process/hsswd.exe.html
    Please uninstall it and check again.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Tuesday, October 18, 2011 11:15 PM