locked
Blue screen in windows 7 RRS feed

  • Question

  • Hi

    Since ive installed windows 7 32bit on my pc i keep getting now and again the blue screen and i really dont understand any of i, this is what it is giving me 

    - < Event xmlns =" http://schemas.microsoft.com/win/2004/08/events/event ">
    - < System >
      < Provider Name =" Microsoft-Windows-Kernel-Power " Guid =" {331C3B3A-2005-44C2-AC5E-77220C37D6B4} " />
      < EventID > 41 </ EventID >
      < Version > 2 </ Version >
      < Level > 1 </ Level >
      < Task > 63 </ Task >
      < Opcode > 0 </ Opcode >
      < Keywords > 0x8000000000000002 </ Keywords >
      < TimeCreated SystemTime =" 2010-08-05T21:22:01.406250000Z " />
      < EventRecordID > 4387 </ EventRecordID >
      < Correlation />
      < Execution ProcessID =" 4 " ThreadID =" 8 " />
      < Channel > System </ Channel >
      < Computer > Jayne-PC </ Computer >
      < Security UserID =" S-1-5-18 " />
      </ System >
    - < EventData >
      < Data Name =" BugcheckCode "> 36 </ Data >
      < Data Name =" BugcheckParameter1 "> 0x1904fb </ Data >
      < Data Name =" BugcheckParameter2 "> 0x98c819bc </ Data >
      < Data Name =" BugcheckParameter3 "> 0x98c816ec </ Data >
      < Data Name =" BugcheckParameter4 "> 0x894aea5a </ Data >
      < Data Name =" SleepInProgress "> false </ Data >
      < Data Name =" PowerButtonTimestamp "> 0 </ Data >
      </ EventData >
      </ Event >

     

          if anyone has any idea's would love some help thanks

     

    Friday, August 6, 2010 2:39 PM

Answers

  • 36 = 0x24

    Bug Check 0x24: NTFS_FILE_SYSTEM

    Please upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Magon Liu Wednesday, August 18, 2010 2:25 AM
    Friday, August 6, 2010 3:43 PM
  • Hi,

    Can you provide the make and model of your computer? Make sure you have installed the latest driver that is claimed compatible with Windows 7.

    Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software, incompatible driver\faulty device or anti-virus services (buggy services).

    The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).

    To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. The dmp files located in the folder C:\Windows\Minidump. Please upload it here for further research.

    At this point, certain things you can try are to find out the root cause of the problem are given below.
     
    1.    If the issue occurs frequently, Have a look whether you can reproduce the problem in safe mode.
     
    Start your computer in safe mode
    http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode
     
    If behavior doesn’t persist in safe mode, it indicates that a third party program or service is preventing you from performing the action as supposed to.
     
    To validate or determine which service/startup item could be causing this, restart the computer and boot to desktop normally. Once done, perform clean boot.
     
    2.    Clean Boot prevents software conflicts by preventing the startup items and non Microsoft services from loading. This way you can safely follow the process of elimination to check which application is causing this behavior.
     
    Refer:
    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
    http://support.microsoft.com/kb/929135
    Note: Ensure that you put your computer back to normal startup mode after completing the troubleshooting steps. Steps are available in the article given above.

    Regards,


    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 Magon Liu Wednesday, August 18, 2010 2:26 AM
    Tuesday, August 10, 2010 8:25 AM

All replies

  • 36 = 0x24

    Bug Check 0x24: NTFS_FILE_SYSTEM

    Please upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Magon Liu Wednesday, August 18, 2010 2:25 AM
    Friday, August 6, 2010 3:43 PM
  • Hi,

    Can you provide the make and model of your computer? Make sure you have installed the latest driver that is claimed compatible with Windows 7.

    Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software, incompatible driver\faulty device or anti-virus services (buggy services).

    The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).

    To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. The dmp files located in the folder C:\Windows\Minidump. Please upload it here for further research.

    At this point, certain things you can try are to find out the root cause of the problem are given below.
     
    1.    If the issue occurs frequently, Have a look whether you can reproduce the problem in safe mode.
     
    Start your computer in safe mode
    http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode
     
    If behavior doesn’t persist in safe mode, it indicates that a third party program or service is preventing you from performing the action as supposed to.
     
    To validate or determine which service/startup item could be causing this, restart the computer and boot to desktop normally. Once done, perform clean boot.
     
    2.    Clean Boot prevents software conflicts by preventing the startup items and non Microsoft services from loading. This way you can safely follow the process of elimination to check which application is causing this behavior.
     
    Refer:
    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
    http://support.microsoft.com/kb/929135
    Note: Ensure that you put your computer back to normal startup mode after completing the troubleshooting steps. Steps are available in the article given above.

    Regards,


    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 Magon Liu Wednesday, August 18, 2010 2:26 AM
    Tuesday, August 10, 2010 8:25 AM