BSOD irql_not... cause by ntoskrnl.exe and another cause by display driver

By ssseven
Feb 13, 2010
  1. i don't know what to say... i keep getting bsod for 2 months...

    it is randomly happen... 3 days, 5 days, or even 1 weeks.. the time when my computer getting bsod is completly random...

    is anything like wrong input the sound cabel to the motherboard could make my computer bsod?

    when i get the bsod again, i will post the minidump file
  2. ssseven

    ssseven TS Rookie Topic Starter

    the last time

    by the way the last time i get bsod...

    the minidump consist of three problem

    two of them is irql_not_less_or_equal cause by ntoskrnl.exe

    and the last is cause by the display driverr

    for the display driver, i already try download the latest driver but still get the BSOD
  3. Archean

    Archean TechSpot Paladin Posts: 5,681   +86

    Please download BlueScreenView from here it will open your minidump file(s); select all of them and click on save icon on the toolbar; it will ask for filename and save it in text format post that file here; or attach your minidump files from C:\WIndows\Minidump with your next post.
  4. ssseven

    ssseven TS Rookie Topic Starter

    attach file

    this is the attachment file.. please help

    Attached Files:

  5. Archean

    Archean TechSpot Paladin Posts: 5,681   +86

    It seems to be a driver issue to me. However, I need you to do this, so it can be determined what driver is causing the problem I need you to enable driver verifier.

    1) Windows Key + R
    2) Type in 'verifier' and hit enter
    3) Make sure 'Create Standard Setting' is selected and hit next
    4) Click on 'Select all drivers installed on this computer' and hit Finish
    5) Reboot

    There is a possibility that your computer will crash on reboot. If this occurs hit F8 when rebooting just before the windows logo screen and select the safe mode boot option. Follow the same steps above but on step 4 choose 'Select driver names from a list'; hit next; check the box next to any driver where the provider is not Microsoft; hit Finish; reboot.

    This will slow the performance of you computer a little while enabled but will hopefully catch the driver causing corruption. Next time you crash the blue screen will hopefully say something like "DRIVER_VERIFIER_DETECTED_VIOLATION". When this occurs please post your new minidump.
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...