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

Random BSOD's


  • Please log in to reply
7 replies to this topic

#1 sykosiOn

sykosiOn

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:20 PM

Posted 20 June 2014 - 01:08 AM

Been getting some blue screens that I can't seem to replicate with any consistency. I had a couple while loading/closing a game, while watching YouTube videos or just completely at random. I've run MemTest86 overnight and it showed 0 errors. Can't seem to figure out what's wrong and would appreciate any help. I have some dump files I will post along with the specs to my PC.
 

PC Specs:
Windows 7 Ultimate 64bit

Intel i7-4770k

Nvidia GeForce GTX 770

4 x 4gb Corsair DDR3

Samsung 840 Evo 120gb SSD

Z-87 G45 Gaming MSi Mobo

 

Logs from WhoCrashed:

On Thu 6/19/2014 9:26:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061914-4009-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800185359D)
Bugcheck code: 0xD1 (0xB8, 0x2, 0x0, 0xFFFFF8800185359D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 6/19/2014 8:03:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061914-4867-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD194E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001A194E, 0xFFFFF880079FB880, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 6/19/2014 7:37:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061914-4976-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A003052DB0, 0x6, 0x2835A)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 6/19/2014 1:28:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061814-4040-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CC6E7F, 0xFFFFF8800907EED0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.



On Tue 6/17/2014 9:28:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061714-4165-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x307AC)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800FDBC7AC, 0xFFFFF88002541648, 0xFFFFF88002540EA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 6/17/2014 6:59:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061714-4352-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00FC10180, 0x0, 0x686659)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 6/17/2014 6:59:50 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: watchdog.sys (watchdog!WdLogEvent5+0x11B)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00FC10180, 0x0, 0x686659)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


 

Conclusion

7 crash dumps have been found and analyzed. No offending third party drivers have been found.


Edited by sykosiOn, 20 June 2014 - 01:23 AM.


BC AdBot (Login to Remove)

 


#2 dicke

dicke

    Paraclete


  • Members
  • 2,196 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Charlotte, NC
  • Local time:11:20 PM

Posted 20 June 2014 - 07:52 AM

Welcome,

You might try running MEMTEST86 to see if ther is a problem with the RAM.

Keep us posted


Stay well and surf safe [stay protected]

Dick E


#3 sykosiOn

sykosiOn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:20 PM

Posted 20 June 2014 - 04:38 PM

It is stated in my original post that I ran MemTest86 overnight (7 hours) and it showed no errors.



#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,562 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:09:20 PM

Posted 20 June 2014 - 07:07 PM

Please download MiniToolBox  , save it to your desktop and run it.
 
Checkmark the following checkboxes:
  List last 10 Event Viewer log
  List Installed Programs
  List Users, Partitions and Memory size.
 
Click Go and paste the content into your next post.
 
Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link of the snapshot in your next post.
 
Louis
 



#5 Frozwire

Frozwire

  • Members
  • 80 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:10:20 PM

Posted 20 June 2014 - 10:26 PM

It is stated in my original post that I ran MemTest86 overnight (7 hours) and it showed no errors.

 

You might not have found problems with your RAM because it isn't defective. But I think it is something to do with your RAM settings in your BIOS. It seems to be that it needs to be properly configured and tuned to avoid those unwanted BSODs.


"Encryption...is a powerful defensive weapon for free people. It offers a technical guarantee of privacy, regardless of who is running the government... It's hard to think of a more powerful, less dangerous tool for liberty...” - Esther Dyson


#6 blueelvis

blueelvis

    Bleep Blop Bleep


  • Malware Response Team
  • 1,666 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:08:50 AM

Posted 22 June 2014 - 02:47 AM

Hi Johueshua,

 

Could you please goto this path "C:\Windows\Minidump", zip up the Dump files and upload them to a service such as One Drive or Dropbox so that they could be used for further analysis and helping you better and fast as well? ^_^


Member of the Bleeping Computer A.I.I. early response team!


In case I have been helping you and you haven't received a reply from me in 48 hours, please feel free to PM me. Anything else? Still feel free to PM me :)

Did you read this? http://omgdebugging.com/5-tips-for-getting-the-best-bang-for-the-buck-at-fast-food-joints/

#7 sykosiOn

sykosiOn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:08:20 PM

Posted 23 June 2014 - 03:10 AM

 

Hi Johueshua,

 

Could you please goto this path "C:\Windows\Minidump", zip up the Dump files and upload them to a service such as One Drive or Dropbox so that they could be used for further analysis and helping you better and fast as well? ^_^

 

Sure, here they are: https://www.dropbox.com/s/rdrmye1kcbduj50/dumps.zip
 

 

Please download MiniToolBox  , save it to your desktop and run it.
 
Checkmark the following checkboxes:
  List last 10 Event Viewer log
  List Installed Programs
  List Users, Partitions and Memory size.
 
Click Go and paste the content into your next post.
 
Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link of the snapshot in your next post.
 
Louis
 

Here's a screenshot from Speccy: http://i.imgur.com/BxnYfEL.jpg

I tried running MiniToolBox and it gave me an error saying that it wasn't a valid Win32 application.


Edited by sykosiOn, 23 June 2014 - 06:02 AM.


#8 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,239 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:01:20 PM

Posted 23 June 2014 - 05:50 AM

Please re-install your video drivers, let us know if the problem persists.

 

TsVk!

 

edit: perform the clean/clear (I can't remember what it's called, but where it removes everything before installing the drivers) install option under advanced install on the nVidia installer.


Edited by TsVk!, 23 June 2014 - 05:53 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users