BSOD 1E all the time

I am attaching my miniump files, can someone please help!!!

Roddyrex said:

I am attaching my miniump files, can someone please help!!!

Roddyrex

Hi and welcome. You have about 7 different causes. We need to start with them one at a time. Since there are so many causes it has to be hardware and I am thinking RAM.

If you are running a RAID update its drivers, If you are overclocking STOP.


The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do>

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW

2-Download a 3rd party app called memtestx86, burn it so cd, and run memtest for 5-6 passes.

3-Event viewer
There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Go to the windows log>application tab.

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.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If y our driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
Beyond that, please run Verifier with these settings:
[quote]
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users[/quote

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Seven Forums\092510-31902-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e10000 PsLoadedModuleList = 0xfffff800`0304de50
Debug session time: Sat Sep 25 00:39:30.509 2010 (GMT-4)
System Uptime: 0 days 0:00:52.304
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5992952f00e6dde0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002dfb258 -- (.exr 0xfffff88002dfb258)
ExceptionAddress: fffff80002fb3f8c (nt!ExDeferredFreePool+0x0000000000000100)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002dfb300 -- (.trap 0xfffff88002dfb300)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8000300fbc0 rbx=0000000000000000 rcx=fffff8000300fbc0
rdx=ffeffa8004537840 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fb3f8c rsp=fffff88002dfb490 rbp=0000000000000000
 r8=ffeffa8004537840  r9=0000000000000000 r10=fffffa8005c6d010
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExDeferredFreePool+0x100:
fffff800`02fb3f8c 4c8b02          mov     r8,qword ptr [rdx] ds:ffeffa80`04537840=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e79c2e to fffff80002e81ed0

STACK_TEXT:  
fffff880`02dfa338 fffff800`02e79c2e : 00000000`00000000 5acd7f25`ee5e4098 fffff880`02dfaab0 fffff800`02eaee28 : nt!KeBugCheck
fffff880`02dfa340 fffff800`02ea7bed : fffff800`0308ec24 fffff800`02fc7a3c fffff800`02e10000 fffff880`02dfb258 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02dfa370 fffff800`02eaf250 : fffff800`02fcfb5c fffff880`02dfa3e8 fffff880`02dfb258 fffff800`02e10000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02dfa3a0 fffff800`02ebc1b5 : fffff880`02dfb258 fffff880`02dfaab0 fffff880`00000000 fffffa80`05c6c4c0 : nt!RtlDispatchException+0x410
fffff880`02dfaa80 fffff800`02e81542 : fffff880`02dfb258 00000000`00000000 fffff880`02dfb300 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02dfb120 fffff800`02e7fe4a : 00000000`00000000 fffff880`02dfb390 00000000`00000000 fffffa80`04aa9000 : nt!KiExceptionDispatch+0xc2
fffff880`02dfb300 fffff800`02fb3f8c : fffffa80`0451ee70 fffffa80`0451ed02 fffffa80`04494c80 fffff800`02e68395 : nt!KiGeneralProtectionFault+0x10a
fffff880`02dfb490 fffff800`02fb54c1 : fffffa80`0451edc8 fffffa80`05e76230 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x100
fffff880`02dfb520 fffff880`0104e080 : 00000000`00000000 fffffa80`0451ed90 fffffa80`63526d73 fffff800`000002dc : nt!ExFreePoolWithTag+0x411
fffff880`02dfb5d0 fffff880`0105634c : fffffa80`0451ed90 fffffa80`05c64010 fffffa80`05e76240 00000000`00000000 : rdyboost!SmdRBReadWriteCompletion+0x20c
fffff880`02dfb650 fffff880`010561cf : fffffa80`0451ed90 fffff880`010870ca 00000000`00000000 fffffa80`00000000 : rdyboost!SmdProcessReadWriteCompletion+0x154
fffff880`02dfb6d0 fffff800`02e84516 : fffffa80`05c642db fffffa80`04522940 fffffa80`05c64010 fffffa80`05c64010 : rdyboost!SmdReadWriteCompletion+0x5f
fffff880`02dfb710 fffff880`011c18ee : 00000000`00000000 fffff800`02f34001 fffffa80`04edb0f8 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02dfb7f0 fffff800`02e84516 : 00000000`00000000 fffff800`033f2156 fffffa80`044bf860 00000000`00001000 : CLASSPNP!TransferPktComplete+0x1ce
fffff880`02dfb870 fffff880`00f8541a : 00000000`00000000 00000000`00000001 fffffa80`04edb010 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02dfb950 fffff880`00f85242 : fffffa80`04edb010 fffffa80`044bf860 00000000`00000000 fffffa80`04998601 : ataport!IdeCompleteScsiIrp+0x62
fffff880`02dfb980 fffff880`00f7fe32 : 00000000`00000000 00000000`00000000 fffffa80`04516f00 fffff800`03418c60 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`02dfb9b0 fffff880`00f887ed : fffffa80`049971a0 fffffa80`04edb010 00000000`00000000 fffffa80`04edb010 : ataport!IdeTranslateCompletedRequest+0x236
fffff880`02dfbae0 fffff880`00f880ec : fffffa80`049971a0 00000000`00000000 fffffa80`049971a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02dfbc10 fffff800`02e8d5dc : fffff880`02dd3180 00000000`089d5362 fffffa80`04997050 fffffa80`04997118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02dfbcd0 fffff800`02e8a6fa : fffff880`02dd3180 fffff880`02dddfc0 00000000`00000000 fffff880`00f87f44 : nt!KiRetireDpcList+0x1bc
fffff880`02dfbd80 00000000`00000000 : fffff880`02dfc000 fffff880`02df6000 fffff880`02dfbd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+100
fffff800`02fb3f8c 4c8b02          mov     r8,qword ptr [rdx]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nt!ExDeferredFreePool+100

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!ExDeferredFreePool+100

BUCKET_ID:  X64_0x1E_nt!ExDeferredFreePool+100

Followup: Pool_corruption
---------

Hi and thanks for the quick response. I opened the event viewer and there are several criticals!! They all have Event ID 41 and under Source they say Kernal Power. Does this help??

Roddyrex said:

Hi and thanks for the quick response. I opened the event viewer and there are several criticals!! They all have Event ID 41 and under Source they say Kernal Power. Does this help??

That one is well known and common simply means

The last sleep transition was unsuccessful. This error could be caused if the system stopped responding failed or lost power during the sleep transition.

Possibly something in the power cfg, a driver, or other things,. have you started running the tests?


ken J

Yes the test using SMD came up OK with no issues. I'm going to run the MemTest now. I'll let you know ASAP!! Thanks.

Roddyrex said:

Yes the test using SMD came up OK with no issues. I'm going to run the MemTest now. I'll let you know ASAP!! Thanks.

My pleasure. I am subscribed to this thread so any post gets me an email


ken

Memtest86 found a bad RAM stick. Lifetime warranty so I'll send it back. Thanks for your help, I will let you know how it all works out for me now.

Roddyrex said:

Memtest86 found a bad RAM stick. Lifetime warranty so I'll send it back. Thanks for your help, I will let you know how it all works out for me now.

Be sure to check the other one and the mobo slots with known good ram.

Good Luck


KJ