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 2057


  • Please log in to reply
10 replies to this topic

#1 tiredeyes69

tiredeyes69

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:11 AM

Posted 01 February 2011 - 03:25 AM

Hello All
I am, running win7, on a core 2 quad, with 4gb ram.
been working fine for 2 years with raptors installed.
changed to a corsair ssd 60gb and it runs fine for around 1 month, then without adding any new programms, I start getting BSOD.
I never see the bsod, as it happens early hours of morning.
can you help please?
what do I need to post?

EDIT: Deleted clutter data from post ~ Hamluis.

Edited by hamluis, 09 February 2011 - 10:58 AM.


BC AdBot (Login to Remove)

 


#2 tiredeyes69

tiredeyes69
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:11 AM

Posted 01 February 2011 - 05:26 AM

got a screen dump of the problem ntoskrnl.exe+70740
help
so far I have uninstalled avg
rebooted.
installed avast.
my avg has loads of errors, like it cant update and so forth...
fingers crossed.
did a full scan using several online virus scanners - no error.

Attached Files



#3 Zuhl3156

Zuhl3156

  • Members
  • 309 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bensalem, Pa.
  • Local time:05:11 AM

Posted 01 February 2011 - 06:08 AM

Have a look at this topic. http://www.faultwire.com/solutions-fatal_error/Modification-of-system-code-or-a-critical-data-0x00000109-*1262.html
Try to download memtest86, burn it to disk, and let it run. It will take several hours. http://www.memtest86.com/

#4 tiredeyes69

tiredeyes69
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:11 AM

Posted 01 February 2011 - 06:46 AM

Ok after a few hours of trying to install .net 4
and then version Install 64-bit Native x64 version 6.10.3.233 [15.1 MB]
I finally got windbg to install
and click on the blue anaylise this
I got this now


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


Loading Dump File [C:\Windows\Minidump\012811-13353-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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0285e000 PsLoadedModuleList = 0xfffff800`02a9be50
Debug session time: Fri Jan 28 11:07:06.614 2011 (GMT+0)
System Uptime: 1 days 1:33:48.705
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89dd024eb, 0, 890d7d384a612aae, 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: a3a039d89dd024eb, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 890d7d384a612aae, 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 fffff800028ce740

STACK_TEXT:
fffff880`033cb5d8 00000000`00000000 : 00000000`00000109 a3a039d8`9dd024eb 00000000`00000000 890d7d38`4a612aae : 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
---------

------------------------------------------------------------------------------------------------------
Can anyone help now ?
Much appriciated :)

#5 tiredeyes69

tiredeyes69
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:11 AM

Posted 01 February 2011 - 06:49 AM

and from today at 09:00 before I uninstalled AVG

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


Loading Dump File [C:\Windows\Minidump\020111-12963-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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02854000 PsLoadedModuleList = 0xfffff800`02a91e50
Debug session time: Tue Feb 1 09:23:27.645 2011 (GMT+0)
System Uptime: 0 days 0:39:59.331
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d895a6d528, 0, 815b2eb1967067f3, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

3: 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: a3a039d895a6d528, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 815b2eb1967067f3, 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 fffff800028c4740

STACK_TEXT:
fffff880`033af5d8 00000000`00000000 : 00000000`00000109 a3a039d8`95a6d528 00000000`00000000 815b2eb1`967067f3 : 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
---------

--------------------------------------------------------------------------------------------------------------
I have now got Avast antichrist virus on, lets see how i get on with that.

#6 tiredeyes69

tiredeyes69
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:09:11 AM

Posted 09 February 2011 - 08:53 AM

I used memtest 86 +
found 5360 errors in a 8 hour period
RMA Ram back to Crucial.
thanks dude :)

#7 Zuhl3156

Zuhl3156

  • Members
  • 309 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bensalem, Pa.
  • Local time:05:11 AM

Posted 09 February 2011 - 09:36 AM

Whenever you use BlueScreenViewer and get the 'Bug Check Code' (BCC) from a BSOD, FaultWire has some very useful information to help you. I refer to FaultWire's BCC table frequently when troubleshooting a problem. Just ignore any reference or suggestion to using a Registry Cleaner or PC Optimizing utility by them. Experience has shown these programs to be useless and potentially harmful to your operating system. It was good to hear from you. I'm glad that you've found the problem and hopefully everything will work fine for you for a very long time to come. Good luck and 'Happy Computing'.

#8 hamluis

hamluis

    Moderator


  • Moderator
  • 55,870 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:11 AM

Posted 09 February 2011 - 10:54 AM

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html.

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#9 Zuhl3156

Zuhl3156

  • Members
  • 309 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bensalem, Pa.
  • Local time:05:11 AM

Posted 09 February 2011 - 10:58 AM

But Louis, he's already replied that the problem was bad RAM and if you look further up the page he has already posted the 'Blue Screen Viewer' results.

#10 hamluis

hamluis

    Moderator


  • Moderator
  • 55,870 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:11 AM

Posted 09 February 2011 - 11:04 AM

Sorry, you are correct...I sometimes fail to read all the way down...and then, sometimes by brain just wanders off :).

Thanks :).

Louis

#11 Zuhl3156

Zuhl3156

  • Members
  • 309 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Bensalem, Pa.
  • Local time:05:11 AM

Posted 09 February 2011 - 11:14 AM

I have the same problem. As I get older, my brain seems to wander off more frequently and travels much farther than the previous expedition. "But don't worry", everyone tells me. "It only gets better from here"! There's a happy thought!!!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users