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.

    Re : Just normally browsing website & Bluescreen.

    Discussion in 'Alienware 18 and M18x' started by iPhantomhives, Nov 20, 2011.

  1. iPhantomhives

    iPhantomhives Click the image to change your avatar.

    Reputations:
    791
    Messages:
    1,665
    Likes Received:
    48
    Trophy Points:
    66
    roblem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 4105

    Additional information about the problem:
    BCCode: d1
    BCP1: 000002D800000928
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF88001722386
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\WINDOWS\Minidump\112011-12698-01.dmp
    C:\Users\iPhantomhives\AppData\Local\Temp\WER-14352-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    Any idea what happened ?
     

    Attached Files:

    iPhantomhives, Nov 20, 2011
    #1
  2. Mr. Fox

    Mr. Fox BGA Filth-Hating Elitist®

    Reputations:
    37,255
    Messages:
    39,354
    Likes Received:
    70,777
    Trophy Points:
    931
    He bro. If you download and install WhoCrashed it will give you more actionable details on the reason for the BSOD. (It generally does anyway.) I used WhoCrash to analyze your dump file and below is what the report states.

    Sometimes the crash report information in dump files is enough to isolate the cause, but other times only enough to start the troubleshooting process pointed in the right direction. Have you checked Windows Event Viewer for more info yet? Look at the time stamp on the crash report and see if there are any warnings, errors or informational events that correspond with the same date/time of the stop error (BSOD). Sometimes you can find out a great deal regarding the reason for a BSOD by what was reported in Event Viewer only minutes or seconds immediately prior to the stop error.

    Have you made any recent (last 24 hours) changes to RAM, software or drivers?
     
    Mr. Fox, Nov 20, 2011
    #2