event viewer error codes Results

Page 1 of 3.
Results 1...20 of 54

Sponsored Links:

Somebody recently posted about error codes that show in their Event Viewer. I've searched and can't find that post now. They wondered if they were the only ones seeing them. All I show in mine is Kernel PnP 219(212). I thinks it has to do with USB drivers. The remove hardware safely is showing now with printer and external drives all off. In W7 the Icon only appears when one of them is powered on.


I have this error in my event viewer:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 10/17/2004
Time: 9:44:17 AM
User: N/A
Computer: DAVID
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was 80070005 from line 44 of
d:qxp_slpcomcom1xsrceventstier1eventsystemo bj.cpp. Please contact
Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at

Going to help/support yielded no additional information.

Can anyone here help?

David Nimon

New computer (1 month) with Win Vista…..EVENT VIEWER shows a number of errors and warnings that I need additional info on…..I guess the best way to tackle them is to post each separately…..This one is-----

Application Error code 10 > Source: WMI …….as follows—

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Please help me with what I need to do about this……Thanx…..

Hey first of all,

I've been getting bluescreens (most often) shortly after booting up and even if I managed to remain logged in for a longer period of time, they'd catch me eventually.

The Bluescreen Message:

"ATIkmpag.sys - adress FFFFF800480694 base at FFFFF8004800000, date stamp 4cc700d"

The exact codes tend to vary after each bsod, no idea if that is normal, but I thought of mentioning that.

After excessive googling the only thing I could come up with is it being a driver issue, so I deinstalled the catalyst driver -> reboot -> run safe mode -> run driver sweeper -> delete all ATI files, several times without any help.

Event Viewer gave me these kind of Event Types:


Event ID - 41, Source - Kernel Power, Log - System, Last Hour - 4


Event ID - 6008, Source - EventLog, Log - System, Last Hour 4

Event ID - 7026, Source - Service Control Manager, Log - System, Last Hour - 4

Sadly I do not know anything about the Event Manager its meanings, so I'm hoping for assistance.

Other information:

Windows 7 64 Bit


Graphic Driver - 10-10_vista64_win7_64_dd_ccc_enu (the most recent catalyst driver), also I've tried downgrading to 10-9 without any success.

Thanks in advance,


Hey guys,
I recently obtained a new graphics card (AMD Radeon HD 6870) and wanted to start my computer afresh. So, I reinstalled windows via Boot CD and installed all the AMD drivers as well as a few programs like AVAST! , Java x64, Malwarebytes, Steam, Firefox, and of course Minecraft.
Now, I can run the internet pretty well and there arent any errors when browsing, But, when I attempt to play a game such as Minecraft or even a simple game such as Darwinia, My computer crashes into blue and black stripes.
I checked the Event Viewer and found that everytime before my computer crashed, the error message~ "Ntfs: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume ." appears with error code of 55.
I looked up a few solutions to this such as running Chkdsk (led to no bad sections)
and even Chkntfs on both my C: drive and D: drive (both were "not dirty")

I have no idear what the problem is.. im pretty sure its something with my Hard Drive (1Tb WD ) ... but again i have no idea

please, please help me!

BSOD error message

0x0000007f (ox0000000000000008, 0x0000000080031, ox00000000000006f8, oxfffff800028dabd0)

Just curious what the stuff in the parenthesis means? i believe ox7f is hardware/driver issue, but i'm not a doctor. i don't know.

This has been happening it seems almost randomly. I have been working my computer pretty hard but i expect the best. I was pondering replacing some parts because I realize machines get old. shouldn't be, but the first thing i'm addressing is heat. new computer case in the mail for more fan room, and the first building block when i build a new system

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name TIMMY-PC
System Manufacturer BIOSTAR Group
System Model TA790GX 128M
System Type x64-based PC
Processor AMD Phenom(tm) II X4 940 Processor, 3000 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 080014, 1/13/2009
SMBIOS Version 2.5
Windows Directory C:Windows
System Directory C:Windowssystem32
Boot Device DeviceHarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Timmy-PCTimmy
Time Zone US Mountain Standard Time
Installed Physical Memory (RAM) 6.00 GB
Total Physical Memory 6.00 GB
Available Physical Memory 4.51 GB
Total Virtual Memory 12.0 GB
Available Virtual Memory 10.3 GB
Page File Space 6.00 GB
Page File C:pagefile.sys

Just in case you need that.

Thanks for your help! Attached Files W7F_13-04-2013.rar (287.1 KB, 21 views) Share Share this post on Digg Del.icio.us Technorati Twitter
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left;   JavaScript must be enabled 04-14-2013 #2 usasma Microsoft Community Contributor This member is a certified Microsoft Community Contributor at Windows 7 Forums. Click here for more information from Microsoft. Microsoft MVP - Windows Expert
- Consumer  
Join Date Mar 2010 Posts 1,333 Re: BSOD - w7f and error codes attached Info on the STOP 0x7F error: BSOD Index
Please note the "Usual Causes" section up near the top of that section
Also, you'll have to scroll down to see what the stuff in the parentheses means:
Code: WinDbg Help File Entry: The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. This trap could be a bound trap (a trap the kernel is not permitted to catch) or a double fault (a fault that occurred while processing an earlier fault, which always results in a system failure).Parameters The first parameter that appears on the blue screen specifies the trap number. The most common trap codes include the following: 0x00000000, or Divide by Zero Error, indicates that a DIV instruction is executed and the divisor is zero. Memory corruption, other hardware problems, or software failures can cause this error.0x00000004, or Overflow, occurs when the processor executes a call to an interrupt handler when the overflow (OF) flag is set.0x00000005, or Bounds Check Fault, indicates that the processor, while executing a BOUND instruction, finds that the operand exceeds the specified limits. A BOUND instruction ensures that a signed array index is within a certain range.0x00000006, or Invalid Opcode, indicates that the processor tries to execute an invalid instruction. This error typically occurs when the instruction pointer has become corrupted and is pointing to the wrong location. The most common cause of this error is hardware memory corruption.0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault: A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.A hardware problem. The less-common trap codes include the following: 0x00000001 — A system-debugger call0x00000003 — A debugger breakpoint0x00000007 — A hardware coprocessor instruction with no coprocessor present0x0000000A — A corrupted Task State Segment0x0000000B — An access to a memory segment that was not present0x0000000C — An access to memory beyond the limits of a stack0x0000000D — An exception not covered by some other exception; a protection fault that pertains to access violations for applications For other trap numbers, see an Intel architecture manual.Cause Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails. A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.Resolving the Problem Debugging: Always begin with the !analyze extension. If this extension is not sufficient, use the kv (Display Stack Backtrace) debugger command. If kv shows a taskGate, use the .tss (Display Task State Segment) command on the part before the colon.If kv shows a trap frame, use the .trap (Display Trap Frame) command to format the frame.Otherwise, use the .trap (Display Trap Frame) command on the appropriate frame. (On x86-based platforms, this frame is associated with the procedure NT!KiTrap.) After using one of these commands, use kv again to display the new stack. Troubleshooting: If you recently added hardware to the computer, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics that the system manufacturer supplies to determine which hardware component failed. The memory scanner is especially important. Faulty or mismatched memory can cause this bug check. For more informaiton about these procedures, see the owner's manual for your computer. Check that all adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. If the error appears on a newly installed system, check the availability of updates for the BIOS, the SCSI controller, or network cards. These kind of updates are typically available on the Web site or BBS of the hardware manufacturer. Confirm that all hard disk drives, hard disk controllers, and SCSI adapters are listed in the Microsoft Windows Marketplace Tested Products List. If the error occurred after the installation of a new or updated device driver, you should remove or replace the driver. If, under this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console in order to access the file. Also restart your computer, and then press F8 at the character-based menu that displays the operating system choices. At the Advanced Options menu, select the Last Known Good Configuration option. This option is most effective when you add only one driver or service at a time. Overclocking (setting the CPU to run at speeds above the rated specification) can cause this error. If you have overclocked the computer that is experiencing the error, return the CPU to the default clock speed setting. Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error. You can also disable memory caching of the BIOS to try to resolve the problem. If you encountered this error while upgrading to a new version of the Windows operating system, the error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners before you upgrade. Contact the software manufacturer to obtain updates of these tools. Also make sure that you have installed the latest Windows Service Pack. Finally, if all the above steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. WinDbg Output Example: UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80002af243d There are no memory dumps included in the uploaded files, please zip up the contents of the C:WindowsMinidump folder and upload it with your next post. Please check this page to ensure the system is set to save minidumps: Set MiniDump Finally, don't use disk cleaning programs (such as CCleaner) while we're troubleshooting (they delete the files that we need).

Only 118 Windows Updates installed. Most systems have 150 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

As there's no evidence of BSOD's in the WER section of MSINFO32, I'd have to suspect that this might be a hardware problem. Please start with these free hardware diagnostics: Hardware Diagnostics

Good luck!

I have Windows XP Home Edition.

In event viewer, I keep getting the following application error message
every so often:

Event Type: Error
Event Source: PerfNet
Event Category: None
Event ID: 2004
Date: 8/29/2004
Time: 10:03:20 AM
User: N/A
Computer: JEMADSEN
Unable to open the Server service. Server performance data will not be
returned. Error code returned is in data DWORD 0.

For more information, see Help and Support Center at
0000: 34 00 00 c0 4..À

When I go into Command Prompt, I get:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsJim MadsenNet Statistics
Statistics are available for the following running services:


The command completed successfully.

So what does this error mean? And what is this Server service, I
shouldn't have a server running.


Hello fellow Newsgroup members. :-)

I have a computer running Windows XP Home Editon. This is a stand alone
computer, it is not connected to a network.

Since I have had my computer there are always 3 different Failure Audits
shown in the secruity log in the Event Viewer. The Event Viewer is under
Aministrative Tools in the Start Menu.

When I click on the Failure Audit event messages in the Event Viewer this is
the information given for each of the 3 different Failure Audits:


Source: Secruity
Category: Policy Change
Type: Failure Audit
Event ID: 615

IPSec Services: IPSec Services failed to get the complete list of network
interfaces on the machine. This can be a potential security hazard to the
machine since some of the network interfaces may not get the protection as
desired by the applied IPSec filters. Please run IPSec monitor snap-in to
further diagnose the problem.
I have tried to run the IPSec monitor snap-in but I could not figure out how
to use it. I clicked on the help link in the error message but the
information in the help web site is too technical for me to understand.

This event, 615 Policy Change, has a Failure Audit when the computer starts
and sometimes has a Success Audit straight after.


Source: Secruity
Category: Account Logon
Type: Failure Audit
Event ID: 680

Logon account: "User Name"
Source Workstation: "Computer Name"
Error Code: 0xC000006A
This event, 680 Account Logon, always has a Failure Audit when the computer
starts and always has a Success Audit straight after.


Source: Secruity
Category: Logon/Logoff
Type: Failure Audit
Event ID: 529

Logon Failu
Reason: Unknown user name or bad password
User Name: "User Name"
Domain: "Computer Name"
Logon Type: 2
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: "Computer Name"
I do have a password created for my Windows XP Account, which is an
administrators account. I enter the password on the welcome screen and I can
log on with no problem. So why do I have this error which says that there is
an "unknown user name or bad password" when I am able to log on perfectly??

This event, 529 Logon/Logoff, always has a Failure Audit. It has never had
a Success Audit!!! But like I said, I am always able to log on to my Windows
XP account using my user name and password at the welcome screen everytime.


What are the causes of each of these 3 Failure Audits?

How can I fix these Failure Audits and prevent them from happening again?

Are these 3 Failure Audits a serious threat to my computer?

Can someone please help me correct these errors. I am NOT a computer expert
so for me to understand your generous help and advice, please do not use
technical computer language and acronymes.

I am very grateful for any help and advice you generous people out there are
willing to give me!!! :-) :-)


Techno Phobe.

The following entries occur it seems when I log on and are taken from the
security log of the event viewer. However, I know my Password and so they
do not make any sense. I have the WinXP SP2 Firewall enabled as well as
Norton Anti-Virus software running PLUS I am behind a router. Of course you
can imagine my concern that someone might be trying to hack my system. Any
responses greatly appreciated. Thank you.

Logon Failu
Reason: Unknown user name or bad password
User Name: *** *********
Logon Type: 2
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: FAMILYR

For more information, see Help and Support Center at


Logon account: *** *********
Source Workstation: FAMILYR
Error Code: 0xC000006A

For more information, see Help and Support Center at


I am kasinath.

I am getting the error in event viewer event ID:7023;"The Logical Disk Manager Service terminated with the following error:

"The specified module could not be found." This error is listed in the event viewer when ever I start my system.

I am using windows xp professional with sp3 with all latest window updates.

I am using kaspersky internet security 2011 ( nad microsoft security essentials.

The windows Help & supportgives follwoing details.

ID: 7023
version 5.2

Explanation: The specified service stopped unexpectedly with the error indicated int message ,The service closed safely.

I followed the suggested user action as follows

1) service: Logical disk Manager.

service name : dmserver

start type : automatic
status : stopped.

sc query dmserver gave following result.

service_name : dnserver
: 1 stopped

WIN32-EXIT-CODE : 126 (0x7e)

service-exit-code: 0
check point : 0x0
wait-hint 0x0

.I tried the command sfc /scannow as suggested by a website ,using my winxp sp3 slipstreamed cd.

It simply run, with out any message.

I would like user expert option why this error occurs and How to solve it.

Note: My system sometimes goes slow or hangs while browsing(esspecially IE8) or while on the regular usage.

MY system is compaq presario SR1630il, 2GB RAM, two hard disks 1) 500GB seagate with 250GB of two partition and 2) 80GB samsung disk with two partion of 40GB each.

system partition is 250GB partition of the seagate disk.

Iam having broadband net connection of upto 2MBPS.

Kindly advice


Went to the Event Viewer and found 154 occurances of the following error:
"A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 70. The Windows SChannel error state is 105."

Anyone else see these? Doesn't seem to impact anything that I can see.


I'm running Windows 7 x64 build 7229. In Event viewer I'm seeing warning from Microsoft-Windows-WHEA-Logger every few seconds but I can't pinpoint what is causing it. Can anyone decipher the event below?

A corrected hardware error has occurred.
Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)
Busevice:Function: 0x0:0x3:0x0
Vendor IDevice ID: 0x8086:0x340a
Class Code: 0x30400
The details view of this entry contains further information.


Hi everybody,

I installed Windows 7 x64 Enterprise edition yesterday and I got different errors at least 100 times. I'm getting errors of "Windows Live Messenger", Sidebar and mostly "Internet Explorer 8" Here are some reports from Event Viewer. Any help is appreciated.

Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bca42
Faulting module name: mshtml.dll, version: 8.0.7600.16385, time stamp: 0x4a5bdfcd
Exception code: 0xc0000005
Fault offset: 0x00000000001333a2
Faulting process id: 0x1ec
Faulting application start time: 0x01ca194f8a6f3880
Faulting application path: C:Program FilesInternet Exploreriexplore.exe
Faulting module path: C:WindowsSystem32mshtml.dll
Report Id: c82a0ba0-8542-11de-b652-00248c58a11f

Faulting application name: msnmsgr.exe, version: 14.0.8064.206, time stamp: 0x498cf586
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdb3b
Exception code: 0xc0000005
Fault offset: 0x00032f15
Faulting process id: 0x2f8
Faulting application start time: 0x01ca18662cb8ecc0
Faulting application path: C:Program Files (x86)Windows LiveMessengermsnmsgr.exe
Faulting module path: C:WindowsSysWOW64ntdll.dll
Report Id: 8f7c4780-8459-11de-a691-00248c58a11f

Faulting application name: sidebar.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc9e1
Faulting module name: mshtml.dll, version: 8.0.7600.16385, time stamp: 0x4a5bdfcd
Exception code: 0xc0000005
Fault offset: 0x00000000001333a2
Faulting process id: 0x95c
Faulting application start time: 0x01ca1949cb6fa8c0
Faulting application path: C:Program FilesWindows Sidebarsidebar.exe
Faulting module path: C:WindowsSystem32mshtml.dll
Report Id: dd138000-8542-11de-b652-00248c58a11f

My conf:
AMD Phenom II X4 940
ATI Radeon HD4890

Hello, I'm new here and glad to be here. I have a Dell Studio XPX8000 with a WD 640GB Hard Drive. About a month ago I started noticing, in Event Viewer, the following message:
"The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume OS."
It is event ID 55. It says, in the last 7 days I have had another 110 of these. Now back about a month ago I reported this to dell and told them after running chkdsk utility many times the error still existed. They told me to run a procedure from boot up. I forget how I got there but I ran some tests. The first one, confidence test, had a result: No problems found. Do you want to continue w/rest of the Confidense Test - about 91 minutes, and I proceeded. Over the next 2 hours or so I got the following messages:
No additional sense information
Test Results: Fail
Error Code OFOO:1344 Msg Disk block 727663631: can't read-replace disk.
No additional sense information
Test Results: Fail
Error Code OFOO:1344 Msg Disk block 754830164: can't read-replace disk.
No additional sense information
Test Results: Fail
Error Code OFOO:1344 Msg Disk block 860399191: can't read-replace disk.
No additional sense information
Test Results: Fail
Error Code OFOO:1344 Msg Disk block 727663631: can't read-replace disk.

At this point I stopped running the tests and called Dell. The sent a guy with a new WD Hard Drive 2 days later. Now I'm into the new hard drive and I'm still getting the messages in Event Viewer about the NTFS
Now the replacement Hard Drive is giving the same NTFS Error Messages. What are the chances of 2 Western Digital Hard Drives with the same problem(s), winding up in my Dell PC. I didn't run any of the previously talked about tests because, as I said, I forget how I got to the screen to run them, and also they are soooo time consuming.
I've only upgraded from Vista to WIN 7 Home Premium recently and didn't notice the messages before the upgrade. After the Hard Drive replacement and all that goes with that, I downloaded the Upgrade for WIN 7 again and installed it. Is there any possibility that there is something going on with WIN 7?

Thanks for any and all help! I'm sorta lost

I built my computer in 2001, and here are the specs fully
assembled, when problems started:

Epox EP-8KHA+ Motherboard (VIA KT266A chipset)
AMD Athlon 1800+ (1.53GHz)
2 Micron 256MB PC2100 DDR SDRAM
2 Maxtor 6L040J2 40GB 7200rpm ATA-133 drives
Enermax 350w PSU
Silicon Image ATA-133 PCI RAID adapter (Sil0680 chipset)
Creative Labs Audigy MP3+ PCI card w/ IEEE1394
Inno3D GeForce2 MX 400 4x AGP video card
3Com 10/100 PCI NIC
Toshiba SD-M1502 DVD drive
Brand name CD-RW drive (I forget the brand)
Agere Systems PCI soft modem
Full, legal version of WinXP Pro SP1

I haven't changed my computer's configuration since it
was built, and everything has been working fine

until the past few weeks. My computer started to randomly
reboot at any given time, no matter what

application I was using, even when I wasn't using the PC
and it was idle. It would immediately go to a

blue screen that would flash on the screen for a few
seconds before rebooting. Occasionally there was an

error at Windows startup as well that said the computer
recovered from a serious error and asked me to

report it to MS - I did, and every time it would tell me
a device driver caused the problem but wouldnt

tell me which. A few times, it said it was a graphics
device driver that caused it. Knowing this, I made

sure I had the most up-to-date graphics adapter drivers -
I did. I then tried older drivers, and the PC

was still rebooting. Suspecting a video hardware failure,
I removed my card and tried a different video

card - no help, the PC still rebooted and gave me errors.

I figured my Windows install was corrupt, so I
reformatted my PC and reinstalled WindowsXP - didn't

help. In fact, it even gave me a blue screen and rebooted
during Windows setup (after I had formatted

the drive).

I used the Microsoft-provided memory diagnostics check,
and the memory passed all tests without a hitch.

Next I decided to remove all components in my PC except
the essentials. I took out everyting except the

video card, CD drive, and one hard drive. I disabled the
RAID 0 and took out the RAID card so I was down

to one Maxtor 40GB hard drive hooked directly to the
motherboard IDE. I took out the sound card, network

card, and modem. I reformatted this drive and reinstalled
Windows on it, but the Pc still had the same

problems. I also cleaned the inside of the PC with a
compressed gas duster and made sure the fans were

all clean.

Now I was suspecting either a Power Supply failure or
motherboard/processor failure. My motherboard was

setup to sound an alarm or turn off the system if the CPU
was too hot or the fans weren't working.

However, this never happened. I opted to try the least
expensive fix for the situation. I replaced my

power supply with a brand new Antec 350w SmartPower.
Didn't help. However, during replacing the PSU and

cleaning out the inside of the PC, I noticed that the
transistors on the motherboard (I dont know what

they're called actually - perhaps capacitators? ...those
silver pencil-eraser-sized barrels wrapped in

sheathing), particularly the ones around the processor
had a rust-colored chemical buildup of some kind

on the top of them. I gently scraped as much of it off
them as I could.

I am at a loss for what to do next. Is it time to go
ahead and buy a new motherboard/processor, or are

there other things I didn't check that I should have.
PLEASE HELP ME!!!! Any help would be greatly



Joe Przedwiecki

I installed IDimager Pro Version 5 on my Windows 7 Ultimate 64-bit machine and it appeared to install correctly in the X86 programs. However, whenever I attempt to start the application, I get a Runtime Error 217. I have performed all the normal registry cleaning; remove and reinstall procedures. The error and information messages I get in Windows 7 Event Viewer are as follows:

Error Message from Windows 7 Event Viewer

Faulting application name: IDimager.exe, version:, time stamp: 0x2a425e19

Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf

Exception code: 0x0eedfade

Fault offset: 0x0000b727

Faulting process id: 0x153c

Faulting application start time: 0x01cb13260f30c28d

Faulting application path: C:Program Files (x86)IDimager ProductsIDimagerIDimager.exe

Faulting module path: C:Windowssyswow64KERNELBASE.dll

Report Id: 4dde561a-7f19-11df-940b-00221576694a

Information Message from Windows 7 Event Viewer

Fault bucket 1918837260, type 1

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: IDimager.exe


P3: 2a425e19


P5: 6.1.7600.16385

P6: 4a5bdbdf

P7: 0eedfade

P8: 0000b727



Attached files:

C:UsersDonald PC2AppDataLocalTempWER3D8A.tmp.WERInternalMeta data.xml

Thank you for any assistance.

I am experiencing a flashing blue screen on my computer(not a BSOD) after the computer locks due to idling.

I am able to log back in after forcing a reboot.

Event Viewer yields the following:

Log Name: Application
Source: Application Error
Date: 2/6/2013 8:06:35 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Chris-win8.techcess.local
Faulting application name: LogonUI.exe, version: 6.2.9200.16384, time stamp: 0x5010a7f4
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505ab405
Exception code: 0xc0000374
Fault offset: 0x00000000000ea485
Faulting process ID: 0x83c
Faulting application start time: 0x01ce04732ca08bd9
Faulting application path: C:Windowssystem32LogonUI.exe
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Report ID: 6a589894-7066-11e2-be83-80dcc92ac612
Faulting package full name:
Faulting package-relative application ID:
Event Xml:




Thanks in advance

Firstly i would like to say sorry for not reading the "sticky" threads.

my computer has BSODed on me twice now in two days, my primary hhd failed last week so i bought a SSD to replace it. Could the failure be related to the BSODs?

I was running minecraft and hosting a server at the time- just two of us. an hour or so of it and then it just BSODed on me.

I tried google the error codes in event viewer but i cant really understand what they all mean. Source: kernel-power .... event id:41 .... bugcheckcode:122

sorry about my earlier post and i hope this is better?

Thank you


I am having a sony vaio VGN-FW51MF which had windows 7 home. I made a clean install of windows 7 professional but I am facing BSOD problems.

I try to update the yk62x64.sys file (Miniport Driver for Marvell Yukon Ethernet Controller., Marvell) from the Marvell website, the bsod stopped but the computer freezes in random times, so I roll back to the old driver. Can you help me with debbuging ? I attach the dump files and cpu-z screens!


Attached Files dumps.zip (237.6 KB, 14 views) RAMMon - SPD Info.txt (18.2 KB, 53 views) Last edited by Nexuz; 08-26-2011 at 02:27 PM. Share Share this post on Digg Del.icio.us Technorati Twitter
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left;   JavaScript must be enabled 08-26-2011 #2 zigzag3143 Senior Member Wanikiya  
Join Date Jun 2009 Posts 402 Blog Entries1 Re: BSOD on win7 - Help Debugging Originally Posted by Nexuz Hi,

I am having a sony vaio VGN-FW51MF which had windows 7 home. I made a clean install of windows 7 professional but I am facing BSOD problems.

I try to update the yk62x64.sys file (Miniport Driver for Marvell Yukon Ethernet Controller., Marvell) from the Marvell website, the bsod stopped but the computer freezes in random times, so I roll back to the old driver. Can you help me with debbuging ? I attach the dump files and cpu-z screens!


It is the yk62x64.sys driver in every case. Yours is dated before win 7 was even released. If the computer freezes on the newer driver what does event viewer say about it?

There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Event viewer (local) and look for the critical errors listed in the last day, week, etc. Then go to the windows log>application tab. Finally the windows Logs>system tabs.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are. Attached Thumbnails   Share Share this post on Digg Del.icio.us Technorati Twitter
MS MVP - Windows Consumer Expert 2010-2013
Wanikiya & Dyami

Operating System Win 7
Computer Type Dell
CPU Type and Speed quad
Motherboard Chipset dell
System Memory Type 8gig
Video Card Type and Speed ati
Computer Monitor 15.4
Hard Drive WD 540 gig
Optical Drives dvd rw
Network Adapter dell 1390
Anti-virus Software ESS 5.x
Computer Skill Level Certified Professional
Windows Experience Index 5.9
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left;   JavaScript must be enabled 08-26-2011 #3 Nexuz Junior Member  Thread Starter Enjoys Windows 7 Forums  
Join Date Aug 2011 Posts 3 Re: BSOD on win7 - Help Debugging Thanks for your reply ;-)

Here is the requested screenshots.

Any solution ?

Здравей те, наясно съм че едвали за първи път виждате подобна тема, но Ви моля да ми помогне те. Не съм сигурна какво точно се случва с лаптом ми, но напоследък блокира и нищо освен рестата не помага. Лошото е, че като прегледам Event Viewer ми показва няколко грешчици. Моля Ви да ми помогнете, защото имам спешна нужда от работещ лаптоп. Не знам точно какво Ви трябва затова ви давам тази информация, ако мога да направя още нещо ще го направя. Благодаря Ви. Attached Files Seven Forums.rar (712.2 KB, 76 views) Last edited by akashy; 07-01-2011 at 01:14 PM. Share Share this post on Digg Del.icio.us Technorati Twitter
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left;   JavaScript must be enabled 07-03-2011 #2 Elmer Tier 2 Moderator Resident eejit  
Join Date Mar 2010 Posts 1,946 Re: ]Много Ви моля за спешна помощ As per Google Translate: Hey you, I am aware that only the first time you see a similar theme, but please help me they are. I'm not sure what happens to my laptom, but recently blocked and nothing but the change does not help. The bad thing is that as I review the Event Viewer shows several greshchitsi. Please help me, because I urgently need a working laptop. I do not know exactly what you need so I give you this information if I can do something else to do. Thank you. Hi Akashy and Welcome to the Forum. Добре дошли на форума
Please note any links given are to English UK/US sites. You may have to find language specific drivers.

Usual causes: Device driver
Usual causes: Device driver

Your dump files list athr.sys Mon Oct 05 17:31:48 2009 as the probable cause. This is your Atheros Extensible Wireless LAN driver for CB42/CB43/MB42/MB43 Network Adapter (D-Link AirPlus DWL-G520 Wireless PCI Adapter(rev.B) discontinued 2008). Atheros

Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes.

Outdated Drivers. Update:

ATKACPI.sys Thu Dec 14 07:11:57 2006 ATK Hotkey ATK0101 ACPI Utility Driver
ASMMAP.sys Sun Feb 04 19:52:50 2007 LENOVO ATK Hotkey ATK0101 ACPI UTILITY

nvsmu.sys Mon Aug 25 11:22:50 2008 nVidia nForce chipset driver

Rt86win7.sys Thu Feb 26 09:04:22 2009 Realtek PCIe GBE Family Controller v7.046

sncduvc.SYS Mon May 12 04:20:30 2008
snp2uvc.sys Mon Aug 11 03:14:10 2008 Suyin USB 2.0 Webcam driver. Check with your O.E.M. Support

Drivers with Updates:

nvlddmkm.sys Wed Mar 17 02:45:14 2010 nVidia Graphics Drivers.

Download the latest Graphics DriversDownload and install Driver Sweeper in normal mode.Boot to Safe ModeUninstall your current Graphics Driver set up using Driver Sweeper.Reboot to Normal Mode.Install your new Graphics Driver set up.

Bugcheck Analysis: Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {1c, 2, 1, 91cc38c5} Unable to load image SystemRootsystem32DRIVERSathr.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for athr.sys *** ERROR: Module load completed but symbols could not be loaded for athr.sys Probably caused by : athr.sys ( athr+c18c5 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000001c, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: 91cc38c5, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d69718 Unable to read MiSystemVaType memory at 82d49160 0000001c CURRENT_IRQL: 2 FAULTING_IP: athr+c18c5 91cc38c5 c7401c00000000 mov dword ptr [eax+1Ch],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: b68a9b2c -- (.trap 0xffffffffb68a9b2c) ErrCode = 00000002 eax=00000000 ebx=82d3b580 ecx=00000000 edx=870f8020 esi=00000040 edi=868b0c28 eip=91cc38c5 esp=b68a9ba0 ebp=b68a9ba8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246 athr+0xc18c5: 91cc38c5 c7401c00000000 mov dword ptr [eax+1Ch],0 ds:0023:0000001c=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 91cc38c5 to 82c4781b STACK_TEXT: b68a9b2c 91cc38c5 badb0d00 870f8020 870f8020 nt!KiTrap0E+0x2cf WARNING: Stack unwind information not available. Following frames may be wrong. b68a9ba8 91cbdb2a 870f8020 870f6000 b68a9bcc athr+0xc18c5 b68a9bf8 91c7efd8 870f8020 00000001 870f6000 athr+0xbbb2a b68a9c38 91c76704 870f4020 86c8d020 b68a9c6c athr+0x7cfd8 b68a9c48 91c38d40 86c8d020 868b0c28 00000040 athr+0x74704 b68a9c6c 91c048b8 8af8e028 b68a9ca8 00000000 athr+0x36d40 b68a9c88 91c07892 870e7028 b68a9ca8 8af79748 athr+0x28b8 b68a9cdc 8b31330a 8af79748 86b486b8 b68a9d00 athr+0x5892 b68a9cec 82e21b25 86cd0028 86b486b8 85cfed48 ndis!ndisDispatchIoWorkItem+0xf b68a9d00 82c6f03b 868b0c28 00000000 85cfed48 nt!IopProcessWorkItem+0x23 b68a9d50 82e0f9df 80000000 8cfcfa25 00000000 nt!ExpWorkerThread+0x10d b68a9d90 82cc11d9 82c6ef2e 80000000 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: athr+c18c5 91cc38c5 c7401c00000000 mov dword ptr [eax+1Ch],0 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: athr+c18c5 FOLLOWUP_NAME: MachineOwner MODULE_NAME: athr IMAGE_NAME: athr.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4aca1f74 FAILURE_BUCKET_ID: 0xD1_athr+c18c5 BUCKET_ID: 0xD1_athr+c18c5 Followup: MachineOwner Drivers: Code: 8b1b0000 8b1f8000 ACPI ACPI.sys Tue Jul 14 00:11:11 2009 (4A5BBF0F) 90c94000 90cee000 afd afd.sys Tue Jul 14 00:12:34 2009 (4A5BBF62) 91d94000 91da6000 AgileVpn AgileVpn.sys Tue Jul 14 00:55:00 2009 (4A5BC954) 8b2b0000 8b2b9000 amdxata amdxata.sys Tue May 19 18:57:35 2009 (4A12F30F) 8b2fe000 8b308000 AsDsm AsDsm.sys Fri Feb 13 06:13:31 2009 (49950F8B) 91ff9000 92000000 ASMMAP ASMMAP.sys Sun Feb 04 19:52:50 2007 (45C63992) 8b27a000 8b283000 atapi atapi.sys Tue Jul 14 00:11:15 2009 (4A5BBF13) 8b283000 8b2a6000 ataport ataport.SYS Tue Jul 14 00:11:18 2009 (4A5BBF16) 91c02000 91d2f000 athr athr.sys Mon Oct 05 17:31:48 2009 (4ACA1F74) 91d7f000 91d87000 ATKACPI ATKACPI.sys Thu Dec 14 07:11:57 2006 (4580F93D) a5ef2000 a5f1a000 AVGIDSDriver AVGIDSDriver.Sys Tue Aug 03 23:24:21 2010 (4C589715) 8b91b000 8b924000 AVGIDSEH AVGIDSEH.Sys Mon Sep 13 23:46:35 2010 (4C8EA9CB) a0b2e000 a0b38000 AVGIDSFilter AVGIDSFilter.Sys Tue Aug 03 23:23:18 2010 (4C5896D6) a0b46000 a0b4f000 AVGIDSShim AVGIDSShim.Sys Tue Aug 03 23:25:56 2010 (4C589774) 910a7000 910e2d00 avgldx86 avgldx86.sys Wed Dec 08 02:00:20 2010 (4CFEE6B4) 8b976000 8b982000 avgmfx86 avgmfx86.sys Tue Sep 07 01:48:01 2010 (4C858BC1) 8b916000 8b91ab80 avgrkx86 avgrkx86.sys Tue Sep 07 01:48:16 2010 (4C858BD0) 90c1a000 90c61980 avgtdix avgtdix.sys Fri Nov 12 11:05:58 2010 (4CDD1F96) 91d39000 91d72000 ay9z8b9w ay9z8b9w.SYS Tue Jul 14 22:12:41 2009 (4A5CF4C9) 83200000 8320b000 BATTC BATTC.SYS Tue Jul 14 00:19:15 2009 (4A5BC0F3) 8b989000 8b990000 Beep Beep.SYS Tue Jul 14 00:45:00 2009 (4A5BC6FC) 91099000 910a7000 blbdrive blbdrive.sys Tue Jul 14 00:23:04 2009 (4A5BC1D8) 832be000 832c6000 BOOTVID BOOTVID.dll Tue Jul 14 02:04:34 2009 (4A5BD9A2) a0a8a000 a0aa3000 bowser bowser.sys Tue Jul 14 00:14:21 2009 (4A5BBFCD) 99120000 9913e000 cdd cdd.dll unavailable (00000000) 8b957000 8b976000 cdrom cdrom.sys Tue Jul 14 00:11:24 2009 (4A5BBF1C) 83308000 833b3000 CI CI.dll Tue Jul 14 02:09:28 2009 (4A5BDAC8) 8b8f1000 8b916000 CLASSPNP CLASSPNP.SYS Tue Jul 14 00:11:20 2009 (4A5BBF18) 832c6000 83308000 CLFS CLFS.SYS Tue Jul 14 00:11:10 2009 (4A5BBF0E) 91d7b000 91d7e700 CmBatt CmBatt.sys Tue Jul 14 00:19:18 2009 (4A5BC0F6) 8b57a000 8b5d7000 cng cng.sys Tue Jul 14 00:32:55 2009 (4A5BC427) 8b000000 8b008000 compbatt compbatt.sys Tue Jul 14 00:19:18 2009 (4A5BC0F6) 91d87000 91d94000 CompositeBus CompositeBus.sys Tue Jul 14 00:45:26 2009 (4A5BC716) 9882c000 98839000 crashdmp crashdmp.sys Tue Jul 14 00:45:50 2009 (4A5BC72E) 9101d000 91081000 csc csc.sys Tue Jul 14 00:15:08 2009 (4A5BBFFC) 91081000 91099000 dfsc dfsc.sys Tue Jul 14 00:14:16 2009 (4A5BBFC8) 90dab000 90db7000 discache discache.sys Tue Jul 14 00:24:04 2009 (4A5BC214) 8b8e0000 8b8f1000 disk disk.sys Tue Jul 14 00:11:28 2009 (4A5BBF20) 91ef3000 91f0c000 drmk drmk.sys Tue Jul 14 01:36:05 2009 (4A5BD2F5) 91f25000 91f30000 dump_dumpata dump_dumpata.sys Tue Jul 14 00:11:16 2009 (4A5BBF14) 91f3a000 91f4b000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:12:47 2009 (4A5BBF6F) 91f30000 91f3a000 dump_msahci dump_msahci.sys Tue Jul 14 00:45:50 2009 (4A5BC72E) 98817000 98821000 Dxapi Dxapi.sys Tue Jul 14 00:25:25 2009 (4A5BC265) 93125000 931dc000 dxgkrnl dxgkrnl.sys Tue Nov 02 02:37:53 2010 (4CCF7981) 90db7000 90df0000 dxgmms1 dxgmms1.sys Thu Feb 03 03:34:49 2011 (4D4A2259) 8b2ed000 8b2fe000 fileinfo fileinfo.sys Tue Jul 14 00:21:51 2009 (4A5BC18F) 8b2b9000 8b2ed000 fltmgr fltmgr.sys Tue Jul 14 00:11:13 2009 (4A5BBF11) 8b5e5000 8b5ee000 Fs_Rec Fs_Rec.sys unavailable (00000000) 8b8ae000 8b8e0000 fvevol fvevol.sys Sat Sep 26 03:24:21 2009 (4ABD7B55) 8b7be000 8b7ef000 fwpkclnt fwpkclnt.sys Tue Jul 14 00:12:03 2009 (4A5BBF43) 83011000 83048000 hal halmacpi.dll Tue Jul 14 00:11:03 2009 (4A5BBF07) 911b5000 911d4000 HDAudBus HDAudBus.sys Tue Jul 14 00:50:55 2009 (4A5BC85F) 91e74000 91ec4000 HdAudio HdAudio.sys Tue Jul 14 00:51:46 2009 (4A5BC892) a5ff0000 a5ffb000 hiber_dumpata hiber_dumpata.sys Tue Jul 14 00:11:16 2009 (4A5BBF14) a5e0a000 a5e1b000 hiber_dumpfve hiber_dumpfve.sys Tue Jul 14 00:12:47 2009 (4A5BBF6F) a5e00000 a5e0a000 hiber_msahci hiber_msahci.sys Tue Jul 14 00:45:50 2009 (4A5BC72E) a0a05000 a0a8a000 HTTP HTTP.sys Tue Jul 14 00:12:53 2009 (4A5BBF75) 8b8a6000 8b8ae000 hwpolicy hwpolicy.sys Tue Jul 14 00:11:01 2009 (4A5BBF05) 91116000 9112e000 i8042prt i8042prt.sys Tue Jul 14 00:11:23 2009 (4A5BBF1B) 91104000 91116000 intelppm intelppm.sys Tue Jul 14 00:11:03 2009 (4A5BBF07) 9112e000 9113b000 kbdclass kbdclass.sys Tue Jul 14 00:11:15 2009 (4A5BBF13) 80b9e000 80ba6000 kdcom kdcom.dll Tue Jul 14 02:08:58 2009 (4A5BDAAA) 8b3c9000 8b3fd000 ks ks.sys Thu Mar 04 03:57:52 2010 (4B8F2FC0) 8b567000 8b57a000 ksecdd ksecdd.sys Tue Jul 14 00:11:56 2009 (4A5BBF3C) 8b650000 8b675000 ksecpkg ksecpkg.sys Fri Dec 11 04:04:22 2009 (4B21C4C6) 91f80000 91f90000 lltdio lltdio.sys Tue Jul 14 00:53:18 2009 (4A5BC8EE) 91f4b000 91f66000 luafv luafv.sys Tue Jul 14 00:15:44 2009 (4A5BC020) 83235000 832ad000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 02:06:41 2009 (4A5BDA21) 9113b000 91148000 mouclass mouclass.sys Tue Jul 14 00:11:15 2009 (4A5BBF13) 8b264000 8b27a000 mountmgr mountmgr.sys Tue Jul 14 00:11:27 2009 (4A5BBF1F) a0aa3000 a0ab5000 mpsdrv mpsdrv.sys Tue Jul 14 00:52:52 2009 (4A5BC8D4) a0ab5000 a0ad8000 mrxsmb mrxsmb.sys Sat Feb 27 07:32:02 2010 (4B88CA72) a0ad8000 a0b13000 mrxsmb10 mrxsmb10.sys Sat Feb 27 07:32:21 2010 (4B88CA85) a0b13000 a0b2e000 mrxsmb20 mrxsmb20.sys Sat Feb 27 07:32:11 2010 (4B88CA7B) 8b2a6000 8b2b0000 msahci msahci.sys Tue Jul 14 00:45:50 2009 (4A5BC72E) 8b9e2000 8b9ed000 Msfs Msfs.SYS unavailable (00000000) 8b1f8000 8b200000 msisadrv msisadrv.sys Tue Jul 14 00:11:09 2009 (4A5BBF0D) 8b53c000 8b567000 msrpc msrpc.sys unavailable (00000000) 90da1000 90dab000 mssmbios mssmbios.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD) 8b896000 8b8a6000 mup mup.sys Tue Jul 14 00:14:14 2009 (4A5BBFC6) 8b312000 8b3c9000 ndis ndis.sys Tue Jul 14 00:12:24 2009 (4A5BBF58) 91dbe000 91dc9000 ndistapi ndistapi.sys Tue Jul 14 00:54:24 2009 (4A5BC930) 91fd6000 91fe6000 ndisuio ndisuio.sys Tue Jul 14 00:53:51 2009 (4A5BC90F) 91dc9000 91deb000 ndiswan ndiswan.sys Tue Jul 14 00:54:34 2009 (4A5BC93A) 91e63000 91e74000 NDProxy NDProxy.SYS Tue Jul 14 00:54:27 2009 (4A5BC933) 90d25000 90d33000 netbios netbios.sys Tue Jul 14 00:53:54 2009 (4A5BC912) 90c62000 90c94000 netbt netbt.sys Tue Jul 14 00:12:18 2009 (4A5BBF52) 8b612000 8b650000 NETIO NETIO.SYS Tue Jul 14 00:12:35 2009 (4A5BBF63) 8b9ed000 8b9fb000 Npfs Npfs.SYS Tue Jul 14 00:11:31 2009 (4A5BBF23) 90d97000 90da1000 nsiproxy nsiproxy.sys Tue Jul 14 00:12:08 2009 (4A5BBF48) 82c01000 83011000 nt ntkrpamp.exe Wed Oct 27 03:30:44 2010 (4CC78ED4) 8b40d000 8b53c000 Ntfs Ntfs.sys Tue Jul 14 00:12:05 2009 (4A5BBF45) 8b982000 8b989000 Null Null.SYS unavailable (00000000) 93123000 93124040 nvBridge nvBridge.kmd Wed Mar 17 02:25:46 2010 (4BA03DAA) 92615000 93122c00 nvlddmkm nvlddmkm.sys Wed Mar 17 02:45:14 2010 (4BA0423A) 91148000 91151000 nvsmu nvsmu.sys Mon Aug 25 11:22:50 2008 (48B287FA) 91f90000 91fd6000 nwifi nwifi.sys Tue Jul 14 00:51:59 2009 (4A5BC89F) 90cf5000 90d14000 pacer pacer.sys Tue Jul 14 00:53:58 2009 (4A5BC916) 833e8000 833f9000 partmgr partmgr.sys Tue Jul 14 00:11:35 2009 (4A5BBF27) 833be000 833e8000 pci pci.sys Tue Jul 14 00:11:16 2009 (4A5BBF14) 8b24f000 8b256000 pciide pciide.sys Tue Jul 14 00:11:19 2009 (4A5BBF17) 8b256000 8b264000 PCIIDEX PCIIDEX.SYS Tue Jul 14 00:11:15 2009 (4A5BBF13) 8b5d7000 8b5e5000 pcw pcw.sys Tue Jul 14 00:11:10 2009 (4A5BBF0E) a0b4f000 a0be6000 peauth peauth.sys Tue Jul 14 01:35:44 2009 (4A5BD2E0) 91ec4000 91ef3000 portcls portcls.sys Tue Jul 14 00:51:00 2009 (4A5BC864) 832ad000 832be000 PSHED PSHED.dll Tue Jul 14 02:09:36 2009 (4A5BDAD0) 8b308000 8b311200 PxHelp20 PxHelp20.sys Thu Mar 13 01:57:44 2008 (47D88A18) 91da6000 91dbe000 rasl2tp rasl2tp.sys Tue Jul 14 00:54:33 2009 (4A5BC939) 931dc000 931f4000 raspppoe raspppoe.sys Tue Jul 14 00:54:53 2009 (4A5BC94D) 91000000 91017000 raspptp raspptp.sys Tue Jul 14 00:54:47 2009 (4A5BC947) 90c00000 90c17000 rassstp rassstp.sys Tue Jul 14 00:54:57 2009 (4A5BC951) 90d56000 90d97000 rdbss rdbss.sys Tue Jul 14 00:14:26 2009 (4A5BBFD2) 91deb000 91df5000 rdpbus rdpbus.sys Tue Jul 14 01:02:40 2009 (4A5BCB20) 8b9ca000 8b9d2000 RDPCDD RDPCDD.sys Tue Jul 14 01:01:40 2009 (4A5BCAE4) 8b9d2000 8b9da000 rdpencdd rdpencdd.sys Tue Jul 14 01:01:39 2009 (4A5BCAE3) 8b9da000 8b9e2000 rdprefmp rdprefmp.sys Tue Jul 14 01:01:41 2009 (4A5BCAE5) 8b869000 8b896000 rdyboost rdyboost.sys Tue Jul 14 00:22:02 2009 (4A5BC19A) 91fe6000 91ff9000 rspndr rspndr.sys Tue Jul 14 00:53:20 2009 (4A5BC8F0) 911d4000 911f9000 Rt86win7 Rt86win7.sys Thu Feb 26 09:04:22 2009 (49A65B16) 8b18a000 8b1b0000 SCSIPORT SCSIPORT.SYS Tue Jul 14 00:45:55 2009 (4A5BC733) a0be6000 a0bf0000 secdrv secdrv.SYS Wed Sep 13 14:18:32 2006 (45080528) 989f3000 989fa000 sncduvc sncduvc.SYS Mon May 12 04:20:30 2008 (4827B77E) 98839000 989e4e80 snp2uvc snp2uvc.sys Mon Aug 11 03:14:10 2008 (489FA072) 8b861000 8b869000 spldr spldr.sys Mon May 11 17:13:47 2009 (4A084EBB) 8b088000 8b181000 sptd sptd.sys Thu Apr 08 02:28:24 2010 (4BBD3138) a5f1a000 a5f6b000 srv srv.sys Fri Aug 27 04:31:26 2010 (4C77318E) a5e39000 a5e88000 srv2 srv2.sys Fri Aug 27 04:30:45 2010 (4C773165) 8b924000 8b945000 srvnet srvnet.sys Fri Aug 27 04:30:39 2010 (4C77315F) 989e5000 989f2180 STREAM STREAM.SYS Tue Jul 14 00:50:57 2009 (4A5BC861) 91df5000 91df6380 swenum swenum.sys Tue Jul 14 00:45:08 2009 (4A5BC704) 8b675000 8b7be000 tcpip tcpip.sys Mon Jun 14 04:36:59 2010 (4C15A3DB) a0bf0000 a0bfd000 tcpipreg tcpipreg.sys Tue Jul 14 00:54:14 2009 (4A5BC926) 8b817000 8b822000 TDI TDI.SYS Tue Jul 14 00:12:12 2009 (4A5BBF4C) 8b800000 8b817000 tdx tdx.sys Tue Jul 14 00:12:10 2009 (4A5BBF4A) 90d46000 90d56000 termdd termdd.sys Tue Jul 14 01:01:35 2009 (4A5BCADF) 990f0000 990f9000 TSDDD TSDDD.dll unavailable (00000000) 910e3000 91104000 tunnel tunnel.sys Tue Jul 14 00:54:03 2009 (4A5BC91B) 92600000 9260e000 umbus umbus.sys Tue Jul 14 00:51:38 2009 (4A5BC88A) 91f0c000 91f23000 usbccgp usbccgp.sys Tue Jul 14 00:51:31 2009 (4A5BC883) 91f23000 91f24700 USBD USBD.SYS Tue Jul 14 00:51:05 2009 (4A5BC869) 911a6000 911b5000 usbehci usbehci.sys Sat Oct 24 04:58:55 2009 (4AE27B7F) 91e1f000 91e63000 usbhub usbhub.sys Sat Oct 24 05:00:05 2009 (4AE27BC5) 91151000 9115b000 usbohci usbohci.sys Tue Jul 14 00:51:14 2009 (4A5BC872) 9115b000 911a6000 USBPORT USBPORT.SYS Tue Jul 14 00:51:13 2009 (4A5BC871) 98800000 98817000 USBSTOR USBSTOR.SYS Tue Jul 14 00:51:19 2009 (4A5BC877) 833b3000 833be000 vdrvroot vdrvroot.sys Tue Jul 14 00:46:19 2009 (4A5BC74B) 8b990000 8b99c000 vga vga.sys Tue Jul 14 00:25:50 2009 (4A5BC27E) 8b99c000 8b9bd000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:25:49 2009 (4A5BC27D) 8b7ef000 8b7f8000 vmstorfl vmstorfl.sys unavailable (00000000) 8321b000 8322f000 vodafone_K3805_z_dc_enum vodafone_K3805-z_dc_enum.sys Mon Mar 01 18:31:49 2010 (4B8C0815) 8320b000 8321b000 volmgr volmgr.sys Tue Jul 14 00:11:25 2009 (4A5BBF1D) 8b204000 8b24f000 volmgrx volmgrx.sys unavailable (00000000) 8b822000 8b861000 volsnap volsnap.sys Tue Jul 14 00:11:34 2009 (4A5BBF26) 91d2f000 91d39000 vwifibus vwifibus.sys Tue Jul 14 00:52:02 2009 (4A5BC8A2) 90d14000 90d25000 vwififlt vwififlt.sys Tue Jul 14 00:52:03 2009 (4A5BC8A3) 91e00000 91e09000 vwifimp vwifimp.sys Tue Jul 14 00:52:09 2009 (4A5BC8A9) 90d33000 90d46000 wanarp wanarp.sys Tue Jul 14 00:55:02 2009 (4A5BC956) 8b9bd000 8b9ca000 watchdog watchdog.sys Tue Jul 14 00:24:10 2009 (4A5BC21A) 8b009000 8b07a000 Wdf01000 Wdf01000.sys Tue Jul 14 00:11:36 2009 (4A5BBF28) 8b07a000 8b088000 WDFLDR WDFLDR.SYS Tue Jul 14 00:11:25 2009 (4A5BBF1D) 90cee000 90cf5000 wfplwf wfplwf.sys Tue Jul 14 00:53:51 2009 (4A5BC90F) 98e90000 990db000 win32k win32k.sys unavailable (00000000) 91d72000 91d7b000 wmiacpi wmiacpi.sys Tue Jul 14 00:19:16 2009 (4A5BC0F4) 8b181000 8b18a000 WMILIB WMILIB.SYS Tue Jul 14 00:11:22 2009 (4A5BBF1A) 91f66000 91f80000 WudfPf WudfPf.sys Tue Jul 14 00:50:13 2009 (4A5BC835) a5f6b000 a5f8b480 WUDFRd WUDFRd.sys Tue Jul 14 00:50:44 2009 (4A5BC854) Unloaded modules: a5fe5000 a5ff0000 monitor.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 a5fbf000 a5fca000 hiber_pciide Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 a5fca000 a5fd4000 hiber_msahci Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000A000 a5fd4000 a5fe5000 hiber_dumpfv Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00011000 a5fb2000 a5fbd000 monitor.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 a5fbd000 a5fbf000 MSPQM.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00002000 a5f8c000 a5f97000 hiber_pciide Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 a5f97000 a5fa1000 hiber_msahci Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000A000 a5fa1000 a5fb2000 hiber_dumpfv Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00011000 98821000 9882c000 monitor.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 a5e88000 a5ef2000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0006A000 a0b2e000 a0b46000 parport.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00018000 8b924000 8b931000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000D000 8b931000 8b93c000 dump_pciidex Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000B000 8b93c000 8b946000 dump_msahci. Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 0000A000 8b946000 8b957000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 ImageSize: 00011000 Some other things you may wish to consider:
AVG is known to be a cause of BSOD's on Windows 7 systems. If you decide or need to uninstall it: Download the correct AVG Remover for your system (32 or 64 bit).
If you have AVG ID protection installed, download the AVGID Protection Remover from the above link as well (it wouldn't hurt to download and run it anyway). Download Microsoft Security Essentials as AVG's replacement. Re-boot to Safe Mode. In Safe Mode run the AVG Removal tools. Re-boot to normal mode and install MSE. Make sure your Windows firewall is enabled!

Just to let you know. The older version of the sptd driver used by Daemon Tools is notorious for causing BSOD's on Windows 7. I'm not sure of the 2010 version you have installed though.

Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.


Page 1 of 3.
Results 1...20 of 54