Random BSOD Crashes even after fresh install

#1
View attachment Nugi17_W7F_20-11-2012.zip
Hi BsOD Pros.. need help big time. Built this rig a year ago never had any problems. Specs are as follows:
asus m5a97
AMD Radeon HD 6570 1gb
AMD FX 6100 Six-Core processor 3.3ghz
8 GB RAM
sound blaster audigy se
Win 7
all specs and information from forum guidelines in zip.

Pretty much my step mom / lil bros computer. They play minecraft and silly flash games what not 10 year old stuff, and mom just does office work as a teacher. Theyve never told me of any blue screens till now that they started happening everytime the pc loaded windows 7 . I tried going into safe mode and that stopped the blue screens from happening. I tried to restore to earlier dates and that did not help. I ran disk defrag and malwarebytes but to no avail. So I finally did a fresh install of win 7 pro again and thought it fixed the problem but it randomly happened again as I was re in stalling drivers and restoring backed up documents. I got it connected here on my hdmi monitor at home because I couldnt solve the problem at their place the only difference is they are set up with 2 monitors vga/dvi setup as opposed to now I have only m hdmi led connected. Also I am not connected to the internet here since no ethernet cable to my room. They were using an ethernet cable in their office.

Have had the PC on for about an hour now here (got all requirements from it and all and no crashes yet). It's only crashed about 4-5 times after the fresh install of windows as opposed to everytime the computer loaded windows before the fresh install. It also feels much more stable, but i'm still really clueless as to what is causing this crash. Hope someone can analyze these diagnostics and further guide me to solving this problems. FEel free to ask me about anthing i left out.. Gotta help them get their pc back up they got projects and work to do ya know how it is.


edit: I wanted to add that I took out a years worth of dust after getting home with the rig and also noticed the gfx card was a little to the side so I adjusted it but it was in the slot completely just slanted on the port side. I'm also completed the restore of the documents I backed up and it did not crash. It did crash both times I tried to do this at their place. I don't know if the gfx card may have been the problem earlier or the dust but its too soon to speak. I feel like the computer will start acting up as soon as I plug it in at their place. Hope someone can let me know something off the dump files. Thx.
 


Last edited:

GeneralHiningII

Honorable Member
#2
Looks like you've only got 2 updates installed for SP1 - Go to Windows Update, and install all the new updates (usually there are about ~100 updates for SP1 [so far]).


You also seem to have one device without the proper drivers:
Multimedia Audio Controller The drivers for this device are not installed.

Looking at your drivers, you have Daemon Tools installed. Please uninstall it, as it has been known to cause frequent BSODs.
Driver Reference Table - dtsoftbus01.sys


You have AMD Overdrive installed, which is another known BSOD maker in Windows 7.
Driver Reference Table - AODDriver2.sys

Analysis:
Code:
Debug session time: Tue Nov 20 17:45:25.319 2012 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\111912-43118-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:02:40.129
BugCheck 1000007E, {c0000005, 875b5864, 8cfffa70, 8cfff650}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Bugcheck code 1000007E
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  [COLOR=#ff0000]MMLoadDrv.exe[/COLOR]
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  0x7E_CODE_ADDRESS_MISMATCH_BAD_IP_ANALYSIS_INCONCLUSIVE
BiosVersion = 0901
BiosReleaseDate = 11/24/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Nov 20 17:08:27.950 2012 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\111912-24554-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:03:01.137
BugCheck A, {40075, 2, 1, 82a8792b}
Probably caused by : ntkrpamp.exe ( nt!KiAttachProcess+58 )
Bugcheck code 0000000A
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xA_nt!KiAttachProcess+58
BiosVersion = 0901
BiosReleaseDate = 11/24/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Nov 20 17:04:50.193 2012 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\111912-51371-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:24:29.003
BugCheck 1000007E, {c0000005, 8685b864, 80791a70, 80791650}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Bugcheck code 1000007E
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  [COLOR=#ff0000]svchost.exe[/COLOR]
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  0x7E_CODE_ADDRESS_MISMATCH_BAD_IP_ANALYSIS_INCONCLUSIVE
BiosVersion = 0901
BiosReleaseDate = 11/24/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Nov 20 15:41:40.616 2012 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\111912-23977-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:16:16.442
BugCheck 1000007E, {c0000005, 828bfcbd, 8cdf3a4c, 8cdf3630}
Probably caused by : ntkrpamp.exe ( nt!RtlImageNtHeaderEx+4a )
Bugcheck code 1000007E
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  [COLOR=#ff0000]svchost.exe[/COLOR]
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  0x7E_nt!RtlImageNtHeaderEx+4a
BiosVersion = 0901
BiosReleaseDate = 11/24/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Nov 20 15:24:45.585 2012 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\111912-29905-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 0:03:02.755
BugCheck A, {41c18, 2, 1, 828ca92b}
Probably caused by : ntkrpamp.exe ( nt!KiAttachProcess+58 )
Bugcheck code 0000000A
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xA_nt!KiAttachProcess+58
BiosVersion = 0901
BiosReleaseDate = 11/24/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
2 of them point to svchost.exe:
svchost.exe is a generic host process name for services that run from dynamic-link libraries
in English, svchost.exe is a process that controls your services that are running.
How to fix this:
Go to the start menu, and type in "Run" (anything wrapped in quotations should be typed without quotations in the appropriate search bar).
In the run box, type in "msconfig".
In the General Tab, select "Selective Startup" and check the boxes: "Load System Services" and "Load startup items".
In the Startup tab, UNCHECK ALL BOXES.
Click "Apply", and restart your computer.
Try it and see what happens, then post back the results (if you do get another crash, just get the minidump).

MMLoadDrv.exe is from AMD Catalyst Control Center. I'm no expert in AMD cards/software, but I guess you can use these two links:
Driver Reference Table - atikmdag.sys
Driver Reference Table - atikmpag.sys
to install the newest AMD Drivers (? need confirmation on this, usasma?)
 


#3
hey thanks for the fast response. I know the audio adapter is the soundblaster I just havent gotten the driver for it yet currently just using on board. I did uninstall daemon tools because off some research i did earlier someone said to get rid of vmware. Thats weird that the driver still came up. I wil move my pc near my router and do some windows updates. will check back latero

oh and i cant find anthing on amd overdrive but hopefully win updates fixes the problems because i remebmer turning it off when I set up their pc last year so that they didnt get any popups (they call me about everything).
 


GeneralHiningII

Honorable Member
#4
Ok good, if you could post back the results when you're done that'd be very good.

If it does work for you though, just come back and say it worked, so people who view this thread after know it worked.

Good Luck!
 


#5
so I unplugged the pc and moved everything near the router to use a short ethernet cable. On the first boot with the ethernet cable connected now it crashed on the please wait screen before showing the desktop. it rebooted and it went through this time and now i got it installing windows updates here is the logs from the last crash View attachment 112012-20576-01.dmp View attachment 112012-21668-01.dmp

there was 2 new files i think one was from a bad shutdown when i moved the pc to the router area but the more recent one should be the bsod when windows was loading.
let me know if you get anything from this one, going to check the windows update n hope it didnt bsod again
 


GeneralHiningII

Honorable Member
#6
points to userinit.exe, which is just the initialization process. shouldn't be a problem, in my experience.
 


#7
points to userinit.exe, which is just the initialization process. shouldn't be a problem, in my experience.
well I just finished installing all the windows updates that it had and while I was running a few programs installing like firefox, avast, and connected my external hardrive, it bsod again.

this is the dump file hope we get something from this one

View attachment 112012-61027-01.dmp
 


GeneralHiningII

Honorable Member
#8
What I see in the minidumps:

Analysis:
Code:
[FONT=verdana]Debug session time: Tue Nov 20 21:42:02.715 2012 (UTC + 11:00)[/FONT]
[FONT=verdana]Loading Dump File [C:\Users\MZ\SysnativeBSODApps\112012-21668-01.dmp][/FONT]
[FONT=verdana]Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850[/FONT]
[FONT=verdana]System Uptime: 0 days 0:01:21.525[/FONT]
[FONT=verdana]BugCheck 1000008E, {c0000005, 82c75f3e, 80795764, 0}[/FONT]
[FONT=verdana]Probably caused by : ntkrpamp.exe ( nt!ExpAllocateHandleTableEntry+1f )[/FONT]
[FONT=verdana]Bugcheck code 1000008E[/FONT]
[FONT=verdana]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/FONT]
[FONT=verdana]BUGCHECK_STR:  0x8E[/FONT]
[FONT=verdana]PROCESS_NAME:  userinit.exe[/FONT]
[FONT=verdana]FAILURE_BUCKET_ID:  0x8E_nt!ExpAllocateHandleTableEntry+1f[/FONT]
[FONT=verdana]BiosVersion = 0901[/FONT]
[FONT=verdana]BiosReleaseDate = 11/24/2011[/FONT]
[FONT=verdana]SystemManufacturer = To be filled by O.E.M.[/FONT]
[FONT=verdana]SystemProductName = To be filled by O.E.M.[/FONT]
[FONT=verdana]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]
[FONT=verdana]Debug session time: Tue Nov 20 21:39:41.100 2012 (UTC + 11:00)[/FONT]
[FONT=verdana]Loading Dump File [C:\Users\MZ\SysnativeBSODApps\112012-20576-01.dmp][/FONT]
[FONT=verdana]Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850[/FONT]
[FONT=verdana]System Uptime: 0 days 0:20:25.910[/FONT]
[FONT=verdana]BugCheck 1000007E, {c0000005, 82ae9cbd, 80795a4c, 80795630}[/FONT]
[FONT=verdana]Probably caused by : ntkrpamp.exe ( nt!RtlImageNtHeaderEx+4a )[/FONT]
[FONT=verdana]Bugcheck code 1000007E[/FONT]
[FONT=verdana]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/FONT]
[FONT=verdana]PROCESS_NAME:  rundll32.exe[/FONT]
[FONT=verdana]BUGCHECK_STR:  0x7E[/FONT]
[FONT=verdana]FAILURE_BUCKET_ID:  0x7E_nt!RtlImageNtHeaderEx+4a[/FONT]
[FONT=verdana]BiosVersion = 0901[/FONT]
[FONT=verdana]BiosReleaseDate = 11/24/2011[/FONT]
[FONT=verdana]SystemManufacturer = To be filled by O.E.M.[/FONT]
[FONT=verdana]SystemProductName = To be filled by O.E.M.[/FONT]
[FONT=verdana]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]


Another BSOD caused by userinit -
Specifies the programs that Winlogon runs when a user logs on. By default, Winlogon runs Userinit.exe, which runs logon scripts, reestablishes network connections, and then starts Explorer.exe, the Windows user interface.
so this shouldn't be the problem.

rundll32.exe is a Windows program which downloads data for services, updates etc. so that shouldn't be the problem either.

You mention your external hard drive - use these "
www.carrona.org/hddiag.html" to diagnose the problem.
 


Last edited:
This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.