Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Please help me with my BSOD


  • Please log in to reply

#1
Tubzzywubzzy

Tubzzywubzzy

    New Member

  • Member
  • Pip
  • 4 posts
Hello i keep getting BSOD' i will try to attach my zip folder as i have looked around at other applications of the same problem. I usualy get the BSOD when im playing a game or trying to update a program. This has been going on now for over a week and im not in a happy mood as i like to be left alone when i play game (lol). Please if anyone could help i would appreciate it :)

Attached Files


Edited by Tubzzywubzzy, 15 October 2011 - 08:58 PM.

  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello Tubzzywubzzy.... Welcome to
GeeksToGo, :)
:yes: :)

I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.
  • Please understand we are all volunteers and we are not here all the time.
  • Sometimes it may be a extended amount of time to get back to you. If it has been
    more then 3 days please shoot me a PM and I will try to get back to you quickly
    then.
  • Please do the following and supply the requested information as needed. If you
    don't understand my instructions please ask and I will try to explain them
    clearer for you.
  • Do not attempt any steps unless instructed or ask before to
    make sure they will not cause any further issues.
  • If you are receiving assistance in any other forum site please let us know as there may be conflicting advice given.


Before we can help you need to provide the following so I can start you in the right direction.
Laptop or Desktop?
  • If a name brand system then what brand, make and model is the system?
  • If custom built then what brand, make and model is the motherboard
  • Total memory installed
  • Total hard drive capacity and free space
  • What steps have you taken so far to resolve the issue


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



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
  • 0

#3
Tubzzywubzzy

Tubzzywubzzy

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Hello, ty for your reply.
I have A custom build.
My motherboard is a "ASrock 890GX Extreme3"
I have 4gig of ram.
I have 2 HDD installed, a 100gb which has 5.55gb free, and a 1tb which has 714gb free.
I have taken none but as i said, i have looked around at other sites to try and find a solution.
I will add the rest of the stuff as i have to head to school now.
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

100gb which has 5.55gb free

This I take is your main OS drive. You have less the 5% of the drive free which could be most of your issue.
To run correctly you should never let your main OS drive get below 10% or 10 gigs in your case.
When you get done with the above instructions please do the following ASAP

Download TFC by OldTimer to your desktop
  • Please double-click TFC.exe to run it. (Note: If you are running on Vista, right-click on the file and choose Run As Administrator).
  • It will close all programs when run, so make sure you have saved all your work before you begin.
  • Click the Start button to begin the process. Depending on how often you clean temp files, execution time should be anywhere from a few seconds to a minute or two. Let it run uninterrupted to completion.
  • Once it's finished it should reboot your machine. If it does not, please manually reboot the machine yourself to ensure a complete clean.



Background info courtesy of DonnaB Thank you


As for TFC, this is a tidbit of an article I found a while back by a MicroSoft MVP.

TFC (Temp File Cleaner) will clear out all temp folders for all user accounts (temp, IE temp, java, FF, Opera, Chrome, Safari), including Administrator, All Users, LocalService, NetworkService, and any other accounts in the user folder. It also cleans out the %systemroot%\temp folder and checks for .tmp files in the %systemdrive% root folder, %systemroot%, and the system32 folder (both 32bit and 64bit on 64bit OSs). It shows the amount removed for each location found (in bytes) and the total removed (in MB).

Before running, it will stop Explorer and all other running applications. When finished, if a reboot is required the user must reboot to finish clearing any in-use temp files.
-- TFC only cleans temp folders.
-- TFC will not clean URL history, prefetch, or cookies. Depending on how often someone cleans their temp folders, their system hardware, and how many accounts are present, it can take anywhere from a few seconds to a minute or more. TFC will completely clear all temp files where other temp file cleaners may fail.




Download Auslogics Defrag from the link in my signature below. Auslogics Defrag in my opinion is better because:

It does a more comprehensive job at Defragging
It will actually show you what it is doing
At the end of working it will show you how much speed you picked up
You can view a online log of the files that Auslogics defragged
Please do not run any other Auslogics programs other then this one as they may cause unwanted results.
http://auslogics.com...defrag/download
  • 0

#5
Tubzzywubzzy

Tubzzywubzzy

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
==================================================
Dump File : 101611-119059-01.dmp
Crash Time : 10/16/2011 9:31:33 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000001`ed061c4c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`036ab053
Caused By Driver : hal.dll
Caused By Address : hal.dll+1344e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101611-119059-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 284,536
==================================================

==================================================
Dump File : 101611-59623-01.dmp
Crash Time : 10/16/2011 9:19:07 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`039b3b7f
Parameter 3 : fffff880`0890b0c0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101611-59623-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291,504
==================================================

==================================================
Dump File : 101611-69685-01.dmp
Crash Time : 10/16/2011 8:39:52 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101611-69685-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 283,256
==================================================

==================================================
Dump File : 101511-107437-01.dmp
Crash Time : 10/15/2011 4:06:58 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : ffffffff`fffffff8
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`036b7682
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101511-107437-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 283,000
==================================================

==================================================
Dump File : 101511-54023-01.dmp
Crash Time : 10/15/2011 3:37:01 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`0000000a
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`036b9053
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101511-54023-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 282,848
==================================================

==================================================
Dump File : 101511-84958-01.dmp
Crash Time : 10/15/2011 1:42:31 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffffa7f`8d1dd7e8
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`03cf3742
Caused By Driver : usbehci.sys
Caused By Address : usbehci.sys+4742
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101511-84958-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 283,752
==================================================

==================================================
Dump File : 101511-127702-01.dmp
Crash Time : 10/15/2011 12:44:15 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff800`036fd56e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101511-127702-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 283,320
==================================================

==================================================
Dump File : 101411-43602-01.dmp
Crash Time : 10/14/2011 7:59:12 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000020
Parameter 2 : fffffa80`07abd650
Parameter 3 : fffffa80`07abdee0
Parameter 4 : 00000000`0489000c
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101411-43602-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 282,296
==================================================

==================================================
Dump File : 101411-45692-01.dmp
Crash Time : 10/14/2011 7:51:53 PM
Bug Check String : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code : 0x000000c4
Parameter 1 : 00000000`00000091
Parameter 2 : 00000000`00000000
Parameter 3 : fffffa80`03b9cb60
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101411-45692-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 270,776
==================================================

==================================================
Dump File : 101411-45645-01.dmp
Crash Time : 10/14/2011 7:35:08 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`00e6bb07
Parameter 3 : fffff880`0c1a6d00
Parameter 4 : 00000000`00000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+3b07
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101411-45645-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 283,368
==================================================

==================================================
Dump File : 101411-75254-01.dmp
Crash Time : 10/14/2011 7:32:02 PM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 00000000`00000006
Parameter 2 : fffffa80`03b7f9b0
Parameter 3 : 00000000`48786649
Parameter 4 : 00000000`00000000
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+2d1c1
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101411-75254-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 283,608
==================================================

==================================================
Dump File : 101411-114629-01.dmp
Crash Time : 10/14/2011 7:25:09 PM
Bug Check String : INTERRUPT_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000003d
Parameter 1 : fffff880`0ba84590
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`03679b86
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101411-114629-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 285,792
==================================================

==================================================
Dump File : 100911-44678-01.dmp
Crash Time : 10/9/2011 2:47:29 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffffff`ffffffd8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`06da59b2
Parameter 4 : 00000000`00000000
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+22434
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100911-44678-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 332,128
==================================================

==================================================
Dump File : 100911-49670-01.dmp
Crash Time : 10/9/2011 1:05:40 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`001a30a2
Parameter 3 : fffff880`059e70d0
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+c30a2
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100911-49670-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 287,288
==================================================

==================================================
Dump File : 100911-90152-01.dmp
Crash Time : 10/9/2011 12:17:53 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`02e7dfe5
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000054
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100911-90152-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291,440
==================================================

==================================================
Dump File : 100911-110214-01.dmp
Crash Time : 10/9/2011 10:04:16 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff880`0b667cf0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`0167251d
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+7051d
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100911-110214-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291,472
==================================================

==================================================
Dump File : 100911-130619-01.dmp
Crash Time : 10/9/2011 9:33:08 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`0010b331
Parameter 3 : fffff880`0bf6e940
Parameter 4 : 00000000`00000000
Caused By Driver : nwifi.sys
Caused By Address : nwifi.sys+681e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100911-130619-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291,432
==================================================

==================================================
Dump File : 100911-50216-01.dmp
Crash Time : 10/9/2011 9:02:10 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`06daba7d
Parameter 3 : fffff880`0cb11e80
Parameter 4 : 00000000`00000000
Caused By Driver : ks.sys
Caused By Address : ks.sys+2a7d
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100911-50216-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291,480
==================================================

==================================================
Dump File : 100911-51495-01.dmp
Crash Time : 10/9/2011 8:38:47 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`149d6cf7
Parameter 3 : fffff880`031fb6a8
Parameter 4 : fffff880`031faf10
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+1ded3
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : dxgmms1.sys+20cf7
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100911-51495-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 291,472
==================================================

==================================================
Dump File : 100811-49218-01.dmp
Crash Time : 10/8/2011 3:56:55 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`03177c41
Parameter 3 : fffff880`05bf4ce0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100811-49218-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 289,872
==================================================

==================================================
Dump File : 100711-53477-01.dmp
Crash Time : 10/7/2011 7:51:01 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`00001097
Parameter 3 : 00000000`00000000
Parameter 4 : fffff8a0`0ee0bcc0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100711-53477-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 270,776
==================================================

==================================================
Dump File : 100711-65270-01.dmp
Crash Time : 10/7/2011 7:27:15 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`0317dc41
Parameter 3 : fffff880`0b9dcbf0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100711-65270-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 284,344
==================================================

==================================================
Dump File : 100711-54303-01.dmp
Crash Time : 10/7/2011 7:18:18 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff880`0b733cc0
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+705c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16841 (win7_gdr.110622-1503)
Processor : x64
Crash Address : ntoskrnl.exe+705c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100711-54303-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 285,848
==================================================
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 10/16/2011 4:28:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101611-119059-01.dmp
This was probably caused by the following module: hal.dll (hal+0x1344E)
Bugcheck code: 0xA (0x1ED061C4C, 0x2, 0x1, 0xFFFFF800036AB053)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 10/16/2011 4:28:57 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x1ED061C4C, 0x2, 0x1, 0xFFFFF800036AB053)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.


On Sun 10/16/2011 4:17:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101611-59623-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800039B3B7F, 0xFFFFF8800890B0C0, 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 which cannot be identified at this time.


On Sun 10/16/2011 1:49:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101611-69685-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 10/15/2011 11:04:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-107437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFF8, 0x0, 0x0, 0xFFFFF800036B7682)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.


On Sat 10/15/2011 10:35:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-54023-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0xA, 0x2, 0x1, 0xFFFFF800036B9053)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time.


On Sat 10/15/2011 8:40:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-84958-01.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x4742)
Bugcheck code: 0xD1 (0xFFFFFA7F8D1DD7E8, 0x2, 0x1, 0xFFFFF88003CF3742)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport 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 which cannot be identified at this time.


On Sat 10/15/2011 7:41:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-127702-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800036FD56E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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/15/2011 2:57:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101411-43602-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007ABD650, 0xFFFFFA8007ABDEE0, 0x489000C)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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/15/2011 2:50:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101411-45692-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA8003B9CB60, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 which cannot be identified at this time.


On Sat 10/15/2011 2:33:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101411-45645-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x3B07)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000E6BB07, 0xFFFFF8800C1A6D00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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/15/2011 2:30:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101411-75254-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D1C1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA8003B7F9B0, 0x48786649, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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/15/2011 2:22:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101411-114629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3D (0xFFFFF8800BA84590, 0x0, 0x0, 0xFFFFF80003679B86)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 10/9/2011 8:58:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-44678-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD8, 0x0, 0xFFFFF88006DA59B2, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 which cannot be identified at this time.


On Sun 10/9/2011 8:04:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-49670-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC30A2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001A30A2, 0xFFFFF880059E70D0, 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.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\100911-84474-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

On your computer a total of 25 crash dumps have been found. Only 24 could be analyzed. Only 15 are included in this report.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Have you done the next set of instructions?
If so please do the following.

Go to Start then to Run
Type in compmgmt.msc and click Enter
On left side click on Disk Management
On right side you will see you hard drive.
Now I need you to take a screenshot and attach it to your next reply. Do the following to take a screenshot while the above is open and showing on your desktop.

To do a screenshot please have click on your Print Screen on your keyboard. It is normally the key above your number pad between the F12 key and the Scroll Lock key
Now go to Start and then to All Programs
Scroll to Accessories and then click on Paint
In the Empty White Area click and hold the CTRL key and then click the V
Go to the File option at the top and click on Save as
Save as file type JPEG and save it to your Desktop


Attach it to your next reply
  • 0

#7
Tubzzywubzzy

Tubzzywubzzy

    New Member

  • Topic Starter
  • Member
  • Pip
  • 4 posts
Here it is :)

Attached Thumbnails

  • bsod.jpg

  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK system is at 12% free space on the C drive now which is better but keep a eye on it.

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






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