windows 7 has crashed a lot lately. Mem dump enclosed.

[TheTeZ]

alright, well the reinstall was running and i had just entered the time zone, my key, and that good stuff, selected that it chose that it will be on a home network, and durring that phase, it blue screened, and restarted, now its stuck on starting windows..... i think my next trouble shooting step is a shotgun, or a sledge hammer.

 

[TheTeZ]

I recommend downloading and installing the latest drivers for your motherboard. Search for your mobo here: ASUSTeK Computer Inc.-Support-

i had done that already, and it made no difference.... i may try a clean install next, nothing else works, and once again, i'd be surprised if that worked.

 

[Jonathan_King]

Just don't install any programs after the clean install without first consulting us.

 

[TheTeZ]

ouch, i feel like a baby... Generally i am the one fixing other peoples computers, and can often look at other peoples problems and fix them no problem, But my stuff never seems to work, or be as easy a fix as others... at least not to me,

But ok, i will give you my list of software as i will install it.... That is if i can get the computer booted up anyway.

Generally things i install are
Firefox
Chrome
Thunderbird Shredder (x64 edition)
MagicJack Software With the windows 7 update
Open office
My Zune Software x64
Foxit Reader
i was installing AVGfree but after doing research, i decided to just go with the Microsoft security essentials or w/e its called. Although AVG is on the free list of win7 compatible software, under the software forum on these boards.
bitpim
Gimp x64
Utorrent
Nero 7
Steam And its Games
WinRAR
MagicISO
may or may not install GaIM or Pidgeon
Smart Defrag
Skype
Eidos TV Software

and i am pretty sure thats close to it.... i wont remember till i need other software.

 

[Jonathan_King]

I recommend installing them slowly. Install your browsers, Open Office, Foxit Reader, and skype.

MagicISO and the other virtualization programs are higher risk programs.

If you must install an AV, install MSE.

Other than that, don't install anything else until you determine the BSODs have stopped.

 

[TheTeZ]

i was planning on doing some intensive testing before i went and installed everything anyway. magic iso would be one of the last things i installed. i wont install programs until i need them really.


but my desktop has been stuck on the network section of set up for the last hour and a half, if i restart it, it sits on the same screen, the computer isnt locked up... its just not working

 

[Jonathan_King]

What is the network section you are referring to? If you think it could be a problem with your network drivers, tell it not to go online to get the latest updates.

 

[TheTeZ]

i dont think thats the problem, i honestly dont know why it hung there. when installing windows it gets to the set up, first asks you for the key, than the time zone, than the network you are a part of, i clicked home, and it stayed there.... i restarted the computer and unplugged the Ethernet cable, so it skipped that part, it booted, i plugged the cable in, and it booted up, and i already received a BSOD so here is the mini dump, maybe this will be informative, this is my last shot before a format, and reinstall.


View attachment 69779 I appreciate the help and suggestions so far.
Thanks to all.

 

[TheTeZ]

well that stinks,... but is nice at the same time..... I have 4 gigs of ocz platnum memory, and i have 4 gigs of corsair, (4 x 2gig sticks) all decent quality memory.

when i ran my memory tests (memtestx86) i ran about 3 hours worth on all 8 gigs, found errors, so i broke them down i scanned each stick, for way more than 5 passes, some were over night, some were while i was out for what ever reasons, they ran i found errors on one stick, removed it, kept running the tests, no more errors. so i just went through all this junk weve been talking about and more trying to isolate this problem. like i said i reinstalled, and had no luck, i had formatted and started to do a clean install on the new hard drive, guess what... lock up! i thought about it, my errors were all over, from a quick glance at each blue screen, i was getting errors of many different types from many different sources. i figured lets try going down to 1 stick, Which is often recommended, (but i didnt think would matter since all my memory (currently installed) came out clean. i popped out the 3 sticks, popped one back in, and its running real smooth!
after i get it installed i am going to go ahead and run more memtestx86 memory test on my sticks find out which ones are bad, and hopefully RMA them... hopefully its still possible....

 

[Jonathan_King]

Just remember that any time Memtest reports errors, it could be the RAM, and it could be a bad slot on the motherboard.

If you find a stick with no errors, try testing it in all the slots.

 

[TheTeZ]

AAh... good call. Thanks for that, if i find something wrong on the board i know its still warrantied by asus

Thanks, i didnt even think of that.

 

[TheTeZ]

****************'n ********* *******!!!

did a clean install, so far i have installed,

My Mail Client (thunderbird, but havent used it)
Google Chrome
Microsoft Security Essentials.
And My Graphics Driver
Steam


Guess What.... CRASH!!
View attachment 69917

i would really like to know what caused it this time, so i can get rid of what ever did and chuck it out the window, i assume its hardware....

 

[TheTeZ]

View attachment 69919

 

[TheTeZ]

if you tell me the last 2 were the harddrive caused errors again, i will be happy.

a couple days ago, i ran a chckdsk, it came out fine, no errors or anything. After my reformat/reinstall i decided to run a chkdsk again because this time windows told me a device or device driver caused the error but could no isolate the device/driver.

i figured you guys were telling me its a hard drive related error,, so lets run it, when the computer rebooted, it started deleting and replacing all kinds of files, no bad sectors, but plenty of stuff was going on. hopefully this was the problem with my bsod's but we shall see... please check out those dmp files and hopefully the problem is solved.

 

[Jonathan_King]

I suggest a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\042810-22323-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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0284d000 PsLoadedModuleList = 0xfffff800`02a8ae50
Debug session time: Wed Apr 28 10:03:54.373 2010 (GMT-4)
System Uptime: 0 days 0:06:13.057
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d897144670, 0, f578c1f9e87575ac, 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: a3a039d897144670, Reserved
Arg2: 0000000000000000, Reserved
Arg3: f578c1f9e87575ac, 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 fffff800028bd600

STACK_TEXT:  
fffff880`031bd5d8 00000000`00000000 : 00000000`00000109 a3a039d8`97144670 00000000`00000000 f578c1f9`e87575ac : 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
---------

 

[TheTeZ]

just crashed again,

Last night i ran a memtest with my 3 sticks in for 6 passes, no errors..... I know one of my ocz sticks had errors, but the one in it did not come up with any errors, i have run a pass on each of the 3 remaining sticks for a minimum of 5 passes each, than the 3 in the machine, no errors, That was using memtestx86

 

[TheTeZ]

well i believe the problem is the memory, but not that their is anything wrong with it, i think its a difference in brand problem, i took out my remaining ocz stick, and its been working, no blue screens yet, i just played some games and junk tried causing problems, nothing yet, so hopefully thats fixed it, only problem is i will have 4 gigs of ocz platinum memory .... unused....
figured it'd be fine all the numbers were the same, but as we all know that doesnt always matter.

 

[Jonathan_King]

Some motherboard are picky that way. I had trouble adding 2GB of RAM to my machine, same brand, numbers and all. I eventually got it sorted out by changing a compatibility setting.

 

[TheTeZ]

i am RMAing the ocz, since its got a lifetime warranty, and one of the stick's was found to have errors. after that, maybe i can research how to get it to work, or see if i can sell my memory to a friend, so i can pick up the same stuff thats in my machine now... and hope that works...

 

[TheTeZ]

WRONG!! im still having problems, same problems... no idea what the problem is.... memory is not causing the issue, i am going to remove the hard drive i am currently using, and put the o.s. on the newest drive i have, what sucks is all my hardware is less than 4 months old...