Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD & corrupt database / Windows Live


  • Please log in to reply

#1
Jamila'sfilter

Jamila'sfilter

    Member

  • Member
  • PipPip
  • 57 posts
Backstory: HP Pavilion Slimline purchased Feb. 2010. Repeated BSODs in Feb. 2011; returned for repairs under warranty (Best Buy / Geek Squad); some memory was replaced. Error message: Page fault in nonpaged area.

Occasional BSODs since, but problem has suddenly worsened. Same error message appears. Currently, part of Windows Live inbox is inaccessible; intermittent "database corrupt" messages; nothing appears after date of Feb. 2011, although current items do show up in "unread messages" until they are opened, then vanish unless they were first moved to another folder.

Am running subscription Kaspersky as antivirus. Full scans show nothing.

Suggestions?

Jamila

Oops, running Windows 7
  • 0

Advertisements


#2
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Download and run this please.
Click the analyse tab.
Copy and paste the actual log results please to your reply.
http://www.resplendence.com/whocrashed

Edited by Macboatmaster, 27 July 2011 - 04:24 PM.

  • 0

#3
Jamila'sfilter

Jamila'sfilter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
Hello Macboatmaster

Thanks for your help! --Here is the log:


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: USER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Pentium® Dual-Core CPU E5200 @ 2.50GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3209879552 total
VM: 2147352576, free: 1980215296



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 7/26/2011 11:42:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072611-17612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFC0A0093DD010, 0x0, 0xFFFFF80002BFCF8C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 7/26/2011 11:42:38 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFC0A0093DD010, 0x0, 0xFFFFF80002BFCF8C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 7/25/2011 11:21:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-16021-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFA803FD10A40, 0x0, 0xFFFFF80002AF92A9, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 7/25/2011 10:31:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-16411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B810D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 7/25/2011 2:42:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072511-17799-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B81040, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 7/25/2011 1:07:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072411-17128-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B81070, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/24/2011 7:53:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072411-21824-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B81070, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/24/2011 7:30:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072411-18766-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFC0A001B30F90, 0x0, 0xFFFFF80002DCBBD2, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/24/2011 6:50:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072411-18704-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B810D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/24/2011 3:36:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072411-19016-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFCA00AB8925C, 0x0, 0xFFFFF80002D4D74D, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/24/2011 3:29:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072411-19609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFC0A0022808C0, 0x0, 0xFFFFF80002C08F8C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 7/24/2011 2:52:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072411-19234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF40002C7B048, 0x1, 0xFFFFF80002D54916, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/9/2011 8:27:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070911-17206-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFC0A00BEC4508, 0x1, 0xFFFFF88001113920, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 7/9/2011 12:12:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070911-16754-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A4AB40, 0xFFFFF88005F13090, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 6/20/2011 9:56:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062011-17409-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4FA9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001017FA9, 0xFFFFF880057C3970, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

51 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

klif.sys (Klif Mini-Filter [fre_wlh_AMD64], Kaspersky Lab)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
  • 0

#4
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts

Am running subscription Kaspersky as antivirus. Full scans show nothing.


Were you running this when the first set of problems occurred and please confirm that you do NOT have two security programs running.
By that I mean do you have ANYTHING else besides Kaspersky.
  • 0

#5
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Further to the above, I am signing off as it is 0057 here in UK.
Please see this and work your way through the suggestions.
http://answers.micro...b4-6305c0fc5c3b
My advice if you DID have Kaspersky when this first started would be to start with the uninstall and the use of the removal tool for Kaspersky and then install Microsoft Security Essentials.
http://www.microsoft...ls/default.aspx
You can always go back of course to Kaspersky if that proves NOT to be the cause.

Edited by Macboatmaster, 27 July 2011 - 06:00 PM.

  • 0

#6
Jamila'sfilter

Jamila'sfilter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
Yes, I purchased Kaspersky with the computer and have always run that. I used to have some Geek Squad-recommended programs as well. But I removed those many months ago.
  • 0

#7
Jamila'sfilter

Jamila'sfilter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
You are suggesting that I uninstall Kaspersky, correct?

Do you anticipate this will resolve the issue with my missing inbox messages in Windows Live?

Also, Windows Live is now crashing consistently shortly after opening.

P.S. - I am in the U.S., Eastern time zone. I will check this post periodically again tomorrow.

~Many thanks

Jamila

Edited by Jamila'sfilter, 27 July 2011 - 06:48 PM.

  • 0

#8
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Unfortunately I do not know the answer for certain, but have you read the link I sent you.
I am sure that is your first step.
  • 0

#9
Jamila'sfilter

Jamila'sfilter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
Yes, I have read the link. To summarize, you recommend:
1) Uninstall Kaspersky
2) Install MSE and Prevx OR Avast and Prevx

Correct? Do I need to install anything else?

Note: I use Firefox almost exclusively as my browser

Also note: I didn't run any malware scans before opening this post, as I didn't know what would conflict with Kaspersky and was told not to use anything else while it was loaded. Please let me know if I should run any other kind of diagnostic scan before uninstalling Kaspersky.

Other current details: On computer startup, I get the message "unable to connect to Group Policy Client Service." Windows Live crashes each time I open the program. I get BSOD consistently when shutting down.

FYI, I am fairly knowledgeable but not totally techie.

Many thanks,
Jamila
  • 0

#10
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
The crash analysis from Who Crashed indicates that one of the problems maybe
A third party driver has been identified to be causing system crashes on your computer.

klif.sys (Klif Mini-Filter [fre_wlh_AMD64], Kaspersky Lab


This is the matter dealt with in the link I sent. I can only repeat, that on the evidence at this time, I would proceed as per the link.

Here is another link which basically states the same.
http://www.sevenforu...oskrnl-exe.html

I cannot assure you that this will solve the problem, but I really cannot understand your hesitation, as if it does not, you can simply reinstall Kaspersky and we can explore further with other analysis tools.

Edited by Macboatmaster, 29 July 2011 - 07:38 AM.

  • 0

Advertisements


#11
Jamila'sfilter

Jamila'sfilter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
Hello Macboatmaster

Not hesitant; I am working full-time and also traveling on this weekend, and some of this is a matter of time for me. I will post back after I have completed these steps.

Thank you

Jamila
  • 0

#12
Jamila'sfilter

Jamila'sfilter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I have uninstalled Kaspersky and installed MSE. Install was completed about three hours ago. No BSOD since then.

Windows Live is no longer crashing. However, six months of inbox listings are missing. Also, this problem continues:

I can import new emails (from Yahoo account), and they show up in "unread e-mail." Intermittently, new e-mails also will show up in the inbox. However, when I open them, they vanish from the inbox and also of course from unread e-mails, and I can't locate them in Windows Live.

I can still access them via my Yahoo account.

Error message on attempt to install PrevX beta edition/Webroot Cloud AntiVirus:
Webroot could not be installed. This could potentially be caused by malware on the computer. Would you like to try installing with a randomized filename?

Edited by Jamila'sfilter, 31 July 2011 - 03:49 PM.

  • 0

#13
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts

Error message on attempt to install PrevX beta edition/Webroot Cloud AntiVirus:


But you do NOT want to install it as you have MSE.
The only items you could do well to have with that is Malwarebytes - free edition as a periodic scan, to verify the scan with MSE and SuperAntiSpyware as a periodic scan.
See this link for site links to those and recommendations.
http://www.geekstogo...yware-software/


NOTE

PrevX beta

NEVER NEVER install Beta editions on your main computer. They are released by companies ONLY for more extensive testing amongst the general user community.
They are NOT for general use.
From the PrevX Forum
This beta phase is on a first-come-first-serve basis. We're opening it up initially to a small group of users and will then close it so sign up fast :) There will be another round of beta testing after and we'll be introducing new features along the way. We request that in this round of beta testing, you send your reports/feedback directly to us via our dedicated beta feedback system - http://info.webrootc...ce=WEBROOTPBETA rather than post them publicly as it is still considered a "closed" beta.

And the general information on Beta Software
After an initial round of in-house testing, software publishers often release new programs to be tested by the public. These pre-release versions are called beta software, usually denoted by a "b" in the version number, e.g., Firefox 3.1b2. Since the publisher cannot possibly test the software under all possible conditions, it is reasonable to expect that wider use of the software may uncover problems that were not discovered during in-house testing. The publisher expects to be notified when users find such problems so that the program can be fixed before its official release.

In general, you should expect to run into bugs whenever using any piece of beta software. These bugs may range in severity, from minor features that don't work to problems that cause your computer to crash. Before choosing to use a piece of beta software, you should decide whether the benefit of new features in a beta program outweighs the risk of program instability.

Edited by Macboatmaster, 31 July 2011 - 04:01 PM.

  • 0

#14
Jamila'sfilter

Jamila'sfilter

    Member

  • Topic Starter
  • Member
  • PipPip
  • 57 posts
I did not install. If I need to install a version of Prevx, please point me to the appropriate link, as I was unable to find a version that I could download and launch.
  • 0

#15
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
I cannot follow your reasoning, you would have installed it if it had worked.
The point I am making is that you do not need it, NOR indeed do you WANT it. because you have MSE and you do NOT want another anti-virus program running in real time.

However more importantly please see my suggestion re the emails
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP