Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD all the time, different codes


  • Please log in to reply

#1
interpolarity

interpolarity

    Member

  • Member
  • PipPipPip
  • 286 posts
Hi guys, it has been a while... probable because I've become more computer savvy and can fix most problems, but this one has been plaguing me for a while, and before doing a backup and reinstall of the system, I was hoping to be able to fix the problem.

I keep getting BSOD stop errors. Usually they are System Service Exception, but I also get Driver IQRL Less than or Equal to. The numbers are always different (no, I haven't written them down :-P)
The pattern I've noticed is that it usually occurs when watching videos, especially streaming online ones. But, I have gotten BSOD even when doing nothing or just normal browsing. It happened once when I was playing Civilizaton V.

Obviously, I assumed this was a video driver problem. I adjusted settings, I uninstalled and reinstalled, but nothing helped. I know my hardware can't be failing (or at least I really hope not) because my computer is only about 2 years old. If so, I still have warranty coverage. But, I don't want to start ripping parts out if it is just a software issue.

I also ran scans with Windows Defender and Microsoft Security Essentials, with all coming up clean.

I've attached an xml file from speccy with all my system specs. Hope that helps.

What should my next step be?

P.S. Just realized that I've been using this site for 5 years now! Doesn't feel that long, lol

Attached Files


Edited by interpolarity, 07 October 2011 - 07:32 AM.

  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Sorry about your issue and we will try to get to the bottom of it.
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads



Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go 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.

Thanks to Broni for the instructions and program
  • 0

#3
interpolarity

interpolarity

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 286 posts
Who Crashed
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 10/11/2011 9:18:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-17799-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F) 
Bugcheck code: 0x10E (0x16, 0xFFFFFA8005717DF0, 0x14000, 0x200)
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 which cannot be identified at this time. 


On Tue 10/11/2011 9:18:24 PM 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 (0x16, 0xFFFFFA8005717DF0, 0x14000, 0x200)
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 which cannot be identified at this time. 


On Sun 10/9/2011 5:49:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-16738-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) 
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x6AC2, 0x446700000684)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
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 10/8/2011 11:38:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100811-16676-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x954F8) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001254F8, 0xFFFFF880084ABD40, 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 which cannot be identified at this time. 


On Sat 10/8/2011 9:48:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100811-16785-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880073CDCB8, 0xFFFFF880073CD510, 0xFFFFF880012B11A2)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system. 
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 which cannot be identified at this time.

Blue Screen
==================================================
Dump File         : 101111-17799-01.dmp
Crash Time        : 10/11/2011 5:20:33 PM
Bug Check String  : 
Bug Check Code    : 0x0000010e
Parameter 1       : 00000000`00000016
Parameter 2       : fffffa80`05717df0
Parameter 3       : 00000000`00014000
Parameter 4       : 00000000`00000200
Caused By Driver  : watchdog.sys
Caused By Address : watchdog.sys+122f
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\101111-17799-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,320
==================================================

==================================================
Dump File         : 100911-16738-01.dmp
Crash Time        : 10/9/2011 1:52:54 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00005003
Parameter 2       : fffff700`01080000
Parameter 3       : 00000000`00006ac2
Parameter 4       : 00004467`00000684
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\100911-16738-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,320
==================================================

==================================================
Dump File         : 100811-16676-01.dmp
Crash Time        : 10/8/2011 7:39:11 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff960`001254f8
Parameter 3       : fffff880`084abd40
Parameter 4       : 00000000`00000000
Caused By Driver  : win32k.sys
Caused By Address : win32k.sys+954f8
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\100811-16676-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,320
==================================================

==================================================
Dump File         : 100811-16785-01.dmp
Crash Time        : 10/8/2011 5:49:58 PM
Bug Check String  : NTFS_FILE_SYSTEM
Bug Check Code    : 0x00000024
Parameter 1       : 00000000`001904fb
Parameter 2       : fffff880`073cdcb8
Parameter 3       : fffff880`073cd510
Parameter 4       : fffff880`012b11a2
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+a91a2
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7cc40
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\100811-16785-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 275,320
==================================================

Hope this brings results :)
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate [b/memtest86+-4.20.iso[/b] file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#5
interpolarity

interpolarity

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 286 posts
Ok, well the computer came with 2 ram modules, 2GB each with two slots empty. Do you want me to take one stick out and do the test? I don't understand what you mean by option A. I don't want to keep my comp with just 2GB of RAM. I don't mind doing the RAM test, but I hate opening my computer up :-P

Though, I haven't dusted it in a while...

I'll write back with results/progress
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

I don't mind doing the RAM test, but I hate opening my computer up :-P

Then just run the memtest86 program if you don't want to take out ram.



Though, I haven't dusted it in a while...


Dust is the number one factor of overheating and slowing down a system. I would suggest opening it and using a can of compressed air blow the system out. Pay close attention the the fans but DO NOT let them spin freely while blowing them out as this can damage the bearings.
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Are you still having problems with your issue?
It has been 24 days since your last response and I was wondering if the issue has been resolved?
If so can you explain how it was resolved so others may be able to fix it if they have the same issue.
If not please let us know and we can continue with helping you to resolve the issue.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP