The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Updated my drivers - now bluescreen when starting 3dmark11

    Discussion in 'Gaming (Software and Graphics Cards)' started by Rambisco, Jun 23, 2012.

  1. Rambisco

    Rambisco Notebook Consultant

    Reputations:
    19
    Messages:
    262
    Likes Received:
    0
    Trophy Points:
    30
    I recently updated my drivers to the latest version (301.42) and when I start 3dmark11 I immediately get a bluescreen. I'm not sure what drivers I came from, but with the new ones, TF2 still works just the same as before (if not better), so it might be a 3dmark11 only issue. I just wanted to retest with new drivers and an overclock to up my wimpy P2215. Thanks in advance. :(
     
    Rambisco, Jun 23, 2012
    #1
  2. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    download who crashed in my signature below which will tell you what caused the bsod
     
    MrDJ, Jun 23, 2012
    #2
  3. Rambisco

    Rambisco Notebook Consultant

    Reputations:
    19
    Messages:
    262
    Likes Received:
    0
    Trophy Points:
    30
    I don't see "who crashed" in your signature.. :O

    edit:

    WoW worked awesome. (+21% boost with overclock :D)

    3dmark06 also crashed.
     
    Rambisco, Jun 23, 2012
    #3
  4. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    click on
    >>>--- Everything you need to Monitor Temperatures & More ---<<<
     
    MrDJ, Jun 23, 2012
    #4
  5. Rambisco

    Rambisco Notebook Consultant

    Reputations:
    19
    Messages:
    262
    Likes Received:
    0
    Trophy Points:
    30
    On Sat 6/23/2012 6:56:58 PM GMT your computer crashed
    crash dump file: C:\windows\Minidump\062312-40310-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA80092B39E0, 0xFFFFFA80092B3CC0, 0xFFFFF80003393510)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Sat 6/23/2012 6:56:58 PM GMT your computer crashed
    crash dump file: C:\windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA80092B39E0, 0xFFFFFA80092B3CC0, 0xFFFFF80003393510)
    Error: CRITICAL_OBJECT_TERMINATION
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    (If that helps at all) (And I dont know if thats the 3dmark11 or 3dmark06 crash, but its probably the same thing causing it anyway)
     
    Rambisco, Jun 23, 2012
    #5
  6. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    Error: CRITICAL_OBJECT_TERMINATION

    this is what caused the problem > ntkrnlmp.exe which has been talked about on here before.

    google is your friend (most of the time)
    enjoy the readup on it >> Google
     
    MrDJ, Jun 23, 2012
    #6