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

BSOD Help - Minidump included - First post


  • Please log in to reply
12 replies to this topic

#1 boosted

boosted

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:31 PM

Posted 12 May 2011 - 06:25 PM

Hello.. this is my first post on any computer help website. I have been having BSOD error crashes for the last month and need to stop them from recurring. I have followed the steps on the "How to receive help diagnosing Blue Screens and Windows crashes" thread, and this is the text that is generated from WinDbg.

Can someone please help me make some sense of it? I have no idea what I am looking at. Thank you

System:
ASUS M4A78-E
Phenom II X4 2.8ghz
6gb Patriot Viper DDR2 1066 (3x2gb)
BFG GeForce 9800 GTX+ OC
Windows 7 x64 Ultimate
Intel X25-V 40gb SSD with Windows install
Seagate 1TB HDD for files

--------------------------------------------------------------

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051211-11247-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50
Debug session time: Thu May 12 15:08:27.653 2011 (UTC - 4:00)
System Uptime: 1 days 18:55:21.105
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89a5738c8, 0, fad470d4ba6ea2ed, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89a5738c8, Reserved
Arg2: 0000000000000000, Reserved
Arg3: fad470d4ba6ea2ed, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification

Debugging Details:
------------------


BUGCHECK_STR: 0x109

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002acf740

STACK_TEXT:
fffff880`031a85d8 00000000`00000000 : 00000000`00000109 a3a039d8`9a5738c8 00000000`00000000 fad470d4`ba6ea2ed : nt!KeBugCheckEx


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: BAD_STACK

Followup: MachineOwner
---------

Edited by boosted, 12 May 2011 - 06:26 PM.


BC AdBot (Login to Remove)

 


#2 boosted

boosted
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:31 PM

Posted 12 May 2011 - 06:26 PM

If there is any other information I can provide please let me know, thanks for reading.

#3 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:31 PM

Posted 12 May 2011 - 06:37 PM

Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and 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.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#4 boosted

boosted
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:31 PM

Posted 12 May 2011 - 06:50 PM

==================================================
Dump File : 051211-11247-01.dmp
Crash Time : 5/12/2011 3:09:40 PM
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`9a5738c8
Parameter 2 : 00000000`00000000
Parameter 3 : fad470d4`ba6ea2ed
Parameter 4 : 00000000`00000101
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051211-11247-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,136
==================================================

==================================================
Dump File : 051011-12542-01.dmp
Crash Time : 5/10/2011 8:13:19 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+152ad8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051011-12542-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,144
==================================================

==================================================
Dump File : 050111-10545-01.dmp
Crash Time : 5/1/2011 9:55:46 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff87f`939a56d4
Parameter 2 : 00000000`00000001
Parameter 3 : fffff960`000c66d2
Parameter 4 : 00000000`00000005
Caused By Driver : hal.dll
Caused By Address : hal.dll+7b7f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\050111-10545-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,184
==================================================

==================================================
Dump File : 042611-12324-01.dmp
Crash Time : 4/26/2011 5:50:43 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`028c781a
Parameter 3 : fffff880`09522180
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\042611-12324-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,200
==================================================

==================================================
Dump File : 041711-14414-01.dmp
Crash Time : 4/17/2011 2:42:01 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`00109354
Parameter 3 : fffff880`08ffd1d0
Parameter 4 : 00000000`00000000
Caused By Driver : atapi.sys
Caused By Address : atapi.sys+26d4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\041711-14414-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,144
==================================================

==================================================
Dump File : 040311-9079-01.dmp
Crash Time : 4/3/2011 3:04:52 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70710
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\040311-9079-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,152
==================================================

==================================================
Dump File : 040211-10966-01.dmp
Crash Time : 4/2/2011 11:58:46 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`01404121
Parameter 3 : fffff880`0829c7f0
Parameter 4 : 00000000`00000000
Caused By Driver : NETIO.SYS
Caused By Address : NETIO.SYS+4121
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\040211-10966-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,200
==================================================

#5 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:31 PM

Posted 12 May 2011 - 07:02 PM

Since we have very various types of errors and a various system files are involved, my first suspect would be some kind of infection.
Please, create new topic in "Am I Infected?" forum.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#6 boosted

boosted
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:31 PM

Posted 12 May 2011 - 07:20 PM

I will create a thread in that forum, but the main error I was concerned with was today's 5/12/2011 error. Any help with that one? Thanks

#7 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:31 PM

Posted 12 May 2011 - 07:36 PM

You don't draw any conclusions from one error.
You have to look at all of them.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#8 boosted

boosted
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:31 PM

Posted 15 May 2011 - 02:05 PM

I followed the instructions given in the "Am I infected?" forum (see post here: http://www.bleepingcomputer.com/forums/topic397031.html ) and all the scans came back clean. Any other ideas? I have BSODed twice since my original post. Thanks

#9 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:31 PM

Posted 15 May 2011 - 02:06 PM

Can you post fresh BSV log?

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#10 boosted

boosted
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:31 PM

Posted 15 May 2011 - 02:06 PM

Here is the bluescreenview from the last two crashes:


==================================================
Dump File : 051511-10062-01.dmp
Crash Time : 5/15/2011 2:42:53 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+152ad8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051511-10062-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,128
==================================================

==================================================
Dump File : 051311-10966-01.dmp
Crash Time : 5/13/2011 2:06:04 AM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041201
Parameter 2 : fffff680`00052ee0
Parameter 3 : cb700000`0c89a805
Parameter 4 : fffffa80`071d3710
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16695 (win7_gdr.101026-1503)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051311-10966-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
Dump File Size : 292,152
==================================================

#11 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:31 PM

Posted 15 May 2011 - 02:08 PM

You may have some RAM issues...

A. If you have more than one RAM module installed, try starting/running 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)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....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 memtest86+-....iso 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.

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.

Edited by Broni, 15 May 2011 - 02:09 PM.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#12 boosted

boosted
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:10:31 PM

Posted 15 May 2011 - 02:13 PM

Thanks for the advice with memtest, but I bought all of the components for this computer used, so I did a thorough memtest after I bought the RAM to make sure it was good. The test came back with 0 errors every time. I have been running the same sticks in the same slots for almost 6 months now, and the crashes have only been occuring for about the last month. Any other ideas? Thanks again.

Here is a post I made on another website which may contain useful information:

http://www.sevenforums.com/crashes-debugging/162827-bsod-help-minidump-included-first-post.html

#13 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:31 PM

Posted 15 May 2011 - 02:14 PM

Yes. Computer parts go bad.

A. If you have more than one RAM module installed, try starting/running 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


My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users