locked
Blue Screen on Windows 7. RRS feed

  • Question

  • I recently installed Windows 7 on my pc, and I keep getting blue screen error. Here is the error message:

    Problem signature:

      Problem Event Name: BlueScreen

      OS Version: 6.1.7601.2.1.0.256.48

      Locale ID: 1033

     

    Additional information about the problem:

      BCCode: a

      BCP1: 00000000

      BCP2: 00000002

      BCP3: 00000001

      BCP4: 82AB00AF

      OS Version: 6_1_7601

      Service Pack: 1_0

      Product: 256_1

     

    Files that help describe the problem:

      C:\Windows\Minidump\111211-23375-01.dmp

      C:\Users\[USERNAME]\AppData\Local\Temp\WER-51281-0.sysdata.xml

     

    Any ideas what is causing this?

    Saturday, November 12, 2011 10:23 PM

Answers

  • Hi,
     
    I analyzed all of the dumps that you uploaded and it would seem like you
    probably have a memory issue. Please check your memory with windiag or
    memtest86+,
     
     
    If it comes back clean, then we can do further troubleshooting.
     

    -- Mike Burr
    Technology
    • Marked as answer by Leo Huang Tuesday, November 22, 2011 2:15 AM
    Wednesday, November 16, 2011 8:02 PM
  • Hi,

     

    Dump file 111211-23375-01 analyze below:

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    IRQL_NOT_LESS_OR_EQUAL (a)

    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high.  This is usually

    caused by drivers using improper addresses.

    If a kernel debugger is available get the stack backtrace.

    Arguments:

    Arg1: 00000000, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000001, bitfield :

                    bit 0 : value 0 = read operation, 1 = write operation

                    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

    Arg4: 82ab00af, address which referenced memory

     

    Debugging Details:

    ------------------

     

     

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82ba2848

    Unable to read MiSystemVaType memory at 82b81e40

     00000000

     

    CURRENT_IRQL:  2

     

    FAULTING_IP:

    nt!KeWaitForSingleObject+373

    82ab00af 8939            mov     dword ptr [ecx],edi

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

     

    BUGCHECK_STR:  0xA

     

    PROCESS_NAME:  System

     

    TRAP_FRAME:  9e318b1c -- (.trap 0xffffffff9e318b1c)

    ErrCode = 00000002

    eax=85600020 ebx=85600018 ecx=00000000 edx=00000000 esi=855b7d48 edi=855b7e08

    eip=82ab00af esp=9e318b90 ebp=9e318bf4 iopl=0         nv up ei pl zr na pe nc

    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

    nt!KeWaitForSingleObject+0x373:

    82ab00af 8939            mov     dword ptr [ecx],edi  ds:0023:00000000=????????

    Resetting default scope

     

    LAST_CONTROL_TRANSFER:  from 82ab00af to 82a7a5db

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP:

    nt!KeWaitForSingleObject+373

    82ab00af 8939            mov     dword ptr [ecx],edi

     

    SYMBOL_STACK_INDEX:  1

     

    SYMBOL_NAME:  nt!KeWaitForSingleObject+373

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: nt

     

    IMAGE_NAME:  ntkrpamp.exe

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a389

     

    FAILURE_BUCKET_ID:  0xA_nt!KeWaitForSingleObject+373

     

    BUCKET_ID:  0xA_nt!KeWaitForSingleObject+373

     

    Followup: MachineOwner

    ---------


    The problem is caused by ntkrpamp.exe,
    to solid troubleshoot this kind of kernel crash issue, I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)

     

    Thank you for your understanding.

     

    Regards,

    Leo   Huang

     

     


    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.
    • Marked as answer by Leo Huang Tuesday, November 22, 2011 2:15 AM
    Tuesday, November 15, 2011 1:28 AM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 00000099, Attempt to free pool with invalid address  (or corruption in pool header)
    Arg2: 85600008, Address being freed
    Arg3: 00000000, 0
    Arg4: 00000000, 0
    Debugging Details:
    ------------------
    *** WARNING: Unable to verify timestamp for IDSvix86.sys
    *** ERROR: Module load completed but symbols could not be loaded for IDSvix86.sys
    BUGCHECK_STR:  0xc2_99
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 82d79f03 to 82b21eb4
    STACK_TEXT:  
    8d327a84 82d79f03 000000c2 00000099 85600008 nt!KeBugCheckEx+0x1e
    8d327aa4 82b3331d 85600008 85600000 000001ff nt!VerifierBugCheckIfAppropriate+0x30
    8d327ab8 82b63ff9 85600008 00000f40 00000001 nt!VerifierFreeTrackedPool+0x24
    8d327b2c 9207d1a2 85600008 4d43444e 859f24d8 nt!ExFreePoolWithTag+0x53e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8d327b44 92080885 85600000 86c3e078 8d327b78 IDSvix86+0x271a2
    8d327b54 92080bbe 00000001 86c3e008 92081150 IDSvix86+0x2a885
    8d327b78 9207e16d 00000001 8638b8d8 8d327bac IDSvix86+0x2abbe
    8d327b88 92058d78 877ad178 8b1470de 8b147005 IDSvix86+0x2816d
    8d327bac 920695c4 00000850 877ad178 859f24d8 IDSvix86+0x2d78
    8d327bc4 8b434c05 00000018 0000010a 859f24d8 IDSvix86+0x135c4
    8d327be0 8b4285dd 0000c439 00000000 00000018 NETIO!WfpNotifyFlowContextDelete+0x40
    8d327c24 8b412d43 0000c439 00000000 00000000 NETIO!WfpProcessFlowDelete+0xc1
    8d327c38 8b412d64 0000c439 00000000 855fac84 NETIO!KfdNotifyFlowDeletion+0x19
    8d327c50 8b4dbf87 855fac68 8b56cb34 00000000 NETIO!KfdAleNotifyFlowDeletion+0x18
    8d327c70 8b4f141d 855fac48 8d327cb4 8b4e09de tcpip!WfpAleFreeRemoteEndpoint+0x1c
    8d327c7c 8b4e09de 855fac88 82a0f8f0 8b56c2a0 tcpip!WfpAleDecrementWaitRef+0x65
    8d327cb4 8b4d3421 8b56c2a0 8b56cb40 8d327ce8 tcpip!WfpAlepDeleteDeferredEntries+0x120
    8d327cc4 8b413478 8b56cb74 85ef11b8 85ee9650 tcpip!WfpAlepDeferredCleanupWorkQueueRoutine+0x15
    8d327ce8 82c574e6 85ee9650 8b56cb40 85ef11b8 NETIO!NetiopIoWorkItemRoutine+0x2f
    8d327d00 82ac0a6b 85ef11b8 00000000 85209920 nt!IopProcessWorkItem+0x2d
    8d327d50 82c4bfda 00000001 a1c853c7 00000000 nt!ExpWorkerThread+0x10d
    8d327d90 82af41d9 82ac095e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    IDSvix86+271a2
    9207d1a2 ??              ???
    SYMBOL_STACK_INDEX:  4
    SYMBOL_NAME:  IDSvix86+271a2
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: IDSvix86
    IMAGE_NAME:  IDSvix86.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e26d58e
    FAILURE_BUCKET_ID:  0xc2_99_IDSvix86+271a2
    BUCKET_ID:  0xc2_99_IDSvix86+271a2
    Followup: MachineOwner
    ---------
    1: kd> lmvm IDSvix86
    start    end        module name
    92056000 920b4000   IDSvix86 T (no symbols)           
        Loaded symbol image file: IDSvix86.sys
        Image path: \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_5.1.0.29\Definitions\IPSDefs\20111111.030\IDSvix86.sys
        Image name: IDSvix86.sys
        Timestamp:        Wed Jul 20 14:18:06 2011 (4E26D58E)
        CheckSum:         00067875
        ImageSize:        0005E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    --------------------------------------------------------------------------------------------------------
    The BSOD is possibly caused by IDSvix86.sys driver. More about it: http://www.greatis.com/appdata/a/i/idsvix86.sys.htm
    Uninstall your Symantec antiviral solution and check results.

    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

    • Marked as answer by Leo Huang Tuesday, November 22, 2011 2:15 AM
    Tuesday, November 15, 2011 3:54 PM
  • Since it sounds like you upgraded from XP to Windows 7, please check to
    see if there are any unsigned drivers that may be lingering from the XP
    installation,
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Astartes Monday, November 28, 2011 1:38 PM
    Thursday, November 24, 2011 12:55 AM

All replies

  • Bug Check Code 0xA: http://msdn.microsoft.com/en-us/library/ff560129(v=VS.85).aspx

    Please use Microsoft Skydrive to upload C:\Windows\Minidump\111211-23375-01.dmp dump file. Once done, post a link here.

    You can also contact Microsoft CSS.

     


    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

    Sunday, November 13, 2011 11:55 AM
  • Thank you for your response.

    When I try to upload to Skydrive, I get an error message that say that I don't have permission to open the file. I am definitely the administrator. What do I need to do?

    Monday, November 14, 2011 2:45 AM
  • Hi,

     

    You needn’t to open the dump file, just upload to skydrive, you may follow the article to upload:

    Upload to SkyDrive

     

    Regards,

    Leo   Huang

     

     


    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, November 14, 2011 3:51 AM
  • Ok, I was finally able to upload the .dmp files. Apparently I did not have the proper permission, so I had to enable the Administrator account and upload them from there. I uploaded the 111211-23375-01.dmp file as well as all of the .dmp files since that occurrence (yeah,  it happens a lot, which is why I am worried). They are all in this folder:

    https://skydrive.live.com/redir.aspx?cid=275d41cb53fcf921&resid=275D41CB53FCF921!144

    I followed the bug check link, and I have already done the the things that it says to do. I have updated all of my drivers, ran a disk check, and scanned for viruses. It is odd, though, because at one point I updated my graphics card driver, and the problem stopped for about a week, then came back again.

    Again, thank you all for your help.

    Monday, November 14, 2011 5:15 PM
  • Hi,

     

    Dump file 111211-23375-01 analyze below:

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    IRQL_NOT_LESS_OR_EQUAL (a)

    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high.  This is usually

    caused by drivers using improper addresses.

    If a kernel debugger is available get the stack backtrace.

    Arguments:

    Arg1: 00000000, memory referenced

    Arg2: 00000002, IRQL

    Arg3: 00000001, bitfield :

                    bit 0 : value 0 = read operation, 1 = write operation

                    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

    Arg4: 82ab00af, address which referenced memory

     

    Debugging Details:

    ------------------

     

     

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82ba2848

    Unable to read MiSystemVaType memory at 82b81e40

     00000000

     

    CURRENT_IRQL:  2

     

    FAULTING_IP:

    nt!KeWaitForSingleObject+373

    82ab00af 8939            mov     dword ptr [ecx],edi

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO

     

    BUGCHECK_STR:  0xA

     

    PROCESS_NAME:  System

     

    TRAP_FRAME:  9e318b1c -- (.trap 0xffffffff9e318b1c)

    ErrCode = 00000002

    eax=85600020 ebx=85600018 ecx=00000000 edx=00000000 esi=855b7d48 edi=855b7e08

    eip=82ab00af esp=9e318b90 ebp=9e318bf4 iopl=0         nv up ei pl zr na pe nc

    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

    nt!KeWaitForSingleObject+0x373:

    82ab00af 8939            mov     dword ptr [ecx],edi  ds:0023:00000000=????????

    Resetting default scope

     

    LAST_CONTROL_TRANSFER:  from 82ab00af to 82a7a5db

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP:

    nt!KeWaitForSingleObject+373

    82ab00af 8939            mov     dword ptr [ecx],edi

     

    SYMBOL_STACK_INDEX:  1

     

    SYMBOL_NAME:  nt!KeWaitForSingleObject+373

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: nt

     

    IMAGE_NAME:  ntkrpamp.exe

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a389

     

    FAILURE_BUCKET_ID:  0xA_nt!KeWaitForSingleObject+373

     

    BUCKET_ID:  0xA_nt!KeWaitForSingleObject+373

     

    Followup: MachineOwner

    ---------


    The problem is caused by ntkrpamp.exe,
    to solid troubleshoot this kind of kernel crash issue, I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.

    Microsoft Customer Support Service (CSS)

     

    Thank you for your understanding.

     

    Regards,

    Leo   Huang

     

     


    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.
    • Marked as answer by Leo Huang Tuesday, November 22, 2011 2:15 AM
    Tuesday, November 15, 2011 1:28 AM
  • I am having the blue screen crash also. I uploaded dump files to skydrive.

     

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.256.1
      Locale ID:    1033

    Additional information about the problem:
      BCCode:    124
      BCP1:    0000000000000000
      BCP2:    FFFFFA800EB918F8
      BCP3:    0000000000000000
      BCP4:    0000000000000000
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    256_1

    Files that help describe the problem:
      C:\Windows\Minidump\111511-28220-01.dmp
      C:\Users\thedoctor\AppData\Local\Temp\WER-36036-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt


    Tuesday, November 15, 2011 12:10 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 00000099, Attempt to free pool with invalid address  (or corruption in pool header)
    Arg2: 85600008, Address being freed
    Arg3: 00000000, 0
    Arg4: 00000000, 0
    Debugging Details:
    ------------------
    *** WARNING: Unable to verify timestamp for IDSvix86.sys
    *** ERROR: Module load completed but symbols could not be loaded for IDSvix86.sys
    BUGCHECK_STR:  0xc2_99
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  INTEL_CPU_MICROCODE_ZERO
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 82d79f03 to 82b21eb4
    STACK_TEXT:  
    8d327a84 82d79f03 000000c2 00000099 85600008 nt!KeBugCheckEx+0x1e
    8d327aa4 82b3331d 85600008 85600000 000001ff nt!VerifierBugCheckIfAppropriate+0x30
    8d327ab8 82b63ff9 85600008 00000f40 00000001 nt!VerifierFreeTrackedPool+0x24
    8d327b2c 9207d1a2 85600008 4d43444e 859f24d8 nt!ExFreePoolWithTag+0x53e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8d327b44 92080885 85600000 86c3e078 8d327b78 IDSvix86+0x271a2
    8d327b54 92080bbe 00000001 86c3e008 92081150 IDSvix86+0x2a885
    8d327b78 9207e16d 00000001 8638b8d8 8d327bac IDSvix86+0x2abbe
    8d327b88 92058d78 877ad178 8b1470de 8b147005 IDSvix86+0x2816d
    8d327bac 920695c4 00000850 877ad178 859f24d8 IDSvix86+0x2d78
    8d327bc4 8b434c05 00000018 0000010a 859f24d8 IDSvix86+0x135c4
    8d327be0 8b4285dd 0000c439 00000000 00000018 NETIO!WfpNotifyFlowContextDelete+0x40
    8d327c24 8b412d43 0000c439 00000000 00000000 NETIO!WfpProcessFlowDelete+0xc1
    8d327c38 8b412d64 0000c439 00000000 855fac84 NETIO!KfdNotifyFlowDeletion+0x19
    8d327c50 8b4dbf87 855fac68 8b56cb34 00000000 NETIO!KfdAleNotifyFlowDeletion+0x18
    8d327c70 8b4f141d 855fac48 8d327cb4 8b4e09de tcpip!WfpAleFreeRemoteEndpoint+0x1c
    8d327c7c 8b4e09de 855fac88 82a0f8f0 8b56c2a0 tcpip!WfpAleDecrementWaitRef+0x65
    8d327cb4 8b4d3421 8b56c2a0 8b56cb40 8d327ce8 tcpip!WfpAlepDeleteDeferredEntries+0x120
    8d327cc4 8b413478 8b56cb74 85ef11b8 85ee9650 tcpip!WfpAlepDeferredCleanupWorkQueueRoutine+0x15
    8d327ce8 82c574e6 85ee9650 8b56cb40 85ef11b8 NETIO!NetiopIoWorkItemRoutine+0x2f
    8d327d00 82ac0a6b 85ef11b8 00000000 85209920 nt!IopProcessWorkItem+0x2d
    8d327d50 82c4bfda 00000001 a1c853c7 00000000 nt!ExpWorkerThread+0x10d
    8d327d90 82af41d9 82ac095e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    IDSvix86+271a2
    9207d1a2 ??              ???
    SYMBOL_STACK_INDEX:  4
    SYMBOL_NAME:  IDSvix86+271a2
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: IDSvix86
    IMAGE_NAME:  IDSvix86.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e26d58e
    FAILURE_BUCKET_ID:  0xc2_99_IDSvix86+271a2
    BUCKET_ID:  0xc2_99_IDSvix86+271a2
    Followup: MachineOwner
    ---------
    1: kd> lmvm IDSvix86
    start    end        module name
    92056000 920b4000   IDSvix86 T (no symbols)           
        Loaded symbol image file: IDSvix86.sys
        Image path: \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_5.1.0.29\Definitions\IPSDefs\20111111.030\IDSvix86.sys
        Image name: IDSvix86.sys
        Timestamp:        Wed Jul 20 14:18:06 2011 (4E26D58E)
        CheckSum:         00067875
        ImageSize:        0005E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    --------------------------------------------------------------------------------------------------------
    The BSOD is possibly caused by IDSvix86.sys driver. More about it: http://www.greatis.com/appdata/a/i/idsvix86.sys.htm
    Uninstall your Symantec antiviral solution and check results.

    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

    • Marked as answer by Leo Huang Tuesday, November 22, 2011 2:15 AM
    Tuesday, November 15, 2011 3:54 PM
  • What will resolve this?

    I was typeing an email when the last crash happend.

    only app open was fire fox.

    I kinda figure writing an email should not crash the computer.

    Wednesday, November 16, 2011 1:37 AM
  • Had to more crashes this morning.  both time computer had been up less than 5 mins.

    both times I was using firefox once to send email on gmail account, the second time to post here about the first crash this morning.

    I feel like I am playing beat the clock to get this post done.

    Wednesday, November 16, 2011 12:16 PM
  • Hi,
     
    I analyzed all of the dumps that you uploaded and it would seem like you
    probably have a memory issue. Please check your memory with windiag or
    memtest86+,
     
     
    If it comes back clean, then we can do further troubleshooting.
     

    -- Mike Burr
    Technology
    • Marked as answer by Leo Huang Tuesday, November 22, 2011 2:15 AM
    Wednesday, November 16, 2011 8:02 PM
  • Thank you for your replies.

    I just ran an extended test on the Windows Memory Diagnostic Tool, and it came back completely clean. I doubt that this is a problem that involves the physical components of my computer. The problem only started when I upgraded from Windows XP to Windows 7.

    Tuesday, November 22, 2011 11:43 PM
  • Since it sounds like you upgraded from XP to Windows 7, please check to
    see if there are any unsigned drivers that may be lingering from the XP
    installation,
     
     

    -- Mike Burr
    Technology
    • Marked as answer by Astartes Monday, November 28, 2011 1:38 PM
    Thursday, November 24, 2011 12:55 AM
  • I ran the Signature Verification Tool, and I don't think it found any problems. The link below will take you to a folder with the log, named "SIGVERIF.txt"

     

    https://skydrive.live.com/redir.aspx?cid=275d41cb53fcf921&resid=275D41CB53FCF921!144

    Monday, November 28, 2011 5:05 PM