BSOD on my brand new computer. Pulling my hair out!!!!

#21
Thanks for the advice :). So you would really recommend getting a new wireless adapter then? What exactly do you mean by memory corruption? Is there something wrong with my ram? I have run memtest86 like 4 times up to 13 passes with no errors. At this point would you recommend a clean install of windows a new wireless adapter and lose mccafee? Is windows firewall safe? Is there another software you might recommend for virus protection and stuff?

Thanks for your help man!
 


#22
Duh, I just realized what mse was. Will that be enough?
 


#23
Thanks for the advice :). So you would really recommend getting a new wireless adapter then? What exactly do you mean by memory corruption? Is there something wrong with my ram? I have run memtest86 like 4 times up to 13 passes with no errors. At this point would you recommend a clean install of windows a new wireless adapter and lose mccafee? Is windows firewall safe? Is there another software you might recommend for virus protection and stuff?

Thanks for your help man!
well when debugger suggests memory corruption it can be a multitude of reasons which we would need to debug with some stress tests such as hardware error where the ram is faulty or the voltage supplied is insufficient or the motherboard memory controller may be "mishandling" the ram or the systems PSU is dropping the voltage too low, or software is corrupting data etc and memtest passes are a good indicator but not a definitive test as it never quite stresses ram like an Operating System can :eek:

I suggested removing Mcafee and running MSE with windows firewall as they are less or none intrusive, and I haven't seen any bluescreen crashes with their use ?

one step at a time is the way to debug issues ?

Bluescreen crashes are quite unnerving but are actually windows way of protecting your system so although they are very inconvenient they are rarely as fatal as they look :p
 


#24
Ok, I will give MSE a shot. Sucks not to be able to use a service I've paid for though. Still though, would you recommend a clean install of windows and a new wifi adapter? Any recommendation for a good compatable wifi USB adapter?
 


Last edited:
#25
let's see if the wifi adapter and removing Mcafee makes a difference ?

remember we have no real proof these things are the cause so you will be able to use Mcafee again if we prove the bluescreens are caused by something else :eek:

please post anymore problems so we can take the next step :)
 


#26
Alrighty then... I basically wiped out everything and started with a clean slate. I got a new USB Wi-fi adapter that is Windows 7 'compatible'. I re-installed Windows 7 as well. I have got 3 BSOD crashes since redoing all this. The first two came when I was opening Lavalys Everest Ultimate. The computer just crashed and bam... BSOD. This last one cam when I was about to install DXSETUP.exe which is a Direct 10 component I believe.
 


Attachments

#27
interestingly enough the first two crashes named kerneld.amd64 as the faulting driver = everest ultimate_build_1954
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000096, fffff880071e53d6, fffff88008b55c80, 0}

Probably caused by : kerneld.amd64 ( kerneld+13d6 )

Followup: MachineOwner
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: fffff880071e53d6, Address of the instruction which caused the bugcheck
Arg3: fffff88008b55c80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.

FAULTING_IP:
kerneld+13d6
fffff880`071e53d6 0f32 rdmsr

CONTEXT: fffff88008b55c80 -- (.cxr 0xfffff88008b55c80)
rax=000000008010204c rbx=fffffa800887b8c0 rcx=00000000000000ee
rdx=fffffa80082c15f0 rsi=fffffa80082c15f0 rdi=fffffa80082c15f0
rip=fffff880071e53d6 rsp=fffff88008b56660 rbp=000000000000000c
r8=fffffa8007152e70 r9=000000000000000e r10=fffff80002c519a0
r11=fffffa800887b8c0 r12=000000000000000c r13=0000000000000001
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
kerneld+0x13d6:
fffff880`071e53d6 0f32 rdmsr
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: everest.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880071e53d6

STACK_TEXT:
fffff880`08b56660 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kerneld+0x13d6


FOLLOWUP_IP:
kerneld+13d6
fffff880`071e53d6 0f32 rdmsr

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: kerneld+13d6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: kerneld

IMAGE_NAME: kerneld.amd64

DEBUG_FLR_IMAGE_TIMESTAMP: 47119e9f

STACK_COMMAND: .cxr 0xfffff88008b55c80 ; kb

FAILURE_BUCKET_ID: X64_0x3B_kerneld+13d6

BUCKET_ID: X64_0x3B_kerneld+13d6

Followup: MachineOwner
---------

0: kd> lmvm kerneld
start end module name
fffff880`071e4000 fffff880`071ec000 kerneld T (no symbols)
Loaded symbol image file: kerneld.amd64
Image path: \??\C:\Program Files (x86)\Lavalys\EVEREST Ultimate Edition\kerneld.amd64
Image name: kerneld.amd64
Timestamp: Sun Oct 14 05:44:15 2007 (47119E9F)
CheckSum: 00005B15
ImageSize: 00008000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
you need to remove Everest as the timestamp 2007 is too old, pre-dating windows 7 and is named as causing your crashes

the third .dmp file and crash is a 0xc2 BAD_POOL_CALLER but unfortunately a driver isn't named.

I suggest unninstall everest and wait for another crash but we may have caught it :eek:

I am beginning to believe you have had more than one problem causing multiple crashes and we are working down the list :p

please DO NOT install anything else unless absolutely necessary until we are confident you are crash free :razz:

also please look through event viewer to see if there are anymore clues :)
 


#28
Well yes, I did remove that version of Everest and installed a newer version with no problem and no crash. I am in the process of installing my programs all over again. Hopefully with success. I also did not install McAfee and got the MSE you recommended. I will surely keep you updated sir :)
 


#29
also if your tempted to use Utorrent I think you might be better advised using BitTorrent ;)
 


#30
hmm... I use utorrent as a matter of fact and I love it. Can I ask why you would recommend BitTorrent over utorrent?
 


#31
hmm... I use utorrent as a matter of fact and I love it. Can I ask why you would recommend BitTorrent over utorrent?
Utorrent is causing crashes on some windows 7 computers where it crashes the wifi adapter, and this might also explain;- the the third .dmp file and crash is a 0xc2 BAD_POOL_CALLER but unfortunately a driver isn't named. ?

I also love Utorrent but I would still ditch it if I suspected it was causing bluescreen crashes :eek:
 


#32
I knew it was too good to be true. I almost went a entire day without crashing but just before I was gonna go to sleep it happened again. Here is the latest. Wasn't doing anything special, just minimizing a folder to open a new one.
 


Attachments

#33
I knew it was too good to be true. I almost went a entire day without crashing but just before I was gonna go to sleep it happened again. Here is the latest. Wasn't doing anything special, just minimizing a folder to open a new one.
debugger firmly lays the blame on memory corruption
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002ec11a7, 1, 23883}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ec11a7, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000023883, 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.

FAULTING_IP:
nt!KeInitThread+9f
fffff800`02ec11a7 ff8983380200 dec dword ptr [rcx+23883h]

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000023883

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebd0e0
0000000000023883

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

BUGCHECK_STR: 0x1E_c0000005

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880073048c0 -- (.trap 0xfffff880073048c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80070262a0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec11a7 rsp=fffff88007304a58 rbp=fffffa80082ea060
r8=fffff80002f52040 r9=0000000000000000 r10=fffffa8008519970
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeInitThread+0x9f:
fffff800`02ec11a7 ff8983380200 dec dword ptr [rcx+23883h] ds:a060:00000000`00023883=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cc6a17 to fffff80002c86f00

STACK_TEXT:
fffff880`07304038 fffff800`02cc6a17 : 00000000`0000001e ffffffff`c0000005 fffff800`02ec11a7 00000000`00000001 : nt!KeBugCheckEx
fffff880`07304040 fffff800`02c86542 : fffff880`07304818 fffffa80`07026060 fffff880`073048c0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`073046e0 fffff800`02c850ba : 00000000`00000001 fffffa80`07026060 00000000`0ad20000 fffffa80`057c3860 : nt!KiExceptionDispatch+0xc2
fffff880`073048c0 fffff800`02ec11a7 : 00000000`00000000 00000000`00000000 00000000`0ad20000 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`07304a58 00000000`00000000 : fffff800`02f4f573 fffffa80`07026060 00000000`00001000 00000000`07020000 : nt!KeInitThread+0x9f


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
13 errors : !nt (fffff80002ec1187-fffff80002ec127f)
fffff80002ec1180 e0 fe 0b c1 89 83 00 *00 00 00 83 8b 00 01 00 00 ................
fffff80002ec1190 40 83 4b 4c 01 48 8d *00 50 48 89 8b 30 02 00 00 @.KL.H..PH..0...
fffff80002ec11a0 48 8d 83 40 02 00 00 *ff 89 83 38 02 00 00 48 *ff [email protected]
fffff80002ec11b0 49 08 48 89 09 48 8d *20 60 48 89 40 08 48 89 00 I.H..H. `[email protected]
...
fffff80002ec1240 be ff ff 8b c8 49 d3 *e5 4c 33 c8 4d 89 4a 30 *00 .....I..L3.M.J0.
fffff80002ec1250 8d 93 98 01 00 00 b8 *00 01 00 00 66 89 42 28 *00 ...........f.B(.
fffff80002ec1260 42 2a 01 c6 42 2b 02 *00 8d 4a 08 48 8b 01 48 *00 B*..B+...J.H..H.
fffff80002ec1270 02 48 89 4a 08 48 89 *00 08 48 89 11 48 83 a3 *00 .H.J.H...H..H...

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------
which suggests to me you may either have a bad stick or the voltage it's supplied is too low or unstable or it's not quite connecting in the slot or your memory controller (northbridge chipset) is faulty or low voltage or unstable ?

I doubt it's your Power Supply unless it's old and you have any reason to suspect it ?

you need to check what voltage your ram and northbridge chipset are being given by your motherboard so you need to check that in your bios ?

your RAM is on the Asustek qualified vendors list View attachment P6X58D Premium Memory QVL.pdf and is supposed to be running at 1.65v ?

to debug this I suggest take out all of the ram sticks and blow any dust or contamination out of the slots then place one stick only in the first slot and run your system for a day or two with just one stick and wait for a crash ?

It could still be a driver but debugger would normally have caught that and named it in the crash dump ?

did you remove Utorrent ?
 


Last edited:

jcgriff2

Extraordinary Member
Microsoft MVP
#34
Bugcheck 0x1e (0xc0000005,,,) = kernel mode exception; the exception = 0xc0000005 = memory access violation.

What anti-virus / firewall package do you have installed?

Run the driver verifier --> Tech Support Forum - View Single Post - Windows Has Recovered From Unexpected Shutdown - Blue Screen of Death - BSOD

Wait for system to BSOD; get the dump and attach it along with an msinfo32 NFO file -
START | type msinfo32 | save w/ default file ext

Regards. . .

jcgriff2

.
 


#35
Thanks for the replies. First I am going to start by increasing my QPI/DRAM voltage. A few others I talked to suggested this as well. So I will start there. If tha fails I will resort to some of the other methods mentioned.

I am strictly running Microsoft Security Essentials now and have not yet removed utorrent but I haven't used it either.
 


#36
Ok, well it seems most if not all my BSOD are gone since I've somewhat stabalized my RAM. Right now all the RAM settings are on auto except for my QPI/DRAM voltage which I'm running manual @ 1.2500v with auto clocks of 9-9-9-24. I've been able to pass Prime95 and LinX. My RAM is designed to run with clocks of 8-8-8-24 but I haven't been able to tihten them down to those settings with any real success. Any suggestions? Thanks again for all the help here and if anymore problems should arise I know where to come :)
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.