Reboot at random times - IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe

Page 2 of 7 FirstFirst 1234 ... LastLast

  1. jmom
    Posts : 38
    Windows 7 Home Premium 64bit
    Thread Starter
       New #11

    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!
      My Computer
    Quote Quote

  3. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       New #12

    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 Partition or Volume - Create New.
      My Computer
    Quote Quote

  4. jmom
    Posts : 38
    Windows 7 Home Premium 64bit
    Thread Starter
       New #13

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

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

  6. jmom
    Posts : 38
    Windows 7 Home Premium 64bit
    Thread Starter
       New #14

    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!
      My Computer
    Quote Quote

  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       New #15

    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.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus and SynTPEnh, the touchpad driver.
    5. Apply > OK
    6. 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: Speccy - Publish Snapshot of your System Specs .


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

  8. jmom
    Posts : 38
    Windows 7 Home Premium 64bit
    Thread Starter
       New #16

    Ok - will do! Thanks!
      My Computer
    Quote Quote

  10. jmom
    Posts : 38
    Windows 7 Home Premium 64bit
    Thread Starter
       New #17

    Event 41 Bugcheck 0, random


    Hi,

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

    Reboot at random times - IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe

    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!
      My Computer
    Quote Quote

  11. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       New #18

    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
      My Computer
    Quote Quote

  12. jmom
    Posts : 38
    Windows 7 Home Premium 64bit
    Thread Starter
       New #19

    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
      My Computer
    Quote Quote

  13. jmom
    Posts : 38
    Windows 7 Home Premium 64bit
    Thread Starter
       New #20

    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
      My Computer
    Quote Quote

 
Page 2 of 7 FirstFirst 1234 ... LastLast

  Related Discussions
Hello! I've been getting this BSOD for 2 days now and it's happening at seemingly random times, sometimes right after closing a game, sometimes while just browsing. The BSOD screen says IRQL_NOT_LESS_OR_EQUAL. The event viewer says "The computer has rebooted from a bugcheck. The bugcheck was:...
Hi, recently I have been getting the BSOD on and off for a while now. I assume it might be a hardware related I just don't know how to read the mini dump to figure out what it is. Any help on how to fix this is greatly appreciated. Here is my minidump (also as an attachment):
BSOD random, probably under heavy load situations. I dont know how to do. DM log collector file attached many thanks
Hello, For a few weeks now I have been getting BSOD's, sometimes three a day, sometimes none for a few days. I re-installed windows (my boyfriend did actually, he knows lots more about computers than I do), but they still keep coming now and then. That's why he told me to ask for some assistance...
Hey all. I just got finished with a new pc build and after installing my video card i've been receiving BSODs at random. I suspect driver issues, but I really wouldn't know for sure. I'm including all the information below. I'd reaaaaally appreciate some help, been tearing my hair out over this.
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 03:56.
Find Us