New laptop, multiple BSoD

idunnoknowlol · 28 Oct 2010

Guess I might as well post and see if it can be resolved somehow... I really don't want to have to deal with mailing it back and waiting for a replacement.

-x64
-original OS
-OEM
-system is 2 days old as of now, BSODs on first day

thats about it. Thanks to anyone that can take the time to try and help me out.

wish · 29 Oct 2010

Hi,
Most your dumps file have error code 0xA (caused by memory or driver with improper address) and 0xBE (usual caused by a driver attempts to write to a read-only memory segment)

Perform memory test at least for 7 passes because you have memory corruption issue.
RAM - Test with Memtest86+

Code:

BugCheck A, {fffff683ff7ad240, 0, 0, fffff80002ce91e2}
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )

Then uninstall MCAfee and replace it with MSE because its process was involved in the crash.
(You may reinstall Mcafee later after your windows stable)

Code:

BUGCHECK_STR:  0xA
PROCESS_NAME:  mfefire.exe
TRAP_FRAME:  fffff88008a268c0 -- (.trap 0xfffff88008a268c0)

These drivers are part of Mywinlocker software. Update the drivers/software to the latest version or uninstall it.
"Note: MyWinLocker is not compatible with Acer eDataSecurity Management. Please do not install both MyWinLocker and Acer eDataSecurity on the same machine."
Encryption Software - Encryption and Decryption - Files Lock - Files Invisible - MyWinLocker

Code:

mwlPSDFilter.sys            Tue Jun 02 03:07:30 2009 
mwlPSDNServ mwlPSDNServ.sys Tue Jun 02 03:07:39 2009 
mwlPSDVDisk mwlPSDVDisk.sys Tue Jun 02 03:15:29 2009

Log

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff800022146d0, 2, 0, fffff80002c8c3d9}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+d9 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff800022146d0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c8c3d9, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb80e0
 fffff800022146d0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+d9
fffff800`02c8c3d9 483958f8        cmp     qword ptr [rax-8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9caa0 -- (.trap 0xfffff80000b9caa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800022146d8 rbx=0000000000000000 rcx=00000000000028ec
rdx=00000000000000eb rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8c3d9 rsp=fffff80000b9cc30 rbp=00000000000028eb
 r8=0000000000000000  r9=00000000000000c0 r10=00000000000000eb
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiTimerExpiration+0xd9:
fffff800`02c8c3d9 483958f8        cmp     qword ptr [rax-8],rbx ds:fffff800`022146d0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7fca9 to fffff80002c80740

STACK_TEXT:  
fffff800`00b9c958 fffff800`02c7fca9 : 00000000`0000000a fffff800`022146d0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c960 fffff800`02c7e920 : 00000000`00000000 00000000`6168fe9c fffffa80`054b0d00 fffffa80`054a5370 : nt!KiBugCheckDispatch+0x69
fffff800`00b9caa0 fffff800`02c8c3d9 : 00000000`61669d3c fffff800`00b9cc58 00000000`000028eb fffff800`02dfefe8 : nt!KiPageFault+0x260
fffff800`00b9cc30 fffff800`02c8bcb7 : 00000000`14ecc6c0 00000000`000028ec 00000000`14ecc62b 00000000`000000eb : nt!KiTimerExpiration+0xd9
fffff800`00b9ccd0 fffff800`02c88eea : fffff800`02dfae80 fffff800`02e08c40 00000000`00000000 fffff800`02da0da0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+d9
fffff800`02c8c3d9 483958f8        cmp     qword ptr [rax-8],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+d9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+d9

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+d9

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

usasma · 29 Oct 2010

If you're still getting BSOD's after following wish's suggestions, please run Driver Verifier according to these instructions. Driver Verifier works well with most STOP 0xA errors, and with some of the STOP 0x8E errors.

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

idunnoknowlol · 30 Oct 2010

First off, thank you for helping. I did all that, then tried using driver verifier... an iffy proposition indeed. Couldn't get windows to boot up without BSoD, so I run it in safe mode ( which works thank god), turn off driver verifier, try to boot and... still BSoD. This time its "critical service failed". So I'm worse off then when I started, somehow. Uploading more dump files.

What a pain in the ass this is becomming, one of these days I will learn my lesson from buying online. If I bought this locally I would have returned it that day, no questions asked.

wish · 30 Oct 2010

Hi,
All the dumps have error 0x5A (critical service failed), could be software or hardware failure.
Your system up time only about 11 seconds before crash.

So you need to repair the windows system, can be done with recovery partition or Win7 Installation Disc :
System Recovery Options
Startup Repair

Log

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 5A, {1, 1, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmBootLastKnownGood+2f )

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

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

CRITICAL_SERVICE_FAILED (5a)
Arguments:
Arg1: 0000000000000001
Arg2: 0000000000000001
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x5A

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000303600f to fffff80002cc0740

STACK_TEXT:  
fffff880`009a9698 fffff800`0303600f : 00000000`0000005a 00000000`00000001 00000000`00000001 00000000`00000000 : nt!KeBugCheckEx
fffff880`009a96a0 fffff800`030a8c71 : fffffa80`05145300 00000000`00000000 00000000`c0000034 00000000`00000002 : nt!CmBootLastKnownGood+0x2f
fffff880`009a96e0 fffff800`031edad6 : fffffa80`05145360 fffffa80`05145360 fffffa80`05145350 fffff8a0`00000028 : nt!IopLoadDriver+0xd61
fffff880`009a99b0 fffff800`031eec92 : fffff800`00000000 fffff8a0`003f9f20 ffffffff`800000c0 fffff8a0`00296cf0 : nt!IopInitializeSystemDrivers+0x1d6
fffff880`009a9a40 fffff800`031f1cec : 00000000`00000000 00000000`00000010 ffffffff`80000028 fffff800`008128c0 : nt!IoInitSystem+0x9b2
fffff880`009a9b40 fffff800`031428c9 : 00000000`00000020 fffffa80`03d13b60 00000000`00000080 fffffa80`03d13040 : nt!Phase1InitializationDiscard+0x129c
fffff880`009a9d10 fffff800`02f64c06 : 00000000`005a0070 00000000`00000080 01ca0444`806d2a1d fffff800`02c9ec19 : nt!Phase1Initialization+0x9
fffff880`009a9d40 fffff800`02c9ec26 : fffff800`02e3ae80 fffffa80`03d13b60 fffff800`02e48c40 004f0043`002e0034 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CmBootLastKnownGood+2f
fffff800`0303600f cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!CmBootLastKnownGood+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x5A_nt!CmBootLastKnownGood+2f

BUCKET_ID:  X64_0x5A_nt!CmBootLastKnownGood+2f

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