[TheRagnarok]

Ok, in desperation I did a formatted the drive with @KILLDISK.
Then I re-installed Windows 7 x64.
I DID NOT let windows update download ANY critical updates.
I let Windows Update download ONLY the drivers.
This was last night,(after it BSODd and after I posted the .dmp file).

I then ran the verifier.exe, and started up prime95 (cpu stess test).
The laptop ran stable all night.
After reading your post, I ran the Intel update utility, and it said the chipset drivers were current.
The Intel update agent only updated the outdated WiFi and LAN drivers.
I'm going to run verifier again.

[Advertisements]

I left the laptop on for about 48 hours.
It was a clean install of Windows 7 x64.
The only thing I let Windows update touch was the drivers.
I DID NOT let it install ANY critical updates.
The laptop did not Blue screen any.
The only thing that was bugging me was that the laptop seemed really sluggish.
So I installed Vista x 64 the machine and received this BSOD.
The laptop was on for about 10 minutes, then I started to hera somehing speed up (It sounded like a fan) but may have been a whirring sound.
First thought -hard drive-. But it was probably the fan speeding up right before the bsod.
The .dpm is attached.

http://www.mediafire...9u432ga4a05cka5

It might actually be the WiFi mini PCIe card failing.

Edited by TheRagnarok, 24 January 2011 - 10:42 AM.

[TheRagnarok]

I left the laptop on for about 48 hours.
It was a clean install of Windows 7 x64.
The only thing I let Windows update touch was the drivers.
I DID NOT let it install ANY critical updates.
The laptop did not Blue screen any.
The only thing that was bugging me was that the laptop seemed really sluggish.
So I installed Vista x 64 the machine and received this BSOD.
The laptop was on for about 10 minutes, then I started to hera somehing speed up (It sounded like a fan) but may have been a whirring sound.
First thought -hard drive-. But it was probably the fan speeding up right before the bsod.
The .dpm is attached.

http://www.mediafire...9u432ga4a05cka5

It might actually be the WiFi mini PCIe card failing.

Edited by TheRagnarok, 24 January 2011 - 10:42 AM.

[rshaffer61]

I'm confused as why youwould have the system running great with win7 and then downgrade it to Vista thus causing a BSOD.
If it was running great then the next step would be to start the updates on the system files using Microsoft Windows Update. You can have it update one thing at a time and try it. if no issue then do the next update till you have them all installed or find the update that is causing the issue.

[TheRagnarok]

The laptop was acting really sluggish.
And the cpu usage was really high on run32dll, the laptop just seemed really slow.
Also, I think the dvd drive in my lappy is failing.
The recovery disks would not work in my lappy. So I put my hard drive into my brothers g50vt-x1 (same laptop as mine just blue)
And the recovery disks worked fine. I almost wonder if installing Windows 7 from DVD was somehow corrupting some files as it went.
I don't really know, but I will go as far back as Winsdows XP to get this thing running (I'm in college and I need it every day).

[rshaffer61]

If your dvd drive is faulty then yes it would have a problem installing the OS.
What was the original OS on the system, XP, Vista or Win7?
That is the OS we need to work with because that is what drivers you need to have.

You say you had Win7 on it for 48 hours with no problem. The only problem was it was being sluggish which could be caused by the lack of proper updates on the system.
You then I'm guessing formatted it and installed Vista which almost immediately BSOD on you.

We need to get the original OS on it and go from there.
Making sure all updates are done so that there is no question that software or drivers are causing the issue.

[TheRagnarok]

If your dvd drive is faulty then yes it would have a problem installing the OS.
What was the original OS on the system, XP, Vista or Win7?
That is the OS we need to work with because that is what drivers you need to have.

You say you had Win7 on it for 48 hours with no problem. The only problem was it was being sluggish which could be caused by the lack of proper updates on the system.
You then I'm guessing formatted it and installed Vista which almost immediately BSOD on you.

We need to get the original OS on it and go from there.
Making sure all updates are done so that there is no question that software or drivers are causing the issue.

Before I had read your posts, I had already installed Windows 7 x64 (again).
I fully updated eveything (drivers, critical, updates, etc.)
The only thing I changed was the option in the bios for IDE sata mode (I changed it from Enhanced to Compatable)
That was last night. The laptop ran fine while installing Star Craft 2.
In the morning I shut it down and brought it to campus.
I then proceded to use the laptop for 30 mins...and BAM! BSOD, lol
I do notice that the lappy seems kinda glitchy (sounds staticy when it plays the Win7 greeting)
And whenever I move a window around it kindof moves sluggishly.
Also, the lappy seems to run slow while installing applications. (PC Wizard, Drivers)
Here is the dump (verifier was ran before it crashed)
http://www.mediafire...v7ftg3vd9dd9ict

[rshaffer61]

Run the internal Memory Doagnostic toll in windows by following the correct step HERE which most likely will be the first set of steps.



Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions

[TheRagnarok]

Run the internal Memory Doagnostic toll in windows by following the correct step HERE which most likely will be the first set of steps.



Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions

Ran the Memory Check Tool, and it found nothing.
I then proceeded to run Seagate Seatools and it showed SMART status as: OK, and a short self test also reported back as OK.
Here is the log from WinDbg of the latest minidump.


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Rueal Connell\Desktop\Minidump\012511-36878-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c94e50
Debug session time: Tue Jan 25 10:32:50.294 2011 (UTC - 5:00)
System Uptime: 0 days 0:18:18.369
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000295018, fffff8800b66b750, 0}

Probably caused by : memory_corruption

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

1: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff96000295018, Address of the instruction which caused the bugcheck
Arg3: fffff8800b66b750, 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!GreMaskBlt+acc
fffff960`00295018 0000 add byte ptr [rax],al

CONTEXT: fffff8800b66b750 -- (.cxr 0xfffff8800b66b750)
rax=00000000ffff0030 rbx=0000000000010006 rcx=fffff900c8cb2780
rdx=0000000000000034 rsi=00000000000000c7 rdi=0000000000000000
rip=fffff96000295018 rsp=fffff8800b66c120 rbp=0000000000000001
r8=000000000000008e r9=0000000000000000 r10=0000000000000004
r11=fffff8800b66c0f0 r12=fffff900c8cb2630 r13=0000000000000009
r14=0000000000000034 r15=000000000000008e
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216
win32k!GreMaskBlt+0xacc:
fffff960`00295018 0000 add byte ptr [rax],al ds:002b:00000000`ffff0030=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x3B

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff96000295018

STACK_TEXT:
fffff880`0b66c120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!GreMaskBlt+0xacc


CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
2 errors : !win32k (fffff96000295014-fffff96000295094)
fffff96000295010 41 2b d5 2b *04 24 04 02 00 00 3b c2 74 2b 49 8b A+.+.$....;.t+I.
...
fffff96000295090 00 8b 41 44 *a0 dd f7 81 60 01 00 00 00 e0 00 00 ..AD....`.......

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .cxr 0xfffff8800b66b750 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

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

[rshaffer61]

Tutorial for running chkdsk in Win 7 located HERE.

[TheRagnarok]

Another act of desperation! lol
I ran MemTest after getting home....and not even 3 minutes in 7939 Errors..
I'm going to start testing the sticks one at a time, and each in different slots.
Also, I was reading of someone have memory errors and bsods on cold boot (after comp was off for a while)
And working fine after restart. (same for me, after restart no errors)
http://forums.anandt...d.php?t=2039083
I have some DDR2 from another lappy that I might just borrow... much to the dismay of my brother, Ha!!
Lets hope it's just the ram!!!
I've prolly installed Win7 5 times and Vista once this week

Edited by TheRagnarok, 25 January 2011 - 04:01 PM.

[rshaffer61]

Everything is pointing to faulty ram and now this test shows over 7900 errors. I think the culprit has been found .
The only other explanation would be faulty memory slots on the motherboard.
At this point the less expensive of the two evils is memory to replace.

[The Admiral]

I have ran memtest and instantly received a crapload of errors, flushed contacts/pins with 99% Isopropyl Alcohol, reseated, and no errors for 3 hours.

I ran Memtest last night......and no memory errors showed up.

Ran the Memory Check Tool, and it found nothing.

I ran MemTest after getting home....and not even 3 minutes in 7939 Errors..

Well that's frustrating.... lol

Bad RAM would explain why you were having trouble getting a solid Windows installation. Or a bad mobo.

<house>So why does memtest pass sometimes and epic fail others?</house>

[rshaffer61]

So why does memtest pass sometimes and epic fail others?

A good indicator that we may be dealing with a faulty memory slot on the mobo.

[TheRagnarok]

I put two 1-gig sticks (from my ex-Dell Latitude D820), and ran MemTest for around 2 passes, all good
And there were no errors at all.
I booted into Win7 and ran DriverAgent (just to check), and I received a blue screen shortly after.
BSOD hit me not long after running DriverAgent. ALSO, the lappy still seems oddly sluggish.
Maybe the old glitchy memory corrupted my install?
Here is the dump log from WinDbg.
That doesn't look like corrupted memory to me (hopefully)
Should I load up Win7 again? Or just run sfc /scannow ?
Thanks to all, for the help and advice so far.
Also, I turned verifier off. Now there is no more sluggishness.
http://www.mediafire...k8zmmip6rin52r0


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Rueal Connell\Desktop\Minidump\012511-25443-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c56e50
Debug session time: Tue Jan 25 22:00:00.837 2011 (UTC - 5:00)
System Uptime: 0 days 0:14:03.772
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 26c, fffffa80030b8620, fffff88003815512}

Unable to load image \??\C:\Windows\SysWOW64\Drivers\DrvAgent64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for DrvAgent64.SYS
*** ERROR: Module load completed but symbols could not be loaded for DrvAgent64.SYS
Probably caused by : DrvAgent64.SYS ( DrvAgent64+2512 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 000000000000026c, Handle value being referenced.
Arg3: fffffa80030b8620, Address of the current process.
Arg4: fffff88003815512, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR: 0xc4_f6

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: driveragent.ex

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002f133dc to fffff80002a89740

STACK_TEXT:
fffff880`0208f538 fffff800`02f133dc : 00000000`000000c4 00000000`000000f6 00000000`0000026c fffffa80`030b8620 : nt!KeBugCheckEx
fffff880`0208f540 fffff800`02f28ae4 : 00000000`0000026c fffffa80`030b8620 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0208f580 fffff800`02ce4b40 : fffff880`0208f6c0 fffff880`0208f7b0 00000000`00000000 fffff980`44554f00 : nt!VfCheckUserHandle+0x1b4
fffff880`0208f660 fffff800`02d605f5 : 00000000`00000000 00000000`000f001f 00000000`00000000 fffff800`02a29900 : nt! ?? ::NNGAKEGL::`string'+0x20e2e
fffff880`0208f730 fffff800`02f28878 : fffff980`44554fe0 00000000`00000000 fffff880`0208f8d8 fffff800`02a84f30 : nt!ObReferenceObjectByHandle+0x25
fffff880`0208f780 fffff880`03815512 : 00000000`000f0000 00000000`00000000 fffff980`44554fe0 fffff880`02090000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0208f7d0 00000000`000f0000 : 00000000`00000000 fffff980`44554fe0 fffff880`02090000 fffff880`0208f840 : DrvAgent64+0x2512
fffff880`0208f7d8 00000000`00000000 : fffff980`44554fe0 fffff880`02090000 fffff880`0208f840 00000000`00000000 : 0xf0000


STACK_COMMAND: kb

FOLLOWUP_IP:
DrvAgent64+2512
fffff880`03815512 85c0 test eax,eax

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: DrvAgent64+2512

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: DrvAgent64

IMAGE_NAME: DrvAgent64.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4b26121e

FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_DrvAgent64+2512

BUCKET_ID: X64_0xc4_f6_VRF_DrvAgent64+2512

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

Edited by TheRagnarok, 25 January 2011 - 09:35 PM.

[rshaffer61]

OK I see no results from post 24
Driver Verifier is obviously causing a problem.
How is the system running other then the BSOD.
Does the BDOD happen in any other program other then Verifier right now?