Solved New Lenovo - BSOD, Warrantee Replaced Motherboard, New BSOD 3 weeks

[jaidzer0]

Here's the clif notes: Got a brand new (not refurb) lenovo desktop. win 7 62 bit - blue screen all the time, random times. I'm not a gamer, i had very little installed.

Took a picture, called support with the code, they sent a guy out and he replaced my motherboard. All seemed good - for a few hours. Got two new bsod. Attached are the 2 recent minidumps and a screenshot of my specs, and that other file requested.

Hope you guys can help. I am still under warrantee and can probably raise hell and get another new machine, but it's been 3 weeks and I just want to use the thing

Thanks

 

[ePeen]

Hello, welcome to SevenForums!

Nothing shown as far as processes go, and you have a 109* critical structure corruption bugcheck for one of the two dumps, so it's most likely hardware related, usually memory of hard drive.

I would recommend running Memtest to ensure your memory isn't faulty.

Check your hard drive for any errors as well with chkdsk:

1. Open the "Computer" window
2. Right-click on the drive in question
3. Select the "Tools" tab
4. In the Error-checking area, click <Check Now>.

Drivers in need of update:

LVUSBS64.sys - LVUSBS64 Thu Oct 11 21:39:40 2007 (Logitech Camera driver). Update here.

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

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

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


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

FAULTING_IP: 
win32k!GreUpdateSpriteVisRgn+c8
fffff960`001360e8 498b5528        mov     rdx,qword ptr [r13+28h]

CONTEXT:  fffff8800a9cad00 -- (.cxr 0xfffff8800a9cad00)
rax=fbfff900c0ce84a0 rbx=fffffa8009de7bf0 rcx=040006ff3f317b48
rdx=0000000000000100 rsi=fffff900c00d20a0 rdi=0000000000000001
rip=fffff960001360e8 rsp=fffff8800a9cb6e0 rbp=fffff900c00d2280
 r8=fffff900c00d20a0  r9=0000000000000000 r10=fffff900c00d20a0
r11=fffff900c334ca80 r12=0000000000000000 r13=fbfff900c0ce84a0
r14=0000000000000004 r15=fffff900c0e00b90
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210286
win32k!GreUpdateSpriteVisRgn+0xc8:
fffff960`001360e8 498b5528        mov     rdx,qword ptr [r13+28h] ds:002b:fbfff900`c0ce84c8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001360e8

STACK_TEXT:  
fffff880`0a9cb6e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!GreUpdateSpriteVisRgn+0xc8


FOLLOWUP_IP: 
win32k!GreUpdateSpriteVisRgn+c8
fffff960`001360e8 498b5528        mov     rdx,qword ptr [r13+28h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!GreUpdateSpriteVisRgn+c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f10ff24

STACK_COMMAND:  .cxr 0xfffff8800a9cad00 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!GreUpdateSpriteVisRgn+c8

BUCKET_ID:  X64_0x3B_win32k!GreUpdateSpriteVisRgn+c8

Followup: MachineOwner

------------------------------------

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89d36f911, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 6c563354dee76e8e, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ce4c40

STACK_TEXT:  
fffff880`031cb498 00000000`00000000 : 00000000`00000109 a3a039d8`9d36f911 00000000`00000000 6c563354`dee76e8e : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

Followup: MachineOwner

 

[jaidzer0]

Ran memtest - screenshot attached

I ran the check disk on the C drive first, it came back good, then I booted from the memtest USB, I took a picture with my phone of the screen, then turned it off. I replaced the RAM with the original 4 gigs that came with the new motherboard (I had ordered brand new 8 gb with the pc) I'm running the test again now to see if I get similar errors.

Thoughts? Thanks!

 

[ePeen]

Yep... those are errors, and you don't want those. Let me know how the RAM you're testing now comes back!

 

[jaidzer0]

Well, it's 70% through the second pass with no errors. Looks like its the RAM after all. Time to call tigerdirect. Thanks for your help. Is there anything else I need to know?

 

[ePeen]

Rather than calling TigerDirect, I'd go through the manufacturer directly. Other than that, that's really all. Hopefully your new RAM gets you up and running

 

[Dave76]

OEM computer BIOS has very limited functionality, you can't adjust CPU or RAM settings.
When you order new RAM for an OEM computer you need to get the same frequency, timings, voltage settings as the original RAM that came with the desktop.

You can download CPUZ to find this information on your original RAM, or post a snip of the Memory, and SPD tabs and we can help you with the specs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Most RAM manufacturers have a website program to find the correct RAM for your system, for example:
Crucial Memory Advisor
Be sure to get the RAM from a company that has a good return policy.

Let us know if you have any questions.