Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: It bsod'ed again after serveral weeks of woring fine

17 Oct 2010   #1

Windows Home Premium 64bit
It bsod'ed again after serveral weeks of woring fine


After serveral weeks of working fine my computer BSOD'ed again.

See this thread for the history of this problem

I didnt change anything. That is I am not running NOD32 but Microsoft security essentials.

No new hardware was installed

Please help me. Thanks in advance

My System SpecsSystem Spec
18 Oct 2010   #2

Windows Home Premium 64bit

If anyone wants to take a look, much appreciated.

Thanks in advance
My System SpecsSystem Spec
18 Oct 2010   #3

Windows 7 Ultimate 32 bit

Hi, san; sorry you are having trouble again. I will take a look.
Error code 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.
Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e43eb0
Debug session time: Sat Oct 16 06:27:14.371 2010 (GMT-4)
System Uptime: 0 days 0:25:20.526
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002f22229, 0, a0}

Probably caused by : memory_corruption

Followup: memory_corruption

3: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f22229, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 00000000000000a0, Parameter 1 of the exception

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

fffff800`02f22229 418b8c24a0000000 mov     ecx,dword ptr [r12+0A0h]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000000a0

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eae0e0




PROCESS_NAME:  svchost.exe


EXCEPTION_RECORD:  fffff88006971248 -- (.exr 0xfffff88006971248)
ExceptionAddress: fffff80002f22229 (nt!CmpFindSubKeyByNumber+0x0000000000000095)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000000a0
Attempt to read from address 00000000000000a0

TRAP_FRAME:  fffff880069712f0 -- (.trap 0xfffff880069712f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a000023010
rdx=fffff8a004e3a64c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f22229 rsp=fffff88006971480 rbp=fffff88006971630
 r8=0000000000000000  r9=fffff88006971630 r10=0000000000000005
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff800`02f22229 418b8c24a0000000 mov     ecx,dword ptr [r12+0A0h] ds:1680:00000000`000000a0=????????
Resetting default scope

LOCK_ADDRESS:  fffff80002e7a460 -- (!locks fffff80002e7a460)

Resource @ nt!PiEngineLock (0xfffff80002e7a460)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

    Lock address  : 0xfffff80002e7a460
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff80002cb6789 to fffff80002c75580

fffff880`06970a78 fffff800`02cb6789 : 00000000`0000001e ffffffff`c0000005 fffff800`02f22229 00000000`00000000 : nt!KeBugCheckEx
fffff880`06970a80 fffff800`02c74bc2 : fffff880`06971248 00000000`00000000 fffff880`069712f0 fffff8a0`04ef4b4c : nt!KiDispatchException+0x1b9
fffff880`06971110 fffff800`02c7373a : 00000000`00000000 00000000`000000a0 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`069712f0 fffff800`02f22229 : 00000000`00000000 fffff880`06971630 fffff8a0`04ef4b4c fffff8a0`00023010 : nt!KiPageFault+0x23a
fffff880`06971480 fffff800`02f227b3 : 00000000`00000000 fffff880`06971860 fffff8a0`010d3258 00000000`00000000 : nt!CmpFindSubKeyByNumber+0x95
fffff880`06971500 fffff800`02f2251d : fffff8a0`00380298 fffff880`069716b0 fffffa80`05525501 fffff8a0`00000000 : nt!CmEnumerateKey+0x173
fffff880`06971630 fffff800`02c747d3 : fffffa80`054ed040 00000000`00000000 fffffa80`00000000 fffff8a0`0c1b4680 : nt!NtEnumerateKey+0x25b
fffff880`06971770 fffff800`02c70d70 : fffff800`02ee2a79 00000000`00000000 fffff880`06971b20 fffff8a0`01149c00 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06971978 fffff800`02ee2a79 : 00000000`00000000 fffff880`06971b20 fffff8a0`01149c00 00000000`00000000 : nt!KiServiceLinkage
fffff880`06971980 fffff800`02ee3c8d : 00000000`00000002 00000000`00000000 fffff880`00000000 00000000`00000001 : nt!IopGetDeviceInterfaces+0x225
fffff880`06971af0 fffff800`02ee1aed : 00000000`00000002 00000000`00000000 00000000`00000000 fffff8a0`01149c00 : nt!PiGetInterfaceDeviceList+0x41
fffff880`06971b50 fffff800`02f172f0 : fffff8a0`01149c00 fffff800`00008000 fffff880`06971c01 fffff800`03141da0 : nt!PiControlGetInterfaceDeviceList+0x111
fffff880`06971bd0 fffff800`02c747d3 : fffffa80`057fcb60 00000000`01c7ec00 fffff880`06971ca0 00000000`01c7ec88 : nt!NtPlugPlayControl+0x100
fffff880`06971c20 00000000`774c0daa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01c7ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774c0daa


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002f22229 - nt!CmpFindSubKeyByNumber+95
    [ 48:41 ]
1 error : !nt (fffff80002f22229)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption





Followup: memory_corruption
The dump points out memory corruption. All of your drivers seem to be up to date. Let's test your RAM to make sure it is not the problem. Follow the instructions in this tutorial: RAM - Test with Memtest86+. Errors, if any, will show in red on your screen. Post your results.

If you do not get any RAM errors, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Use your computer normally while Driver Veririfier is running. Upload any dumps triggered by Driver Verifier.

If you have any questions, please ask.
My System SpecsSystem Spec

18 Oct 2010   #4

Windows Home Premium 64bit

thx I did memtest for 7 passes 0 errors came up

I will take a look at verifier
My System SpecsSystem Spec
18 Oct 2010   #5

Windows 7 Ultimate 32 bit

Very good. I think it it is conflict somewhere.
My System SpecsSystem Spec
20 Oct 2010   #6

Windows Home Premium 64bit

the BSOD happend again on start up.

This time I had verifier enabled.

Will you please take a look at the reports.

Also do I need to do anything other to show verifier reports?

Thanks in advance
My System SpecsSystem Spec
20 Oct 2010   #7

Windows Home Premium 64bit

Now my system is gotten very unstable just got another BSOD when computer was idle. Should I disable verifier?
My System SpecsSystem Spec
20 Oct 2010   #8

Windows 7 Ultimate 32 bit

Upload the BSOD. Driver Verifier will create a BSOD every time it finds a faulty driver. That is what it is supposed to do. Unfortunately, the dump you uploaded does not point to a specific driver even though it is a Driver Verifier enabled dump.

Edited to add: Since this BSOD happened during startup, that tends to indicate a hardware problem. Do you have access to another power supply unit you can try? A failing PSU can cause problems at startup.
My System SpecsSystem Spec
20 Oct 2010   #9

Windows Home Premium 64bit

Dont have another psu
My System SpecsSystem Spec
20 Oct 2010   #10

Windows 7 Ultimate 32 bit

Do you have a computer store where you can buy one and return it if it is not the power supply causing the problem?
My System SpecsSystem Spec

 It bsod'ed again after serveral weeks of woring fine

Thread Tools

Similar help and support threads
Thread Forum
BSOD playing serveral games, error 0x0000124
I have a Custom builded PC, I builded it myself and actually had this problem before. I am getting this BSOD 0x0000124 and caused by ntoskrnl.exe. My build should be able to see at my profile and I have tried alot of stuff but I would be very happy and very thankful if you could help me fix this,...
BSOD Help and Support
0x80072ee2 for weeks on some PCs while others on same network are fine
Hi, I am having problems with Windows Update on some, but not all, of the computers on my home network. All are running Windows 7 (combination of Home Premium and Ultimate). Two of the PC's have not been able connect to Windows Update since the start of July. Both are connected to the...
Windows Updates & Activation
BSOD serveral times a day, error 0x0000001e
reinstalled windows7 didn't work here's the dump file thx!
BSOD Help and Support
Two BSOD's in 2 weeks
Hi , I wasn't doing anything in particular during the crash. My first crash was on Jan 4 and earlier today (i.e-Jan 10) was the second time. The only new installation I can think of was an upgrade to Firefox 9.0.1 and Skype facebook Beta. Systems info Current: Windows 7 Pro x64 full retail...
BSOD Help and Support
installs fine, runs fine, reboots..not fine
hey guys so i finally decided to install win7 x86 - everything went well - put all the standard stuff on there etc - i rebooted many times because of installations and updates on my last reboot it just got stock in the bios screen (verifying dmi pool data..success! etc) so i rebooted, same...
Installation & Setup

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 10:21.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App