[SOLVED] BSODs started - Windows 7 x64

M

Mr T

Member
Joined
Jun 19, 2014
Posts
21
Last week my PC started crashing. When I restarted chkdsk reported a lot of drive errors. I fixed them but it was still crashing frequently. I decided to do a full restore to a new hard disk so went to a backup from two weeks previously when the pc was working.

After reboot I ran chkdsk (no errors) sfc 2 errors both fixed, ran again no errors. PC seemed OK. It tried to install Windows updates but I got a message saying it couldn't. Also strange intermittent messages from A/V (ESET) saying A/V was disabled (it wasn't, I checked).

I thought I was OK, but it's started crashing again. Once on boot, other times when running

I scanned the PC for malware with ESET and MBAM - none found

· OS - Windows 7, fully updated x64
· What was original installed OS on system this
· Is the OS an OEM version
· Age of system 18 months
· Age of OS installation 18 months

· CPU INTEL i7-2600 QUAD CORE
· Video Card Intel (integrated) HD Graphics 3000
· MotherBoard ASUS P8Z77-V LX
· Power Supply - Tagan 1200w
· System Manufacturer Clone

· Desktop

Thank you for any help, I'm much obliged
 
Hi,

We have various bug checks:

MEMORY_MANAGEMENT (1a)

This indicates that a severe memory management error occurred.

Code: 
BugCheck 1A, {[COLOR=#ff0000]41790[/COLOR], fffffa80069a7bb0, ffff, 0}

- The 1st parameter of the bug check is 41790 which indicates a page table page has been corrupted.
Code: 
1: kd> dt nt!_MMPFN fffffa80069a7bb0
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`400000b8 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`400000b8 Void
   +0x010 Lock             : 0n1073742008
   +0x010 PteLong          : 0xfffff6fb`400000b8
   +0x018 u3               : <unnamed-tag>
[COLOR=#ff0000]   +0x01c UsedPageTableEntries : 0xffff[/COLOR]
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

UnusedPageTableEntries has fallen below zero, therefore this is being caused by a driver causing memory corruption.

BAD_POOL_CALLER (c2)

This indicates that the current thread is making a bad pool request.

Code: 
4: kd> k
Child-SP          RetAddr           Call Site
fffff880`039935f8 fffff800`04f1d4ec nt!KeBugCheckEx
fffff880`03993600 fffff800`04f1de9e nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`03993640 fffff800`04f2eba8 nt!ExAllocatePoolSanityChecks+0x3e
fffff880`03993680 fffff800`04f2f01d nt!VeAllocatePoolWithTagPriority+0x88
fffff880`039936f0 fffff880`01fd4701 nt!VerifierExAllocatePoolEx+0x1d
fffff880`03993730 fffff880`039937e0 [COLOR=#ff0000]snapman+0x1c701[/COLOR]
fffff880`03993738 00000000`00100008 0xfffff880`039937e0
fffff880`03993740 00000000`00000000 0x100008

snapman.sys is the Acronis True Image Snapshot Manager driver also included in Seagate DiscWizard. It's attempting to allocate pool with a tag of zero, which makes the pool untrackable and corrupts pre-existing tag tables. It appears to be causing file system conflicts because the next bug check is...

NTFS_FILE_SYSTEM (24)

This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.


Uninstall Acronis True Image ASAP.

Regards,

Patrick
 
My pleasure.

Not for now, no. Now we wait and see if the crashes have stopped.

Please keep me updated.

Regards,

Patrick
 
Still working well :rofl12:

Thank you.

Where's the best place to learn about fixing Kernel mode problems?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top