Reboot at random times - IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe

jmom · May 19, 2015

Hi,

I have an HP G60-553NR Notebook computer running Windows 7 Home Edition 64 bit, purchased in 2007.

About 2 months ago, it started randomly rebooting. I thought it was a driver issue based on a brief analysis of the minidump files, but couldn't nail down which driver. So I figured it was time to do a full recovery to speed it up anyway. So after doing a Windows recovery (and having some issues), it is still randomly rebooting, even before performing any Windows Updates!. Since then I have performed some Windows updates as well and the rebooting is still occurring. Note it is fine in Safe Mode.

Note that I had to use the HP F11 recovery option (using Recovery partition) as I have no recovery disks. I have also performed memory and disk diagnostics with no issues found.

I collected the BSOD data as stated by the post and am uploading it here.

I'm attaching 2 zip files as one collected more files and I'm not sure which is more useful (the earlier zip has more files).

Please let me know what this might be. My next step is to order Recovery disks, or try to install Windows 7 from some other place.

Thanks!

Arc · May 20, 2015

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats including BSODs.

Code:

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17795.amd64fre.win7_gdr.150318-1623

Report us for any further BSOD after installing Service pack 1.

EDIT:

jmom said:
Hi,

I have an HP G60-553NR Notebook computer running Windows 7 Home Edition 64 bit, purchased in 2007.

Windows 7 released on July 22, 2009. Are you sure about the year, 2007?
___________________________________________________

Code:

BugCheck A, {105bfdf18, 2, 1, fffff80002f62177}

*** WARNING: Unable to verify timestamp for ACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
Probably caused by : pci.sys ( pci!PciDispatchPnpPower+146 )

Followup: MachineOwner
---------

jmom · Jun 1, 2015

Thanks for the reply and sorry for the delay!

I had installed Microsoft Security Essentials right away to ensure the computer was protected. I went ahead and installed SP1 and still the laptop continued to reboot.

I was able to get a hold of the Recovery disks and reinstalled from those over the weekend, but that did not help -- it still continues to reboot. Note I did not connect to the internet so should not be vulnerable to any malware/viruses/etc.

I also ran the memtest486 for 8+ passes with no errors. Note there was no rebooting during this time (many many hours).

I have set up the system to create minidump files but am not getting any. When I log in to Windows, it generally reboots within a minute so I really can't even do anything anymore, except in safe mode.

Given the laptop is back at the factory state, and is still rebooting, does this lead towards a hardware issue?

Or is it still possible it's still a software issue, possibly with the D:\Recovery\ drive?

Any advice would be most appreciated!

UPDATE - I just turned on the Device Verifier and it rebooted eventually. There was a minidump file. Debug info attached. Maybe this will help? Note I have not connected to the internet at all since reinstalling Windows 7 as I figure there must be some indication of why it keeps rebooting now. Updating did not help earlier.

Thanks!

Arc · Jun 2, 2015

Service Pack 1 is still not seen in the data.

Microsoft Security Essentials is not there, too.

This BSOD is caused by Norton.

Code:

BugCheck A, {0, 2, 0, fffff80002a9ca83}

*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
[COLOR=Red]Probably caused by : SRTSP64.SYS[/COLOR] ( SRTSP64+328c0 )

Followup: MachineOwner
---------

Norton of 2009.

Code:

    Image name: SRTSP64.SYS
    Timestamp:        Tue Jun 23 08:15:21 2009

Please let me know what is going on. Why I am seeing so much discrepancies between your statement and your data.

jmom · Jun 2, 2015

[It's all in the post above, but I understand it's kinda long!

]

Because after loading SP1, the reboots still were occurring. I was able to get the recovery disks, so reinstalled Windows from the disks since I thought it may be more reliable than the recovery partition. However the reboots are still occurring, and that's what the file is referring to.

I don't think I can even install SP1 due to the reboots happening right away.... I tried doing a Windows Update and it just reboots...

Thanks!

Arc · Jun 2, 2015

http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html ... do it.

If you can get a SP1 ISO, install that. Otherwise install without SP1 ISO, and install SP1 right after installation.

Dont install norton back.

See how it goes.

jmom · Jun 2, 2015

Thanks for the info.

I got an iso but have a question about installing Windows. I tried it but think I picked the wrong partition (I picked Partition 2) and it ended up not working (had 2 Windows 7 installed and the new one failed).

I've uploaded a screenshot of the partitions.

Partition 1:SYSTEM does not have enough free space. Does this have the old Windows 7?

I don't want to screw up the BIOS/etc. and make the laptop unusable so please tell me what I should do here.

Should I use Partition 1 but Format it first to make more free space, or ???

HELP!

Arc · Jun 3, 2015

Back up the data of Disk 0 partition 2 elsewhere, externally following http://www.sevenforums.com/tutorials/93347-copy-paste-windows-recovery-console.html.

Now select all the partitions one by one, hit delete to delete the partitions, make the entire disc free.

Now, use the "NEW" button to create your partitions. Allow 120 to 150 GBs for windows (system) and keep the rest for data.

Install windows on the newly created (120 or 150 GB) partitions. During installation, it may create one more partition there (100 MB), if it is prompted to do so, accept it.

jmom · Jun 3, 2015

Thanks.

One clarification - I already backed up all the data a few weeks ago before I did the initial attempt at recovery.

Is the backup of Disk 0 Partition 2 in order to save my personal data, or something related to Windows/drivers/etc.?

If it's for my personal data, I can just skip that as I've already done it, and it's all been wiped out by my multiple recovery attempts.

Thanks!

Arc · Jun 3, 2015

If the personal data is backed up, that is enough. No need to back up anything from windows.

jmom · Jun 3, 2015

Thanks!

So sorry for another follow-up question. Real quick.

Should I be creating 2 new partitions (hit New twice?), one for system and the other ends up being for data?

I just created the one for System and am installing now thinking the rest would automatically go towards data, but figured I can re-do it if you tell me I should have created a second for data.

Thanks!

Arc · Jun 3, 2015

jmom said:
Thanks!

So sorry for another follow-up question. Real quick.

Should I be creating 2 new partitions (hit New twice?), one for system and the other ends up being for data?

I just created the one for System and am installing now thinking the rest would automatically go towards data, but figured I can re-do it if you tell me I should have created a second for data.

Thanks!

If you have created one partition only, and continued with windows installation, the remaining of the disc will remain as unallocated space.

After completing the installation, you can format it to a partition. See the option one of http://www.sevenforums.com/tutorials/2674-partition-volume-create-new.html.

jmom · Jun 3, 2015

THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I will update back here after completing the installation. So far so good! Windows Update right now... no reboots so far anyway....

jmom · Jun 4, 2015

Ok, I have completed the installation. I did run into some issues with it going into the "repair" phase after saying it couldn't complete the startup successfully. Eventually it would start up. I've run Windows Update several times and it did reboot on its own a few times in the middle of all of this, and the reboot was not due to the Windows Update (e.g. right after entering my password, it immediately shut down).

No minidump files have been created for any of these reboots (I did set it up to collect the minidump).

Now, Windows Update is saying No important updates available, but there are some optional updates, some of which are drivers.

Should I select the driver updates? I could post the screenshot here if that would help.

Should I run the verifier again?

Should I just monitor it to see what happens? It's not my laptop (mother-in-law's) so I don't really have much to "do" on it -- I could use it for internet browsing I suppose.

Any other suggestions?

Thanks!

Arc · Jun 4, 2015

You may opt for the driver updates via windows update.

For now, Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus and SynTPEnh, the touchpad driver.
Apply > OK
Accept then restart.

And report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

If it BSODs again, upload the data following the Blue Screen of Death (BSOD) Posting Instructions .

jmom · Jun 4, 2015

Ok - will do! Thanks!

jmom · Jun 7, 2015

Event 41 Bugcheck 0, random

Hi,

I had posted a couple weeks ago about BSOD and received a lot of great help. Link below:

http://www.sevenforums.com/bsod-help-support/370403-reboot-random-times-irql_not_less_or_equal-ntoskrnl-exe.html

I re-installed Windows 7 (non-bloated) and addressed various issues to get Windows and driver updates.

I am still having reboots and now it appears as if the only sign I can see is the Event 41 in the Event Viewer. Since it's a new error/scenario, I'm starting a new thread.

There are no more minidump files being created although I have Verifier turned on (per instructions). The minidumps you see in the collected data are for a driver issue which I've resolved.

I have also updated most of the drivers from the HP website. I downloaded the new BIOS version but I did not install it as I don't want to screw anything up.

Could you please take a look at the attached data to see if it gives any indication of more details of the reboots?

Any suggestions?

I have already done:

- Re-installed Windows 7 (non-bloated)
- Run Verifier
- Run MemTest for 8+ passes with no errors
- Run Speccy and temps seem ok (I can post screenshot).
- Checked hard drive - no errors
- Running just Microsoft Security Essentials and Malware Bytes - no other AV programs are installed
- Updated most drivers from HP (just not BIOS)
- turned off all services except the ones recommended
- other misc suggestions from other posts

[UPDATE - sure enough, the laptop rebooted right after I posted this post and I've attached the new data.]

Thanks!

Arc · Jun 7, 2015

Its bad and annoying. You said you will reply back in your thread, but you did not do that, and started another thread.

It not only gives a bad impression but also a contravention to the basic guideline of the BSOD forum.

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

If you need to add new information like the dump files, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Please do not post anything other than Windows 7 Blue Screen Of Death problems in this section.

This time we are merging this post with your earlier thread, but if this attitude continues then you will not get a reply.

Anyway, for your issue, update the touchpad driver (Synaptics). The one that you have installed there is not compatible with windows 7. I wonder how you got it installed. Here is the easiest way to get the driver.
___________________________________________________________

Code:

BugCheck C4, {f6, d0, fffffa800755eb30, fffff88003d213b9}

*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by : SynTP.sys ( SynTP+123b9 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000d0, Handle value being referenced.
Arg3: fffffa800755eb30, Address of the current process.
Arg4: fffff88003d213b9, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  SynTPEnh.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002f1c4ec to fffff80002a89a40

STACK_TEXT:  
fffff880`028ed1b8 fffff800`02f1c4ec : 00000000`000000c4 00000000`000000f6 00000000`000000d0 fffffa80`0755eb30 : nt!KeBugCheckEx
fffff880`028ed1c0 fffff800`02f31aa4 : 00000000`000000d0 fffffa80`0755eb30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`028ed200 fffff800`02ce4950 : fffff800`02d7ecf0 fffff880`028ed430 fffffa80`03d03a00 00000000`20040000 : nt!VfCheckUserHandle+0x1b4
fffff880`028ed2e0 fffff800`02d629f5 : 00000000`00000000 fffffa80`10000000 fffffa80`03d03a40 fffff800`02d62900 : nt! ?? ::NNGAKEGL::`string'+0x1a10e
fffff880`028ed3b0 fffff800`02f31838 : 00000000`00000000 fffff800`02f2a6bb fffff880`03d5a7c0 fffff800`02f2937c : nt!ObReferenceObjectByHandle+0x25
fffff880`028ed400 fffff880`03d213b9 : fffff980`0cab2fc8 00000000`20040000 00000000`20040000 00000000`00000003 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`028ed450 fffff980`0cab2fc8 : 00000000`20040000 00000000`20040000 00000000`00000003 fffff980`0cab2fd0 : SynTP+0x123b9
fffff880`028ed458 00000000`20040000 : 00000000`20040000 00000000`00000003 fffff980`0cab2fd0 00000000`00000000 : 0xfffff980`0cab2fc8
fffff880`028ed460 00000000`20040000 : 00000000`00000003 fffff980`0cab2fd0 00000000`00000000 fffff880`028ed580 : 0x20040000
fffff880`028ed468 00000000`00000003 : fffff980`0cab2fd0 00000000`00000000 fffff880`028ed580 fffff880`03d39899 : 0x20040000
fffff880`028ed470 fffff980`0cab2fd0 : 00000000`00000000 fffff880`028ed580 fffff880`03d39899 fffff880`028ed580 : 0x3
fffff880`028ed478 00000000`00000000 : fffff880`028ed580 fffff880`03d39899 fffff880`028ed580 00000000`20040000 : 0xfffff980`0cab2fd0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SynTP+123b9
fffff880`03d213b9 b90b0004e0      mov     ecx,0E004000Bh

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  SynTP+123b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SynTP

IMAGE_NAME:  SynTP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47ec46b4

FAILURE_BUCKET_ID:  X64_0xc4_f6_SynTP+123b9

BUCKET_ID:  X64_0xc4_f6_SynTP+123b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc4_f6_syntp+123b9

FAILURE_ID_HASH:  {a1c75ec5-9c55-6a89-f49f-f12d7ae47561}

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000d0, Handle value being referenced.
Arg3: fffffa800755eb30, Address of the current process.
Arg4: fffff88003d213b9, Address inside the driver that is performing the incorrect reference.

Debugging Details:
------------------


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  SynTPEnh.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002f1c4ec to fffff80002a89a40

STACK_TEXT:  
fffff880`028ed1b8 fffff800`02f1c4ec : 00000000`000000c4 00000000`000000f6 00000000`000000d0 fffffa80`0755eb30 : nt!KeBugCheckEx
fffff880`028ed1c0 fffff800`02f31aa4 : 00000000`000000d0 fffffa80`0755eb30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`028ed200 fffff800`02ce4950 : fffff800`02d7ecf0 fffff880`028ed430 fffffa80`03d03a00 00000000`20040000 : nt!VfCheckUserHandle+0x1b4
fffff880`028ed2e0 fffff800`02d629f5 : 00000000`00000000 fffffa80`10000000 fffffa80`03d03a40 fffff800`02d62900 : nt! ?? ::NNGAKEGL::`string'+0x1a10e
fffff880`028ed3b0 fffff800`02f31838 : 00000000`00000000 fffff800`02f2a6bb fffff880`03d5a7c0 fffff800`02f2937c : nt!ObReferenceObjectByHandle+0x25
fffff880`028ed400 fffff880`03d213b9 : fffff980`0cab2fc8 00000000`20040000 00000000`20040000 00000000`00000003 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`028ed450 fffff980`0cab2fc8 : 00000000`20040000 00000000`20040000 00000000`00000003 fffff980`0cab2fd0 : SynTP+0x123b9
fffff880`028ed458 00000000`20040000 : 00000000`20040000 00000000`00000003 fffff980`0cab2fd0 00000000`00000000 : 0xfffff980`0cab2fc8
fffff880`028ed460 00000000`20040000 : 00000000`00000003 fffff980`0cab2fd0 00000000`00000000 fffff880`028ed580 : 0x20040000
fffff880`028ed468 00000000`00000003 : fffff980`0cab2fd0 00000000`00000000 fffff880`028ed580 fffff880`03d39899 : 0x20040000
fffff880`028ed470 fffff980`0cab2fd0 : 00000000`00000000 fffff880`028ed580 fffff880`03d39899 fffff880`028ed580 : 0x3
fffff880`028ed478 00000000`00000000 : fffff880`028ed580 fffff880`03d39899 fffff880`028ed580 00000000`20040000 : 0xfffff980`0cab2fd0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SynTP+123b9
fffff880`03d213b9 b90b0004e0      mov     ecx,0E004000Bh

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  SynTP+123b9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SynTP

IMAGE_NAME:  SynTP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47ec46b4

FAILURE_BUCKET_ID:  X64_0xc4_f6_SynTP+123b9

BUCKET_ID:  X64_0xc4_f6_SynTP+123b9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc4_f6_syntp+123b9

FAILURE_ID_HASH:  {a1c75ec5-9c55-6a89-f49f-f12d7ae47561}

Followup: MachineOwner
---------

1: kd> lmvm SynTP
start             end                 module name
fffff880`03d0f000 fffff880`03d65000   SynTP    T (no symbols)           
    Loaded symbol image file: SynTP.sys
    Image path: SynTP.sys
    Image name: SynTP.sys
    Timestamp:        Fri Mar 28 06:45:32 2008 (47EC46B4)
    CheckSum:         00058FCC
    ImageSize:        00056000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

jmom · Jun 7, 2015

So sorry -- to be honest, I thought your last post about posting if BSOD happens again was suggesting I should start a new thread if it happens. That really is the only reason I did that. I thought referring to the original thread would give the history, if needed.

Just a misunderstanding.....

I will check your post about the driver - I have tried so many things, I cannot recall the details of installing that driver.

Thanks

jmom · Jun 7, 2015

If I recall correctly, the driver error you're seeing may be related to the 4 minidumps, and I did fix that driver issue a couple days ago - the laptop wouldn't even start until I fixed it.

So I don't think that is related to the Event 41.

If it would help, I can clear out those minidumps so they don't cause confusion.

Also, I'm uploading a Speccy screenshot, and the only reason I didn't do that before is that the temps seemed to be ok, according to what I've read anyway. The laptop is not used for anything like gaming. Just browsing, email, etc.

Thanks

Reboot at random times - IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer