Results 1 to 7 of 7

Thread: Determining cause of BSOD?

  1. #1
    Registered+
    Join Date
    Mar 2015
    Posts
    27
    Thanks
    13
    Thanked
    0 times in 0 posts
    • LesC's system
      • Motherboard:
      • EVGA X99 Micro 2
      • CPU:
      • i7-5930K
      • Memory:
      • 64GB Corsair Dominator Platinum 2666
      • Storage:
      • Samsung 951 M2 SSD + 2 WD Blue 2TB
      • Graphics card(s):
      • EVGA GTX980Ti SC
      • PSU:
      • Corsair RMi 750
      • Case:
      • Corsair Air 240
      • Operating System:
      • Windows 10 64 bit
      • Monitor(s):
      • 2 x Dell U2414H
      • Internet:
      • 70 Mbps

    Determining cause of BSOD?

    I have a pretty old PC which has been pretty reliable but I do intend to replace it soon. Whilst on Skype earlier today the monitor went blank & I got a blue screen error. Switched on PC again and it's been fine since.

    The only odd behaviour I'd noticed of late was with Firefox appearing slow at times - when loading a new page on a new tab, parts of the previous screen would show through. I tried the 'refresh firefox' option which appeared to help somewhat. I've also noticed (I think) that the fan's been working more than usual.

    So, is there any way after the event to work out waht the cause of the blue screen error might have been? Thanks

  2. #2
    Senior Member kalniel's Avatar
    Join Date
    Aug 2005
    Posts
    29,024
    Thanks
    1,478
    Thanked
    2,906 times in 2,355 posts
    • kalniel's system
      • Motherboard:
      • Gigabyte X58A UD3R rev 2
      • CPU:
      • Intel Xeon X5680
      • Memory:
      • 12gb DDR3 2000
      • Graphics card(s):
      • nVidia GTX 1060 6GB
      • PSU:
      • Seasonic 600W
      • Case:
      • Cooler Master HAF 912
      • Operating System:
      • Win 10 Pro x64
      • Monitor(s):
      • Dell U2311H
      • Internet:
      • O2 8mbps

    Re: Determining cause of BSOD?

    Event viewer will contain the same information as the blue screen, the error might give some clues.

    http://www.bleepingcomputer.com/foru...-event-viewer/

  3. #3
    Registered+
    Join Date
    Mar 2015
    Posts
    27
    Thanks
    13
    Thanked
    0 times in 0 posts
    • LesC's system
      • Motherboard:
      • EVGA X99 Micro 2
      • CPU:
      • i7-5930K
      • Memory:
      • 64GB Corsair Dominator Platinum 2666
      • Storage:
      • Samsung 951 M2 SSD + 2 WD Blue 2TB
      • Graphics card(s):
      • EVGA GTX980Ti SC
      • PSU:
      • Corsair RMi 750
      • Case:
      • Corsair Air 240
      • Operating System:
      • Windows 10 64 bit
      • Monitor(s):
      • 2 x Dell U2414H
      • Internet:
      • 70 Mbps

    Re: Determining cause of BSOD?

    Thanks Only thing I can see in Event Viewer under 'system' is this error:

    Log Name: System
    Source: EventLog
    Date: 23/04/2015 17:28:24
    Event ID: 6008
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: Les-PC
    Description:
    The previous system shutdown at 17:26:54 on ‎23/‎04/‎2015 was unexpected.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="EventLog" />
    <EventID Qualifiers="32768">6008</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-23T16:28:24.000000000Z" />
    <EventRecordID>260629</EventRecordID>
    <Channel>System</Channel>
    <Computer>Les-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>17:26:54</Data>
    <Data>‎23/‎04/‎2015</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>3306</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>DF0704000400170011001A0036001E01DF0704000400170010001A0036001E01600900003C000000010000006009 000000000000B00400000100000000000000</Binary>
    </EventData>
    </Event>

  4. #4
    Senior Member
    Join Date
    Dec 2013
    Location
    Cymru
    Posts
    309
    Thanks
    152
    Thanked
    47 times in 45 posts
    • satrow's system
      • Motherboard:
      • ASRock Z77E-ITX
      • CPU:
      • Ivy Xeon 1230 v2/Be Quiet Shadow Rock Topflow
      • Memory:
      • GSkill 2x8GB DDR3 2400Mhz
      • Storage:
      • 3x 256GB SSDs, 2x 1TB 2.5" HDDs.
      • Graphics card(s):
      • Asus blower GTX 1060 6GB
      • PSU:
      • Seasonic 360W Gold
      • Case:
      • BitFenix Prodigy/2x 120mm fans
      • Operating System:
      • W7x64 Pro
      • Monitor(s):
      • Dual (/triple) Dell U2412M 1900x1200
      • Internet:
      • TalkTalk FTTC ~14Mbps

    Re: Determining cause of BSOD?

    Try attaching a zipped MSInfo32 log, Start > Run > MSInfo32 > hit Enter. Wait a while for it to fully populate, say 5 minutes, Save As > msinfo32.nfo.

  5. #5
    Senior Member
    Join Date
    Feb 2008
    Posts
    883
    Thanks
    4
    Thanked
    143 times in 132 posts
    • smargh's system
      • Motherboard:
      • Gigabyte GA-EP45-UD3P
      • CPU:
      • Xeon E5450 with 775-to-771 Mod
      • Memory:
      • 16GB Crucial
      • Storage:
      • Intel X25-M G2 80GB/Adaptec 3405 4x 2TB Ultrastar RAID1 / 1x 6TB Hitachi He6 / Dying 2TB Samsung
      • Graphics card(s):
      • GTX 750 Ti
      • PSU:
      • Seasonic X-560
      • Case:
      • Lian-Li PC-A71
      • Operating System:
      • Windows 7 Ultimate 64bit
      • Monitor(s):
      • BenQ G2400WD
      • Internet:
      • Really Crap ADSL2 <3Mbit

  6. #6
    Registered+
    Join Date
    Mar 2015
    Posts
    27
    Thanks
    13
    Thanked
    0 times in 0 posts
    • LesC's system
      • Motherboard:
      • EVGA X99 Micro 2
      • CPU:
      • i7-5930K
      • Memory:
      • 64GB Corsair Dominator Platinum 2666
      • Storage:
      • Samsung 951 M2 SSD + 2 WD Blue 2TB
      • Graphics card(s):
      • EVGA GTX980Ti SC
      • PSU:
      • Corsair RMi 750
      • Case:
      • Corsair Air 240
      • Operating System:
      • Windows 10 64 bit
      • Monitor(s):
      • 2 x Dell U2414H
      • Internet:
      • 70 Mbps

    Re: Determining cause of BSOD?

    Thanks folks, will give those a go. Wht I have worked out is that the cuase of the fan working overtime was due the CPU runnning at up to 100% at times due to a process 'Adobe CEF Helper' which is part of the Creative Cloud app. I've now disabled it from launching at boot up & will just manually check for updates. I wonder if the combination of this running along with Skype was the cause of the BSOD overloading the system?

  7. #7
    Senior Member
    Join Date
    Dec 2013
    Location
    Cymru
    Posts
    309
    Thanks
    152
    Thanked
    47 times in 45 posts
    • satrow's system
      • Motherboard:
      • ASRock Z77E-ITX
      • CPU:
      • Ivy Xeon 1230 v2/Be Quiet Shadow Rock Topflow
      • Memory:
      • GSkill 2x8GB DDR3 2400Mhz
      • Storage:
      • 3x 256GB SSDs, 2x 1TB 2.5" HDDs.
      • Graphics card(s):
      • Asus blower GTX 1060 6GB
      • PSU:
      • Seasonic 360W Gold
      • Case:
      • BitFenix Prodigy/2x 120mm fans
      • Operating System:
      • W7x64 Pro
      • Monitor(s):
      • Dual (/triple) Dell U2412M 1900x1200
      • Internet:
      • TalkTalk FTTC ~14Mbps

    Re: Determining cause of BSOD?

    Yes, on "a pretty old machine", any runaway process would cause a User process (Skype) to choke, the CPU would slow down in steps, trying to keep cool whilst still keeping the PC as productive as possible.

    Good work figuring it out

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •