Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Question about BSOD


  • Please log in to reply
44 replies to this topic

#1 Larliand

Larliand

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 16 November 2013 - 07:28 PM

- System
    - Provider
      [ Name] Windows Error Reporting
    - EventID 1001
      [ Qualifiers] 0
      Level 4       Task 0       Keywords 0x80000000000000     - TimeCreated
      [ SystemTime] 2013-11-17T00:14:49.000000000Z
      EventRecordID 57803       Channel Application       Computer Sillus-PC       Security
- EventData
              0       MemDiagV1       Not available       0       4096       Manual       Immediate       Pass       Standard       0       0       600                       C:\Windows\System32\LogFiles\MemDiag\MemDiag.bin       C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_4096_b46ada34c21761896b27ce07bfc508d19cb251f_cab_06289877               0       421f0d40-4f1d-11e3-b108-00044b161e10       4

 

 

 

This is the log from the even viewer, although I ran the windows memory check and it says there's no problems in it. That made me doubt whether it's an faulty ram, I had this error before I changed my graphics card and now it's here again. Mostly when I play games

 



BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:16 PM

Posted 16 November 2013 - 07:45 PM

We need to know more about your BSODs...

Download BlueScreenView (in Zip file)

No installation required.

Unzip downloaded file and double click on BlueScreenView.exe file to run the program and When scanning is done, go to Edit > Select All.

Then go to File > Save Selected Items, and save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Compliments of Broni

#3 Larliand

Larliand
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 17 November 2013 - 07:10 AM

==================================================
Dump File         : 110413-18205-01.dmp
Crash Time        : 11/4/2013 4:56:53 PM
Bug Check String  : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code    : 0x000000ea
Parameter 1       : fffffa80`0619b8b0
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  :
Caused By Address :
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     :
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\110413-18205-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 11/4/2013 4:57:47 PM
==================================================

==================================================
Dump File         : 102213-21559-01.dmp
Crash Time        : 10/22/2013 11:03:04 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`0724f4e0
Parameter 2       : fffff880`04012e5c
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`0000000d
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+75c40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\102213-21559-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 304,848
Dump File Time    : 10/22/2013 11:04:40 AM
==================================================

==================================================
Dump File         : 101613-19983-01.dmp
Crash Time        : 10/15/2013 11:22:16 PM
Bug Check String  : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code    : 0x100000ea
Parameter 1       : fffffa80`06078b50
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+6f63
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+75c40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\101613-19983-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,264
Dump File Time    : 10/15/2013 11:23:21 PM
==================================================

==================================================
Dump File         : 101113-62088-01.dmp
Crash Time        : 10/11/2013 12:44:35 PM
Bug Check String  : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code    : 0x100000ea
Parameter 1       : fffffa80`0607fb50
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+6f63
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+75c40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\101113-62088-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,264
Dump File Time    : 10/11/2013 12:46:46 PM
==================================================

==================================================
Dump File         : 101113-19281-01.dmp
Crash Time        : 10/11/2013 10:16:00 AM
Bug Check String  : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code    : 0x100000ea
Parameter 1       : fffffa80`060d3b50
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+6f63
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+75c40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\101113-19281-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 274,264
Dump File Time    : 10/11/2013 10:17:32 AM
==================================================

==================================================
Dump File         : 082413-21824-01.dmp
Crash Time        : 8/24/2013 9:59:16 PM
Bug Check String  :
Bug Check Code    : 0x00000117
Parameter 1       : fffffa80`073fd4e0
Parameter 2       : fffff880`04a94410
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+1f8a0
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : watchdog.sys+a577
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\082413-21824-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 298,657
Dump File Time    : 8/24/2013 9:59:16 PM
==================================================

==================================================
Dump File         : 071013-18158-01.dmp
Crash Time        : 7/10/2013 6:30:40 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`079604e0
Parameter 2       : fffff880`04ac4410
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  :
Caused By Address :
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     :
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\071013-18158-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 7/10/2013 6:31:29 PM
==================================================

==================================================
Dump File         : 032413-21621-01.dmp
Crash Time        : 3/24/2013 12:14:29 AM
Bug Check String  :
Bug Check Code    : 0x00000117
Parameter 1       : fffffa80`08302010
Parameter 2       : fffff880`04a6a410
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : discache.sys
Caused By Address : discache.sys+174ca00
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : watchdog.sys+a577
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\032413-21621-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 296,367
Dump File Time    : 3/24/2013 12:14:29 AM
==================================================

==================================================
Dump File         : 030413-18517-01.dmp
Crash Time        : 3/4/2013 2:59:10 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`041cf4e0
Parameter 2       : fffff880`04823410
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+75c40
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\030413-18517-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 308,104
Dump File Time    : 3/4/2013 3:00:33 PM
==================================================

==================================================
Dump File         : 020613-16832-01.dmp
Crash Time        : 2/6/2013 8:06:27 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`0442c010
Parameter 2       : fffff880`04ad4db8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  :
Caused By Address :
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     :
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\020613-16832-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 2/6/2013 8:07:32 PM
==================================================

==================================================
Dump File         : 020213-33649-01.dmp
Crash Time        : 2/2/2013 8:57:16 PM
Bug Check String  :
Bug Check Code    : 0x00000117
Parameter 1       : fffffa80`056894e0
Parameter 2       : fffff880`04b63db8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+1f8a0
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : watchdog.sys+a577
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\020213-33649-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 414,733
Dump File Time    : 2/2/2013 8:57:16 PM
==================================================

==================================================
Dump File         : 012113-15787-01.dmp
Crash Time        : 1/21/2013 4:23:51 PM
Bug Check String  :
Bug Check Code    : 0x00000117
Parameter 1       : fffffa80`04e4f010
Parameter 2       : fffff880`04b64db8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : atikmpag.sys
Caused By Address : atikmpag.sys+8db8
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : watchdog.sys+a577
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\012113-15787-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 284,584
Dump File Time    : 1/21/2013 4:23:51 PM
==================================================

==================================================
Dump File         : 010213-19000-01.dmp
Crash Time        : 1/2/2013 1:14:55 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`045e84e0
Parameter 2       : fffff880`03e88db8
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010213-19000-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 306,096
Dump File Time    : 1/2/2013 1:16:30 PM
==================================================
 

There you go :)



#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:16 PM

Posted 17 November 2013 - 07:25 AM


How to Test your RAM



Guide Overview

The purpose of this guide is to teach you how to check whether your system's RAM (Ramdom Access Memory) is working properly. Bad RAM can lead to a whole host of problems, often which do not appear to have a single cause -- appearing as systemwide glitches, blue screens, and other system trouble. MemTest86+ provides a very good detection mechanism for failed RAM, and is about as good a test you get short of actually replacing the module itself.

Tools Needed
Please perform these steps from a separate, working, machine.Perform these steps on the problem machine.
  • Put your CD in the drive and configure your machine to boot to the CD. This is different on all machines, but it's usually by pressing F12 or F10 as your system boots, and selecting either "CDROM" or your cdrom drive. If you are unable to force a CDRom boot, reply with the make and model of your machine and I should be able to get you exact instructions.
  • If you've done it correctly, MemTest86+ will start to run automaticly, as shown below:
    memtestStart.png
  • If you want to be reasonably your RAM is OK, then allow MemTest to run until you see this message:
    memtestFinished.png

    On the other hand, if you want to be completely sure your RAM is OK, allow MemTest to run overnight. Memtest will run forever until power is pulled on the machine.
  • Check the MemTest screen for any reported errors. Errors will appear as RED warnings at the bottom of the screen, similar to the following screenshot:
    memtestFail.png
  • Hard-Reset the machine, removing the MemTest disk in the process.
If you didn't get an error screen, Congratulations! :)

Compliments of Billy O'Neal.

#5 Larliand

Larliand
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 17 November 2013 - 07:31 AM

Err, so does that suggest it's the ram? or what's the cause of the BSOD's?



#6 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:16 PM

Posted 17 November 2013 - 07:33 AM

There isnt a sure sign what is causing the BSOD to happen, so when this happens we have them run a memory test to rule out hardware issues.

#7 Larliand

Larliand
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 17 November 2013 - 07:55 AM

For how long do I need to run the memtest for?



#8 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:16 PM

Posted 17 November 2013 - 07:56 AM

at least for 4 to 7 passes

#9 Larliand

Larliand
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 17 November 2013 - 09:07 AM

Which means 4 to 7 hours correct? :D



#10 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:16 PM

Posted 17 November 2013 - 09:08 AM

Nope 4 to 7 passes which means I would let it run over night.

#11 Larliand

Larliand
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 18 November 2013 - 06:17 AM

http://postimg.org/image/wl78exrgx/
 

 

Ok so I left it overnight, but I don't think that I've done it correctly have I?



#12 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:16 PM

Posted 18 November 2013 - 06:14 PM

You let it go for 12 passes and no errors which is a good thing and indication.

I would try updating your system drivers such as your chipset and other drivers like video card.

#13 Larliand

Larliand
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 18 November 2013 - 06:38 PM

Didn't test like one of the rams? or is it all of them alltogether?



#14 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:16 PM

Posted 18 November 2013 - 06:39 PM

Did you test each RAM Slot and each RAM Stick Separately?

I would have ran a test with all RAM installed.

#15 Larliand

Larliand
  • Topic Starter

  • Members
  • 25 posts
  • OFFLINE
  •  
  • Local time:03:16 PM

Posted 18 November 2013 - 06:42 PM

nono, I just started it on the PC as it always is with all the ram sticks in.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users