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


  • Please log in to reply

#1
macross21

macross21

    New Member

  • Member
  • Pip
  • 7 posts
hey guys

I'd like to know why I keep getting this BSOD these past few days I've been on my computer.. it didnt happen to be for 2-3 months then it started popping up these past few days. is there a way to get rid of this BSOD?

tks in advance
macross21
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello macross21.... Welcome to
GeeksToGo, :thumbsup:
:ph34r: :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


  • Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
  • Double-click VEW.exe
  • Under 'Select log to query', select (as appropriate):
    • Application
    • System
  • Under 'Select type to list', select (as appropriate):
    • Error
    • Information
    • Warning
Then use the 'Date of events' or 'Number of events' as follows:

Either:
  • Click the radio button for 'Number of events'
    Type 3 in the 1 to 20 box (or any number from 1 to 20)
    Then click the Run button.
    Notepad will open with the output log.

  • Click the radio button for 'Date of events'
    In the From: boxes type today's date (presuming the crash happened today) 04 11 2012
    In the To: boxes type today's date (presuming the crash happened today) 04 11 2012
    Then click the Run button.
    Notepad will open with the output log.
Please post the Output log in your next reply


[*] Click the radio button for 'Date of events'
In the From: boxes type today's date (presuming the crash happened today) 07 06 2013
In the To: boxes type today's date (presuming the crash happened today) 07 06 2013
Then click the Run button.
Notepad will open with the output log.
[/list]Please post the Output log in your next reply
  • 0

#3
macross21

macross21

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
hey rshaffer61

Custom Build
Brand: Asus
Model: Crosshair Forumla AMD 990FX
Ram: 8gb
HDD: 500gb / 175gb

First I tried resetting my BIOS to see if it would clear the problem which didnt work. after that I used the action center " Check for solutions " thingy and found no solutions.... then I tried google to see if this was happen to others motherboard of my model and found its rather common for most computer of different brands... So now I'm getting more advance help since its out of my league.

Attached Files


  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
WOW :help:
Your errors are all over the place but we have to start someplace and this is one I found right away.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.


So lets investigate this first and see what we find. First drivers as the possible issue.

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

#5
macross21

macross21

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
hey rshaffer61

System Information (local)
--------------------------------------------------------------------------------

computer name: CLOUD-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom™ II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8548319232 total
VM: 2147352576, free: 1918058496




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 6/8/2013 8:26:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060713-18330-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646034)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646034)
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 Sat 6/8/2013 8:26:04 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: symimv.sys (SymIMv+0x38AB)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646034)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\symimv.sys
product: Symantec Security Drivers
company: Symantec Corporation
description: NDIS 6.0 Filter Driver for Windows Vista
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symimv.sys (NDIS 6.0 Filter Driver for Windows Vista, Symantec Corporation).
Google query: Symantec Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 6/7/2013 12:38:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060613-19281-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF880016634AD)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFF880016634AD)
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/6/2013 6:10:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060513-18049-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646034)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646034)
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/6/2013 12:09:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060513-15428-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001645E2F)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001645E2F)
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 Tue 6/4/2013 7:01:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060313-17893-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800167CFBF)
Bugcheck code: 0xD1 (0x16, 0x2, 0x0, 0xFFFFF8800167CFBF)
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 Tue 6/4/2013 6:43:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060313-16567-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646034)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646034)
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 Tue 6/4/2013 6:24:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060313-18564-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646034)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646034)
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 Mon 6/3/2013 5:49:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060213-25272-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001682FAA)
Bugcheck code: 0xD1 (0x16, 0x2, 0x0, 0xFFFFF88001682FAA)
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 Mon 6/3/2013 5:40:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060213-21091-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001645E2F)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001645E2F)
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 Sun 5/19/2013 10:39:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051913-22386-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001845E2F)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001845E2F)
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 Tue 3/26/2013 9:07:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032513-20498-01.dmp
This was probably caused by the following module: e1q62x64.sys (0xFFFFF88007423EA0)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88007423EA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® Gigabit Adapter NDIS 6.x 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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e1q62x64.sys (Intel® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 3/26/2013 8:24:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032513-18844-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001E63612)
Bugcheck code: 0xD1 (0x16, 0x2, 0x0, 0xFFFFF88001E63612)
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 Tue 3/26/2013 6:57:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032513-19141-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001C92780)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001C92780)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 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 Sun 3/17/2013 1:07:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031613-25537-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF88001D5F780)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001D5F780)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 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.
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK I think I see the issue. Try updating your Gigabit Adapter NDIS 6.x driver which would be your network adapter driver.
Try the motherboard manufacturer website for the newest driver. If nothing there don't worry we can use drivermax to locate the newest version.
  • 0

#7
macross21

macross21

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
ok I've DL the newest driver from the asus site for my model. version 16.4.68.0.

Edited by macross21, 08 June 2013 - 07:07 PM.

  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK is there anything particular that will trigger the issue to happen? If so try doing that and see if it happens now.
  • 0

#9
macross21

macross21

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
the update seem to have fix the problem as I'm able to play PS2 without the BSOD for about 15mins which without the update around the 15mins mark it'll pop up.
  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
That is great to hear but to be sure lets see how it runs for a day or two. How is the rest of the system running right now?
  • 0

#11
macross21

macross21

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
I tried to trigger the BSOD with the other games that cause it but nothing. hope this stay and hope it isn't a hotfix. but its still to early to tell.
  • 0

#12
macross21

macross21

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
hey rshaffer61 its been almost 3 full days sinces you gave me advice to fix the BSOD problem I've been having and I got great news since it pass the 2 day. I never had a BSOD while trying to trigger it for all of my game and certain sites. Mega Thanks for helping getting out of this spot.
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
That is great to hear and if you are good we will consider this resolved. If the issue returns then just post to this topic and I will get a notice for it. For now I am happy to say Congratulations macross21. :rockon: for a successful resolution for your issue.

I'm glad we could help and please let us know how everything works out for you.
If there is anything else we can do to help please feel free to ask. I appreciate that you allowed us to assist you with your issue and for your patience.
Thank you for choosing GeeksToGo for help. :thumbsup: :ph34r:
This issue now appears to be resolved.


If other members are reading this and have a similar problem please begin a New Topic and someone will assist you as soon as possible
  • 1






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