locked
Windows 7 Home Premium BSOD RRS feed

  • Question

  • Hi,

    I just bought a laptop and when I start it, it gives me a blue screen and starts the memory dump. this happens four or five times and then the computer starts normally.

    Once I have it started and if I shut it down and open it back again after an hour or two, it would open up in the first try.

    I have also done all the updates from the Microsoft update website and have run the HP updater as well.

    I have uploaded the dump file at http://cid-006587c9f98c8384.office.live.com/embedicon.aspx/Public%20Folder/Dump%20Files.zip

    Please help!!!

     

    S

    Monday, March 14, 2011 5:34 AM

Answers

  • Hi,

    Results verifies by WinDBG, DumpCHK, and BlueScreenView.

    There were 8 different Bug_Checks in the 10 minidumps - 1A, 24, 50, 74, 7F, C2, F4, and 7E (3).

    One of the 7E was most telling in that CAUSE was MEMORY CORRUPTION and several of the others pointed to MEMORY. Of course there can be other causes.

    BugCheck 1000007E, {ffffffffc000001d, fffff88005895801, fffff88002bdf388, fffff88002bdebf0}Probably caused by : memory_corruption

    None of the other Bug_Checks really pointed specifically to CAUSE as they showed Windows components which means something else drove them into Fault.

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

    Remove ALL power and reseat all cards, memory, and cables (both ends when possible) -
    actually remove and replace - do not just snug. Remove the dust bunnies and clean the
    vents. Check that the fans work (before and after opening the case). If a laptop about all
    you can do is reseat the memory and clean the vents (still can try adding a small fan as a
    test).

    Have you added any hardware lately? Have you updated any driver just before these started?
    (Check Control Panel - Windows Updates to see if any drivers were updated there about the time
     this started) Main likely culprits are Video driver, other major drivers, memory, and
    antivirus/antispyware/security products could be at fault as well as drive issues.

    When you get to the driver and memory sections of the troubleshooter refer to the next message
    to update drivers and test memory and then refer back to the troubleshooter if needed.

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

    Use the methods such as SFC, CheckDisk, Driver Updates, and others in the troubleshooter referred
    to in this link as they will help solve or at least narrow down the issues. After those you can post
    the information from BlueScreenView and these other utilities so we can offer more specific
    advice. Of course checking with a real computer shop or System Maker's Support would be a good
    idea however I would try the possible solutions you can first.

    See this thread for information on using BlueScreenView, MyEventViewer, and other methods to
    troubleshoot BlueScreens - top 3 replies (+1 other).

    http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

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

    These are usually excellent sources for troubleshooting methods.

    BCCode: 7E      0x00000007E  which is also 0x1000007E <-- read this link
    http://www.faultwire.com/solutions-fatal_error/SYSTEM-THREAD-EXCEPTION-NOT-HANDLED-0x0000007E-*1141.html?order=votes

    BCCode: C2      0x000000C2  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/BAD-POOL-CALLER-0x000000C2-*1195.html?order=date

    BCCode: 1a      0x0000001a  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/MEMORY-MANAGEMENT-0x0000001A-*1041.html?order=votes

    BCCode: 7F      0x0000007F  which is the same as 0x1000007F  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/Run-a-system-diagnostic-utility-supplied-by-your-0x1000007F-*1304.html

    BCCode: F4      0x000000F4  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/A-process-or-thread-crucial-to-system-operation-has-0x000000F4-*1241.html

    BCCode: 50      0x00000050  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/PAGE-FAULT-IN-NONPAGED-AREA-0x00000050-*1095.html?order=votes

    BCCode: 24      0x00000024  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/NTFS-FILE-SYSTEM-0x00000024-*1051.html?order=votes

    BCCode: 74      0x00000074  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/BAD-SYSTEM-CONFIG-INFO-0x00000074-*1131.html?order=votes

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
    • Edited by SpiritX MS MVPMVP Monday, March 14, 2011 6:16 AM
    • Marked as answer by Saad50 Wednesday, March 23, 2011 3:26 AM
    Monday, March 14, 2011 6:12 AM
  • Hi,

    Memory tests do not catch all errors such as mismatched memory (possible even for sticks
    that appear to be identical) and when faster memory is placed in system behind slower memory.
    So it is best to also swap sticks in and out to check for those even if all memory tests fail to show
    a problem.

    To test RAM check here - let it run 4+ hours or so.  <-- best method
    www.memtest.org

    For the Vista/Windows 7 Memory Diagnostic Tool

    Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click -
    RUN AS ADMIN follow the instructions

    Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic
    Tool
    http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

    How to Run the Memory Diagnostics Tool in Windows 7
    http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

    Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool
    http://www.howtogeek.com/howto/windows-vista/test-your-computers-memory-using-windows-vista-memory-diagnostic-tool/

    =================================================

    Driver Verifier can help find some BSOD issues :

    Using Driver Verifier to identify issues with Windows drivers for advanced users
    http://support.microsoft.com/kb/244617

    How To Troubleshoot Driver Problems in Windows Vista or 7.
    http://www.winvistaclub.com/t79.html

    Using Driver Verifier
    http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM

    Driver Verifier
    http://www.techsupportforum.com/2110308-post3.html

    Using Driver Verifier
    http://www.faultwire.com/solutions/using_driver_verifier.php

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM

    You can disable Driver Verifier
    http://support.microsoft.com/kb/244617

    Start - type in Search box -> verifier /reset      hit enter to disable

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

    References to Vista also apply to Windows 7.

    This is my generic how to for proper driver updates : (Check for BIOS and driver updates.)

    This utility makes it easy to see which versions are loaded :

    DriverView - Free - utility displays the list of all device drivers currently loaded on your system.
    For each driver in the list, additional useful information is displayed: load address of the driver,
    description, version, product name, company that created the driver, and more.
    http://www.nirsoft.net/utils/driverview.html

    For Drivers check System Maker as fallbacks and Device Maker's which are the most current.
    Control Panel - Device Manager - Display Adapter - write down the make and complete model
    of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate
    Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -
    Uninstall - REBOOT this will refresh the driver stack.

    Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party
    with their own software and drivers and any other major device drivers you have.

    Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device
    Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for
    BIOS, Chipset and software updates at System Maker's site while there.)

    Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after
    each installation.

    Always check in Device Manager - Drivers tab to be sure the version you are installing actually
    shows up. This is because some drivers rollback before the latest is installed (sound drivers
    particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as
    needed.

    Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check
    manually by model.

    Manually look at manufacturer's sites for drivers - and Device Maker's sites.
    http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

    Installing and updating drivers in Windows 7 (updating drivers manually using the methods above
    is preferred to ensure the latest drivers from System maker and Device makers are found)
    http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
    • Marked as answer by Saad50 Wednesday, March 23, 2011 3:26 AM
    Monday, March 14, 2011 6:14 AM
  • I have also done all the updates from the Microsoft update website and have run the HP updater as well.

    I have uploaded the dump file at http://cid-006587c9f98c8384.office.live.com/embedicon.aspx/Public%20Folder/Dump%20Files.zip

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    happening.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled

    EXCEPTION_CODE: (NTSTATUS) 0xc000001d:

    //
    // MessageId: STATUS_ILLEGAL_INSTRUCTION
    //
    // MessageText:
    //
    // {EXCEPTION}
    // Illegal Instruction
    // An attempt was made to execute an illegal instruction.
    //
    #define STATUS_ILLEGAL_INSTRUCTION       ((NTSTATUS)0xC000001D L)

    STACK_TEXT: 
    dxgkrnl!DxgkCddEnable+0x725

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgkrnl
        fffff88005895800 - dxgkrnl!DxgkCddEnable+724
        [ 74:54 ]
    1 error : !dxgkrnl (fffff88005895800)

    MODULE_NAME: memory_corruption

    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT



    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: 0000000000000007,

    1: kd> k
    Child-SP          RetAddr           Call Site
    fffff880`03b992d8 fffff800`02df260e nt!KeBugCheckEx
    fffff880`03b992e0 fffff800`02fee04d nt!ExDeferredFreePool+0x11eb
    fffff880`03b99390 fffff800`02f97a9b nt! ?? ::NNGAKEGL::`string'+0xc39d
    fffff880`03b993c0 fffff800`02fb6b84 nt!CmpParseKey+0x10eb
    fffff880`03b99690 fffff800`02fbbb4d nt!ObpLookupObjectName+0x585
    fffff880`03b99790 fffff800`02f9aabc nt!ObOpenObjectByName+0x1cd
    fffff880`03b99840 fffff800`02f9dcba nt!CmOpenKey+0x28a
    fffff880`03b99990 fffff800`02cbe993 nt!NtOpenKey +0x12
    fffff880`03b999d0 fffff800`02cbaf30 nt!KiSystemServiceCopyEnd+0x13
    fffff880`03b99b68 fffff800`02fe41ed nt!KiServiceLinkage
    fffff880`03b99b70 fffff800`02f788f9 nt!RtlpGetRegistryHandleAndPath+0x281
    fffff880`03b99e80 fffff880`059ad96f nt!RtlQueryRegistryValues+0xb9
    fffff880`03b9a1d0 00000000`0000006e SynTP +0x3f96f

        Image path: \SystemRoot\system32\DRIVERS\SynTP.sys
        Image name: SynTP.sys
        Timestamp:        Thu May 27 23:41:36 2010

    The synaptic driver wants to open a registry key and fails. so updaet the driver, please.

    Bug Check 0x1A: MEMORY_MANAGEMENT

    This indicates that a severe memory management error occurred.

    Child-SP          RetAddr           Call Site
    fffff880`02b9b238 fffff800`02d36e58 nt!KeBugCheckEx
    fffff880`02b9b240 fffff800`02ce3ca2 nt! ?? ::FNODOBFM::`string'+0x29f57
    fffff880`02b9b330 fffff800`02ce213b nt!MiDispatchFault+0x8c2
    fffff880`02b9b440 fffff800`02cc582e nt!MmAccessFault+0xd3b
    fffff880`02b9b5a0 fffff800`02ca77e7 nt!KiPageFault+0x16e
    fffff880`02b9b738 fffff800`02ca7872 nt!RtlImageNtHeaderEx+0x3f
    fffff880`02b9b740 fffff800`02ff9e1f nt!RtlImageNtHeader +0x1e
    fffff880`02b9b770 fffff800`02fe3b18 nt! ?? ::NNGAKEGL::`string'+0x142a4
    fffff880`02b9b850 fffff800`02fe38eb nt!PsCallImageNotifyRoutines+0xdc
    fffff880`02b9b8b0 fffff800`02fdf4e2 nt!MiMapViewOfImageSection+0x41f
    fffff880`02b9b9f0 fffff800`02fdf07f nt!MiMapViewOfSection +0x372
    fffff880`02b9bae0 fffff800`02cc6993 nt!NtMapViewOfSection+0x2be
    fffff880`02b9bbb0 00000000`77b8f93a nt!KiSystemServiceCopyEnd+0x13


    this crash happens because Windows fails to map the DLLs/Exe files from the HDD in to the RAM.

    Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

    This indicates that a kernel-mode program generated an exception which the error handler did not catch.

    fffff880`03ba1af0 fffff800`02faaa41 nt!ExFreePoolWithTag+0x43
    fffff880`03ba1ba0 fffff800`02f6b7bf nt! ?? ::NNGAKEGL::`string'+0x10341
    fffff880`03ba1bd0 fffff800`02f6a0f0 nt!CmpCleanUpKcbCacheWithLock+0x2b
    fffff880`03ba1c00 fffff800`02f6a2fb nt!CmpDereferenceKeyControlBlockWithLock+0x150
    fffff880`03ba1c30 fffff800`02f6a6c0 nt!CmpDereferenceKeyControlBlock+0x11f
    fffff880`03ba1c80 fffff800`02c86961 nt!CmpDelayDerefKCBWorker +0xe8
    fffff880`03ba1cb0 fffff800`02f1c7c6 nt!ExpWorkerThread+0x111
    fffff880`03ba1d40 fffff800`02c57c26 nt!PspSystemThreadStartup+0x5a
    fffff880`03ba1d80 00000000`00000000 nt!KxStartSystemThread+0x16

    this crash is again, related to registry operations.


    I think your HDD has issues. Please start the command prompt (cmd.exe) with admin rights [1] and run

    chkdsk C: /r /f

    and after a reboot run sfc [2]:

    sfc.exe /scannow

    Is it able to find and repair broken files (create the txt file shown under [2] and look if all files are restored)?

    Now look if you still have crashes. If you still see crashes, download memtest86+ [3], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [4][5] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If memtest86+ detects errors, test each module its own and replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [6], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    best regards
    André

    [1] http://windows.microsoft.com/en-US/windows7/How-do-I-run-an-application-once-with-a-full-administrator-access-token
    [2] http://support.microsoft.com/kb/929833
    [3] http://www.memtest.org/download/4.20/memtest86+-4.20.iso.zip
    [4] http://www.imgburn.com/index.php?act=download
    [5] http://forum.imgburn.com/index.php?showtopic=61
    [6] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    • Proposed as answer by Andre.Ziegler Monday, March 14, 2011 2:37 PM
    • Marked as answer by Saad50 Wednesday, March 23, 2011 3:25 AM
    Monday, March 14, 2011 2:37 PM
  • Hi,

     

    It was a RAM problem afterall. I ran the Windows 7 memory check and it said that it was a hardware problem.

     

    I took it to the supplier and then had a long email discussion which finally resulted in them giving me my money back because they couldn't replace the laptop.

     

    Thank you all for your help. I am really grateful for your time.

     

    S


    S
    Wednesday, March 23, 2011 3:27 AM

All replies

  • Hi,

    Results verifies by WinDBG, DumpCHK, and BlueScreenView.

    There were 8 different Bug_Checks in the 10 minidumps - 1A, 24, 50, 74, 7F, C2, F4, and 7E (3).

    One of the 7E was most telling in that CAUSE was MEMORY CORRUPTION and several of the others pointed to MEMORY. Of course there can be other causes.

    BugCheck 1000007E, {ffffffffc000001d, fffff88005895801, fffff88002bdf388, fffff88002bdebf0}Probably caused by : memory_corruption

    None of the other Bug_Checks really pointed specifically to CAUSE as they showed Windows components which means something else drove them into Fault.

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

    Remove ALL power and reseat all cards, memory, and cables (both ends when possible) -
    actually remove and replace - do not just snug. Remove the dust bunnies and clean the
    vents. Check that the fans work (before and after opening the case). If a laptop about all
    you can do is reseat the memory and clean the vents (still can try adding a small fan as a
    test).

    Have you added any hardware lately? Have you updated any driver just before these started?
    (Check Control Panel - Windows Updates to see if any drivers were updated there about the time
     this started) Main likely culprits are Video driver, other major drivers, memory, and
    antivirus/antispyware/security products could be at fault as well as drive issues.

    When you get to the driver and memory sections of the troubleshooter refer to the next message
    to update drivers and test memory and then refer back to the troubleshooter if needed.

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

    Use the methods such as SFC, CheckDisk, Driver Updates, and others in the troubleshooter referred
    to in this link as they will help solve or at least narrow down the issues. After those you can post
    the information from BlueScreenView and these other utilities so we can offer more specific
    advice. Of course checking with a real computer shop or System Maker's Support would be a good
    idea however I would try the possible solutions you can first.

    See this thread for information on using BlueScreenView, MyEventViewer, and other methods to
    troubleshoot BlueScreens - top 3 replies (+1 other).

    http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/c675b7b8-795f-474d-a1c4-6b77b3fcd990

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

    These are usually excellent sources for troubleshooting methods.

    BCCode: 7E      0x00000007E  which is also 0x1000007E <-- read this link
    http://www.faultwire.com/solutions-fatal_error/SYSTEM-THREAD-EXCEPTION-NOT-HANDLED-0x0000007E-*1141.html?order=votes

    BCCode: C2      0x000000C2  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/BAD-POOL-CALLER-0x000000C2-*1195.html?order=date

    BCCode: 1a      0x0000001a  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/MEMORY-MANAGEMENT-0x0000001A-*1041.html?order=votes

    BCCode: 7F      0x0000007F  which is the same as 0x1000007F  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/Run-a-system-diagnostic-utility-supplied-by-your-0x1000007F-*1304.html

    BCCode: F4      0x000000F4  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/A-process-or-thread-crucial-to-system-operation-has-0x000000F4-*1241.html

    BCCode: 50      0x00000050  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/PAGE-FAULT-IN-NONPAGED-AREA-0x00000050-*1095.html?order=votes

    BCCode: 24      0x00000024  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/NTFS-FILE-SYSTEM-0x00000024-*1051.html?order=votes

    BCCode: 74      0x00000074  <-- read this link
    http://www.faultwire.com/solutions-fatal_error/BAD-SYSTEM-CONFIG-INFO-0x00000074-*1131.html?order=votes

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
    • Edited by SpiritX MS MVPMVP Monday, March 14, 2011 6:16 AM
    • Marked as answer by Saad50 Wednesday, March 23, 2011 3:26 AM
    Monday, March 14, 2011 6:12 AM
  • Hi,

    Memory tests do not catch all errors such as mismatched memory (possible even for sticks
    that appear to be identical) and when faster memory is placed in system behind slower memory.
    So it is best to also swap sticks in and out to check for those even if all memory tests fail to show
    a problem.

    To test RAM check here - let it run 4+ hours or so.  <-- best method
    www.memtest.org

    For the Vista/Windows 7 Memory Diagnostic Tool

    Start - type in Search box ->  Memory - find Memory Diagnostics tool at top of list - Right Click -
    RUN AS ADMIN follow the instructions

    Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic
    Tool
    http://www.shivaranjan.com/2007/11/01/windows-vista-how-to-scan-test-your-ram-or-memory-with-windows-vista-memory-diagnostic-tool/

    How to Run the Memory Diagnostics Tool in Windows 7
    http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

    Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool
    http://www.howtogeek.com/howto/windows-vista/test-your-computers-memory-using-windows-vista-memory-diagnostic-tool/

    =================================================

    Driver Verifier can help find some BSOD issues :

    Using Driver Verifier to identify issues with Windows drivers for advanced users
    http://support.microsoft.com/kb/244617

    How To Troubleshoot Driver Problems in Windows Vista or 7.
    http://www.winvistaclub.com/t79.html

    Using Driver Verifier
    http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM

    Driver Verifier
    http://www.techsupportforum.com/2110308-post3.html

    Using Driver Verifier
    http://www.faultwire.com/solutions/using_driver_verifier.php

    How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM

    You can disable Driver Verifier
    http://support.microsoft.com/kb/244617

    Start - type in Search box -> verifier /reset      hit enter to disable

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

    References to Vista also apply to Windows 7.

    This is my generic how to for proper driver updates : (Check for BIOS and driver updates.)

    This utility makes it easy to see which versions are loaded :

    DriverView - Free - utility displays the list of all device drivers currently loaded on your system.
    For each driver in the list, additional useful information is displayed: load address of the driver,
    description, version, product name, company that created the driver, and more.
    http://www.nirsoft.net/utils/driverview.html

    For Drivers check System Maker as fallbacks and Device Maker's which are the most current.
    Control Panel - Device Manager - Display Adapter - write down the make and complete model
    of your video adapter - double click - Driver's tab - write down the version info. Now click UPdate
    Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click -
    Uninstall - REBOOT this will refresh the driver stack.

    Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party
    with their own software and drivers and any other major device drivers you have.

    Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device
    Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for
    BIOS, Chipset and software updates at System Maker's site while there.)

    Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after
    each installation.

    Always check in Device Manager - Drivers tab to be sure the version you are installing actually
    shows up. This is because some drivers rollback before the latest is installed (sound drivers
    particularly do this) so install a driver - reboot - check to be sure it is installed and repeat as
    needed.

    Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check
    manually by model.

    Manually look at manufacturer's sites for drivers - and Device Maker's sites.
    http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

    Installing and updating drivers in Windows 7 (updating drivers manually using the methods above
    is preferred to ensure the latest drivers from System maker and Device makers are found)
    http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

    Hope this helps.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
    • Marked as answer by Saad50 Wednesday, March 23, 2011 3:26 AM
    Monday, March 14, 2011 6:14 AM
  • I have also done all the updates from the Microsoft update website and have run the HP updater as well.

    I have uploaded the dump file at http://cid-006587c9f98c8384.office.live.com/embedicon.aspx/Public%20Folder/Dump%20Files.zip

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    happening.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled

    EXCEPTION_CODE: (NTSTATUS) 0xc000001d:

    //
    // MessageId: STATUS_ILLEGAL_INSTRUCTION
    //
    // MessageText:
    //
    // {EXCEPTION}
    // Illegal Instruction
    // An attempt was made to execute an illegal instruction.
    //
    #define STATUS_ILLEGAL_INSTRUCTION       ((NTSTATUS)0xC000001D L)

    STACK_TEXT: 
    dxgkrnl!DxgkCddEnable+0x725

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgkrnl
        fffff88005895800 - dxgkrnl!DxgkCddEnable+724
        [ 74:54 ]
    1 error : !dxgkrnl (fffff88005895800)

    MODULE_NAME: memory_corruption

    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT



    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: 0000000000000007,

    1: kd> k
    Child-SP          RetAddr           Call Site
    fffff880`03b992d8 fffff800`02df260e nt!KeBugCheckEx
    fffff880`03b992e0 fffff800`02fee04d nt!ExDeferredFreePool+0x11eb
    fffff880`03b99390 fffff800`02f97a9b nt! ?? ::NNGAKEGL::`string'+0xc39d
    fffff880`03b993c0 fffff800`02fb6b84 nt!CmpParseKey+0x10eb
    fffff880`03b99690 fffff800`02fbbb4d nt!ObpLookupObjectName+0x585
    fffff880`03b99790 fffff800`02f9aabc nt!ObOpenObjectByName+0x1cd
    fffff880`03b99840 fffff800`02f9dcba nt!CmOpenKey+0x28a
    fffff880`03b99990 fffff800`02cbe993 nt!NtOpenKey +0x12
    fffff880`03b999d0 fffff800`02cbaf30 nt!KiSystemServiceCopyEnd+0x13
    fffff880`03b99b68 fffff800`02fe41ed nt!KiServiceLinkage
    fffff880`03b99b70 fffff800`02f788f9 nt!RtlpGetRegistryHandleAndPath+0x281
    fffff880`03b99e80 fffff880`059ad96f nt!RtlQueryRegistryValues+0xb9
    fffff880`03b9a1d0 00000000`0000006e SynTP +0x3f96f

        Image path: \SystemRoot\system32\DRIVERS\SynTP.sys
        Image name: SynTP.sys
        Timestamp:        Thu May 27 23:41:36 2010

    The synaptic driver wants to open a registry key and fails. so updaet the driver, please.

    Bug Check 0x1A: MEMORY_MANAGEMENT

    This indicates that a severe memory management error occurred.

    Child-SP          RetAddr           Call Site
    fffff880`02b9b238 fffff800`02d36e58 nt!KeBugCheckEx
    fffff880`02b9b240 fffff800`02ce3ca2 nt! ?? ::FNODOBFM::`string'+0x29f57
    fffff880`02b9b330 fffff800`02ce213b nt!MiDispatchFault+0x8c2
    fffff880`02b9b440 fffff800`02cc582e nt!MmAccessFault+0xd3b
    fffff880`02b9b5a0 fffff800`02ca77e7 nt!KiPageFault+0x16e
    fffff880`02b9b738 fffff800`02ca7872 nt!RtlImageNtHeaderEx+0x3f
    fffff880`02b9b740 fffff800`02ff9e1f nt!RtlImageNtHeader +0x1e
    fffff880`02b9b770 fffff800`02fe3b18 nt! ?? ::NNGAKEGL::`string'+0x142a4
    fffff880`02b9b850 fffff800`02fe38eb nt!PsCallImageNotifyRoutines+0xdc
    fffff880`02b9b8b0 fffff800`02fdf4e2 nt!MiMapViewOfImageSection+0x41f
    fffff880`02b9b9f0 fffff800`02fdf07f nt!MiMapViewOfSection +0x372
    fffff880`02b9bae0 fffff800`02cc6993 nt!NtMapViewOfSection+0x2be
    fffff880`02b9bbb0 00000000`77b8f93a nt!KiSystemServiceCopyEnd+0x13


    this crash happens because Windows fails to map the DLLs/Exe files from the HDD in to the RAM.

    Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

    This indicates that a kernel-mode program generated an exception which the error handler did not catch.

    fffff880`03ba1af0 fffff800`02faaa41 nt!ExFreePoolWithTag+0x43
    fffff880`03ba1ba0 fffff800`02f6b7bf nt! ?? ::NNGAKEGL::`string'+0x10341
    fffff880`03ba1bd0 fffff800`02f6a0f0 nt!CmpCleanUpKcbCacheWithLock+0x2b
    fffff880`03ba1c00 fffff800`02f6a2fb nt!CmpDereferenceKeyControlBlockWithLock+0x150
    fffff880`03ba1c30 fffff800`02f6a6c0 nt!CmpDereferenceKeyControlBlock+0x11f
    fffff880`03ba1c80 fffff800`02c86961 nt!CmpDelayDerefKCBWorker +0xe8
    fffff880`03ba1cb0 fffff800`02f1c7c6 nt!ExpWorkerThread+0x111
    fffff880`03ba1d40 fffff800`02c57c26 nt!PspSystemThreadStartup+0x5a
    fffff880`03ba1d80 00000000`00000000 nt!KxStartSystemThread+0x16

    this crash is again, related to registry operations.


    I think your HDD has issues. Please start the command prompt (cmd.exe) with admin rights [1] and run

    chkdsk C: /r /f

    and after a reboot run sfc [2]:

    sfc.exe /scannow

    Is it able to find and repair broken files (create the txt file shown under [2] and look if all files are restored)?

    Now look if you still have crashes. If you still see crashes, download memtest86+ [3], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [4][5] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If memtest86+ detects errors, test each module its own and replace the faulty RAM.

    If the memtest tells no error, please download CPU-Z [6], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes.

    best regards
    André

    [1] http://windows.microsoft.com/en-US/windows7/How-do-I-run-an-application-once-with-a-full-administrator-access-token
    [2] http://support.microsoft.com/kb/929833
    [3] http://www.memtest.org/download/4.20/memtest86+-4.20.iso.zip
    [4] http://www.imgburn.com/index.php?act=download
    [5] http://forum.imgburn.com/index.php?showtopic=61
    [6] http://www.cpuid.com/softwares/cpu-z.html


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    • Proposed as answer by Andre.Ziegler Monday, March 14, 2011 2:37 PM
    • Marked as answer by Saad50 Wednesday, March 23, 2011 3:25 AM
    Monday, March 14, 2011 2:37 PM
  • Hi,

     

    It was a RAM problem afterall. I ran the Windows 7 memory check and it said that it was a hardware problem.

     

    I took it to the supplier and then had a long email discussion which finally resulted in them giving me my money back because they couldn't replace the laptop.

     

    Thank you all for your help. I am really grateful for your time.

     

    S


    S
    Wednesday, March 23, 2011 3:27 AM
  • It was a RAM problem afterall. I ran the Windows 7 memory check and it said that it was a hardware problem.

    Thanks for the Feedback.

    André


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    Wednesday, March 23, 2011 3:06 PM
  • Hi,

    Glad to have helped.


    Rob Brown - Microsoft MVP <- profile - Windows Expert - Consumer : Bicycle - Mark Twain said it right.
    Thursday, March 24, 2011 1:46 AM