locked
WIndows 7 BSOD Within 30 Seconds - ntoskrnl.exe RRS feed

  • Question

  • I have been having some issues with booting my system in Windows 7 HP. I had originally thought the issue was related to the TDSS Rootkit as it prevented Windows from opening in any mode (normal, safe, safe with networking, safe with command prompt). None of the removal programs (Kaspersky, Malwarebytes, Sophos) picked up anything however.

    Following other suggestions on trying to remove the iaStor.sys problem, I had booted the system into recovery console and tried to repair this by entering Bootrec.exe /FixMbr and Bootrec.exe /FixBoot. After that, I am still unable to boot into Windows 7, but can boot into any of the safe modes. At least this allows me to see the minidump files.

    Looking at the Minidumps now, it relates to ntoskrnl.exe. Is there anyone that can look into the Minidumps and see what I can do in trying to fix this. Thanks :)

    http://cid-1e968e4cb72fe0fa.office.live.com/self.aspx/Dump%20Files/Dump%20Files.zip

    Wednesday, March 16, 2011 10:41 PM

Answers

  • 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.

    fffff880`02fd94f8 fffff800`03ac0ca9 nt!KeBugCheckEx
    fffff880`02fd9500 fffff800`03abf920 nt!KiBugCheckDispatch+0x69
    fffff880`02fd9640 fffff800`03aae02e nt!KiPageFault+0x260
    fffff880`02fd97d0 fffff880`05ba7f27 nt!ExDeleteResourceLite+0xce
    fffff880`02fd9830 00000000`00000000 SRTSPL64 +0x30f27

        Image name: SRTSPL64.SYS
        Timestamp:        Tue Jan 22 06:12:20 2008

    This driver belongs to Symantec Tools. So update Symantec please. Your version is from 2008.

    Best regards
    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
    • Proposed as answer by Andre.Ziegler Thursday, March 17, 2011 12:43 PM
    • Marked as answer by Leo Huang Thursday, March 24, 2011 9:35 AM
    Wednesday, March 16, 2011 10:46 PM
  • I have been having some issues with booting my system in Windows 7 HP. I had originally thought the issue was related to the TDSS Rootkit as it prevented Windows from opening in any mode (normal, safe, safe with networking, safe with command prompt). None of the removal programs (Kaspersky, Malwarebytes, Sophos) picked up anything however.

    Following other suggestions on trying to remove the iaStor.sys problem, I had booted the system into recovery console and tried to repair this by entering Bootrec.exe /FixMbr and Bootrec.exe /FixBoot. After that, I am still unable to boot into Windows 7, but can boot into any of the safe modes. At least this allows me to see the minidump files.

    Looking at the Minidumps now, it relates to ntoskrnl.exe. Is there anyone that can look into the Minidumps and see what I can do in trying to fix this. Thanks :)

    http://cid-1e968e4cb72fe0fa.office.live.com/self.aspx/Dump%20Files/Dump%20Files.zip


    Have you try repairing windows either by using win 7 CD or boot into advanced boot option and next choose repair your computer other than using cmd.

    If your's is a branded rig say like hp, you could alway use system recovery by hitting F11 (different rig migt be using different key though) during the time of POST (power on self test) to enable system recovery. You might need to hit a few time cos at time just by hitting once it might not work

    • Marked as answer by Leo Huang Thursday, March 24, 2011 9:35 AM
    Thursday, March 17, 2011 12:56 AM
    Answerer

All replies

  • 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.

    fffff880`02fd94f8 fffff800`03ac0ca9 nt!KeBugCheckEx
    fffff880`02fd9500 fffff800`03abf920 nt!KiBugCheckDispatch+0x69
    fffff880`02fd9640 fffff800`03aae02e nt!KiPageFault+0x260
    fffff880`02fd97d0 fffff880`05ba7f27 nt!ExDeleteResourceLite+0xce
    fffff880`02fd9830 00000000`00000000 SRTSPL64 +0x30f27

        Image name: SRTSPL64.SYS
        Timestamp:        Tue Jan 22 06:12:20 2008

    This driver belongs to Symantec Tools. So update Symantec please. Your version is from 2008.

    Best regards
    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
    • Proposed as answer by Andre.Ziegler Thursday, March 17, 2011 12:43 PM
    • Marked as answer by Leo Huang Thursday, March 24, 2011 9:35 AM
    Wednesday, March 16, 2011 10:46 PM
  • I have been having some issues with booting my system in Windows 7 HP. I had originally thought the issue was related to the TDSS Rootkit as it prevented Windows from opening in any mode (normal, safe, safe with networking, safe with command prompt). None of the removal programs (Kaspersky, Malwarebytes, Sophos) picked up anything however.

    Following other suggestions on trying to remove the iaStor.sys problem, I had booted the system into recovery console and tried to repair this by entering Bootrec.exe /FixMbr and Bootrec.exe /FixBoot. After that, I am still unable to boot into Windows 7, but can boot into any of the safe modes. At least this allows me to see the minidump files.

    Looking at the Minidumps now, it relates to ntoskrnl.exe. Is there anyone that can look into the Minidumps and see what I can do in trying to fix this. Thanks :)

    http://cid-1e968e4cb72fe0fa.office.live.com/self.aspx/Dump%20Files/Dump%20Files.zip


    Have you try repairing windows either by using win 7 CD or boot into advanced boot option and next choose repair your computer other than using cmd.

    If your's is a branded rig say like hp, you could alway use system recovery by hitting F11 (different rig migt be using different key though) during the time of POST (power on self test) to enable system recovery. You might need to hit a few time cos at time just by hitting once it might not work

    • Marked as answer by Leo Huang Thursday, March 24, 2011 9:35 AM
    Thursday, March 17, 2011 12:56 AM
    Answerer