I have been getting blue screen and reboots often. I have a stock gateway 1803u laptop. Can someone help analyze my dump file? Thank you, Pat

you can access my zipped dump files (Dump-2) at http://cid-bd1360dedc62cf56.skydrive.live.com/browse.aspx/.Public?uc=1

Also, I already did a memory check through Windows 7 64 on boot up, and no problems were found.

Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION The SYSTEM_SERVICE_EXCEPTION bug check has a value of 0x0000003B. This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code. Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced. Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM). You've a memory corruption. Please check your RAM for errors. "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Make sure to let the memory diagnostic run multiple passes. If that didn't find anything, you may have a bad driver on your machine that's corrupting memory.The fastest way to track this down is to use a testing tool called Driver Verifier.If this tool finds a problem, your machine will crash again. Hopefully with it enabled, it will allow you to easily identify the bad driver.Enable driver verifier1) Open an elevated command prompt2) Type "verifier /standard /all" (no quotes)3) Reboot your machine4) Use machine again until it crashes (hopefully this will be fast :)After the crash & reboot, go into safe mode. http://windowshelp.microsoft.com/Windows/en-US/Help/323ef48f-7b93-4079-a48a-5c58eec904a11033.mspxDisable driver verifier1) Open an elevated command prompt2) Type "verifier /reset" (no quotes)3) Reboot your machineThen using the steps you followed before, post the dumps to your skydrive share.Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

Hello Patrice6, First of all, remove all unnecessary hardware devices from the computer, try entering Windows safe mode to test whether it is a third-party software/hardware compatibility issue. If so, please download and run Windows 7 Upgrade Advisor to check the reason for the issue. If the issue is caused by some incompatible driver, you might go to Device Manager, right click your hardware device in the list and select Update Driver Software; then click Search automatically for updated driver software. If you still get the BSOD error after installing the latest driver, please understand that Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services). The system goes to a blue screen because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are). To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers. I hope the problem will be resolved soon. Thanks! Andy

I'm not an expert on this and I ran your file through the debugging tool and got the output below (I'm including the verbose output in case someone can assist in more detail). From what I understand the offending piece is "NETw5s64.sys" which appears to be a wireless (WiFi) network driver. You can Bing that filename and see what other people have done to resolve it. I don't have anything but generic advice to make sure your BIOS and drivers are current. There may be a more current update from the manufacturer.~~~Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64Copyright (c) Microsoft Corporation. All rights reserved. ******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck A, {fffff80002da9428, 2, 8, fffff80002da9428} Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for NETw5s64.sys*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sysProbably caused by : NETw5s64.sys ( NETw5s64+222404 ) Followup: MachineOwner--------- kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** IRQL_NOT_LESS_OR_EQUAL (a)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If a kernel debugger is available get the stack backtrace.Arguments:Arg1: fffff80002da9428, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000008, 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: fffff80002da9428, address which referenced memory Debugging Details:------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb50e0 fffff80002da9428 CURRENT_IRQL: 2 FAULTING_IP: nt! ?? ::NNGAKEGL::`string'+221ffffff800`02da9428 55 push rbp CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880038be220 -- (.trap 0xfffff880038be220)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000rdx=fffff88005675000 rsi=0000000000000000 rdi=0000000000000000rip=fffff88005897404 rsp=fffff880038be3b0 rbp=000000000000003e r8=0000000000000000 r9=0000000000004096 r10=0000000000000006r11=000000002aec8d98 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncNETw5s64+0x222404:fffff880`05897404 ?? ???Resetting default scope EXCEPTION_RECORD: fffff880038be178 -- (.exr 0xfffff880038be178)ExceptionAddress: fffff88005897404 (NETw5s64+0x0000000000222404) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000NumberParameters: 0 LAST_CONTROL_TRANSFER: from fffff80002a7e469 to fffff80002a7ef00 FAILED_INSTRUCTION_ADDRESS: nt! ?? ::NNGAKEGL::`string'+221ffffff800`02da9428 55 push rbp STACK_TEXT: fffff880`038bcf38 fffff800`02a7e469 : 00000000`0000000a fffff800`02da9428 00000000`00000002 00000000`00000008 : nt!KeBugCheckExfffff880`038bcf40 fffff800`02a7d0e0 : fffffa80`027d3580 fffff800`02bdff3c 00000000`00000000 fffffa80`02809e60 : nt!KiBugCheckDispatch+0x69fffff880`038bd080 fffff800`02da9428 : fffff800`02aad4dc 00000000`0000003c 00000000`00000000 fffffa80`02264000 : nt!KiPageFault+0x260fffff880`038bd218 fffff800`02aad4dc : 00000000`0000003c 00000000`00000000 fffffa80`02264000 fffffa80`027c7920 : nt! ?? ::NNGAKEGL::`string'+0x221ffffff880`038bd220 fffff800`02aa4bed : fffff800`02bdff30 fffff880`038bed00 00000000`00000000 fffff800`02a0d000 : nt!_C_specific_handler+0x8cfffff880`038bd290 fffff800`02aac250 : fffff800`02bdff30 fffff880`038bd308 fffff880`038be178 fffff800`02a0d000 : nt!RtlpExecuteHandlerForException+0xdfffff880`038bd2c0 fffff800`02ab91b5 : fffff880`038be178 fffff880`038bd9d0 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410fffff880`038bd9a0 fffff800`02a7e542 : fffff880`038be178 fffffa80`03211e60 fffff880`038be220 fffffa80`03bdd0ee : nt!KiDispatchException+0x135fffff880`038be040 fffff800`02a7c69f : fffff880`038be220 fffffa80`02691702 fffffa80`02691700 00000000`00000000 : nt!KiExceptionDispatch+0xc2fffff880`038be220 fffff880`05897404 : fffffa80`03186ef0 00000000`00000000 fffffa80`03211908 00000000`00000001 : nt!KiInvalidOpcodeFault+0x11ffffff880`038be3b0 fffffa80`03186ef0 : 00000000`00000000 fffffa80`03211908 00000000`00000001 fffffa80`01f021f8 : NETw5s64+0x222404fffff880`038be3b8 00000000`00000000 : fffffa80`03211908 00000000`00000001 fffffa80`01f021f8 00000000`00000080 : 0xfffffa80`03186ef0 STACK_COMMAND: kb FOLLOWUP_IP: NETw5s64+222404fffff880`05897404 ?? ??? SYMBOL_STACK_INDEX: a SYMBOL_NAME: NETw5s64+222404 FOLLOWUP_NAME: MachineOwner MODULE_NAME: NETw5s64 IMAGE_NAME: NETw5s64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4aafedb7 FAILURE_BUCKET_ID: X64_0xA_CODE_AV_BAD_IP_NETw5s64+222404 BUCKET_ID: X64_0xA_CODE_AV_BAD_IP_NETw5s64+222404 Followup: MachineOwner---------

thank you to everyone that commented. feel free to give further advice after my update below. -I ran scandisk and it came up with no errors. -I ran memcheck86 again, and it detected no errors after 9 passes. When I analyzed my memory.dmp file, it pointed to a problem with dxgmms1.sys, and as some of you pointed out, this deals with the video driver. So one major thing I did was install the latest driver from the mainboard manufacturer (Intel), which was more recent than the driver from the laptop manufacturer (Gateway). It did blue screen once at some point after installing the latest driver, but then I uninstalled the drivers completely (i.e., with deletion of driver), and installed this latest driver as the base driver (not layering on top as I had done previously). PNutts-I didn't see that in my dump analysis but thanks, and I went ahead and installed the latest wirelss (Intel 5100) driver from their website also. Mark - I did set it up to run verify, but it couldn't get it to crash. One thing I had noticed upon crashes was that it often happened during a lot of file transfers (the sata driver is up to date with Gateway's latest driver for that), so I also played a couple of movies and transferred some large files over winscp to see if i could help along the halt. Nothing so far, and I have turned off the verify because it was running the cpu at 100% and I need to work on some school work. I'm really hoping the updated video driver did it, now let's see what happens over the next bit of time. If it happens again I might try installing 32 bit Windows 7, or just concede that it's the onboard video and just return the unit. This has been a drain on time. Alas, Is there anything problematic with running 64 bit Windows 7 with 2gb of memory (my system's specs)? Pat

I'm not an expert on this and I ran your file through the debugging tool and got the output below (I'm including the verbose output in case someone can assist in more detail). From what I understand the offending piece is "NETw5s64.sys" which appears to be a wireless (WiFi) network driver. You can Bing that filename and see what other people have done to resolve it. I don't have anything but generic advice to make sure your BIOS and drivers are current. There may be a more current update from the manufacturer. PNutts - In this case, the crashes in the dumps were in a variety of components (uh...at least if I'm remembering correctly; I looked at a big batch of dump files last night). It MIGHT be that wifi driver, and trying to find an updated version probably wouldn't be a bad idea, but it could just be an innocent victim in this case.Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

Mark - I did set it up to run verify, but it couldn't get it to crash. One thing I had noticed upon crashes was that it often happened during a lot of file transfers (the sata driver is up to date with Gateway's latest driver for that), so I also played a couple of movies and transferred some large files over winscp to see if i could help along the halt. Nothing so far, and I have turned off the verify because it was running the cpu at 100% and I need to work on some school work. I'm really hoping the updated video driver did it, now let's see what happens over the next bit of time. If it happens again I might try installing 32 bit Windows 7, or just concede that it's the onboard video and just return the unit. This has been a drain on time. Alas, Is there anything problematic with running 64 bit Windows 7 with 2gb of memory (my system's specs)? There's no concrete evidence here that it's video-related. As far as I know, it's fine to run 64-bit Windows on a machine w/ 2GB of RAM (I was doing that on my work laptop for a while).Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

"There's no concrete evidence here that it's video related." Did you catch this part of my post: "When I analyzed my memory.dmp file, it pointed to a problem with dxgmms1.sys"

"There's no concrete evidence here that it's video related." Did you catch this part of my post: "When I analyzed my memory.dmp file, it pointed to a problem with dxgmms1.sys" You provided several dump files. Not all of them were pointing to that same file. That's why I didn't think it was solid evidence of a video issue.In one of the crashes above, it points to the wifi driver. In another crash, it pointed to the onboard net driver. Random crashes like this make me suspect hardware issues or a bad driver corrupting memory.Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

i just got another blue screen. I had just a few minutes ago turned on aero, and I was playing a movie. For what it's worth the fan was going non-stop. Upon boot up I loaded the C:\Windows\Memory.dmp into WinDbg and it said the following (below). Notice the complaint about the ntkrnlmp.exe. I have uploaded the dump file just from this latest blue screen on the skydrive. (the file is at http://cid-bd1360dedc62cf56.skydrive.live.com/self.aspx/.Public/122509-59857-01.dmp) Any further help appreciated on root causing this. Pat Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: symsrv*symsrv.dll*f:\localsymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 UP Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50 Debug session time: Fri Dec 25 05:29:59.291 2009 (GMT-5) System Uptime: 0 days 4:58:35.132 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c000001d, fffff80002a79845, fffff88006c4ac10, 0} PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 000007ff`fffdf018). Type ".hh dbgerr001" for details Probably caused by : ntkrnlmp.exe ( nt!SepNormalAccessCheck+265 ) Followup: MachineOwner

just a quick amendment to the above post, I put the recent "minidump" into the debugger and it came up with the below. It is referring to memory corruption. Since I have already extensively tested out the memory, should I at least try different memory? I am already ready to send this back, but would love to solve it. Pat Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\122509-59857-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: symsrv*symsrv.dll*f:\localsymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 UP Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c3ee50 Debug session time: Fri Dec 25 05:29:59.291 2009 (GMT-5) System Uptime: 0 days 4:58:35.132 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c000001d, fffff80002a79845, fffff88006c4ac10, 0} Probably caused by : memory_corruption Followup: memory_corruption

Hi, please check your RAM for errors. You can use MemTest86+ (http://www.memtest.org/) to do this. André"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

see a previous post: "-I ran memcheck86 again, and it detected no errors after 9 passes."

Hello Patrice,Please follow my earlier steps for enabling driver verifier again. I'd leave it set up that way for a few days, until you can "hopefully" get it to crash again and identify the offending component.I'd suggest trying to repeat some of the same actions where you've seen a crash in the past.Good luck,MarkWant to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

Mark, I have gone by to enabling the verifier /standard /all like you suggested. I was very tempted this morning to put in ram that I know is working fine from another laptop. But if this next crash will be telltale, then I'll leave it.

update: my last two aberrant restarts (I wasn't around to see if they were blue screens) did not elicit a memory.dmp or Minidump files, and this is with verifier /standard/all enabled. this is very frustrating. any further suggestions appreciated.

One way to know for sure if it was a crash is to prevent the reboot after a crash.Control Panel -> System and Security -> System -> Advanced System Settings -> Settings in the Startup and Recovery section -> Uncheck "automatically restart".Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

ok, based on this setting the blue screen stayed from last night. it is still not writing to the dump files even though the blue screen says it is. I am certainly in the verifier mode that was suggested above. there is plenty of disk space, it is just not writing to Windows/Memory.dump or Windows/Minidump/. I might move the files that are there now, maybe it doesn't want to overwrite them? this is a headscratcher. i am elicting plenty of blue screens but cannot get a log the last 3 times. Pat

Well, if it won't create a crash file, perhaps we'll have to troubleshoot with what's on that screen. The next time it happens, can you take a picture of it, and upload that to the skydrive share? If not, take a look at this example: http://www.pcstats.com/articleimages/200409/BSOD_2.gif. I'd need you to capture the exact STOP error code (along with all of the other values; sometimes they're useful, sometimes they're not), the "title" of the crash (in the example, it's DRIVER_IRQL_NOT_LESS_OR_EQUAL), and let me know if there are any drivers mentioned on the screen (in the example, it would be WXYZ.SYS).On the page where you changed the option to prevent the reboot, what are the other settings?Did you try searching on the hard drive for *.dmp? Maybe it's not putting it in the locations we're expecting (for some unknown reason).Did you update the wifi driver as suggested above?Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

Well, if it won't create a crash file, perhaps we'll have to troubleshoot with what's on that screen. The next time it happens, can you take a picture of it, and upload that to the skydrive share? If not, take a look at this example: http://www.pcstats.com/articleimages/200409/BSOD_2.gif. I'd need you to capture the exact STOP error code (along with all of the other values; sometimes they're useful, sometimes they're not), the "title" of the crash (in the example, it's DRIVER_IRQL_NOT_LESS_OR_EQUAL), and let me know if there are any drivers mentioned on the screen (in the example, it would be WXYZ.SYS). Ok, I will probably end up typing out the screen the next time.On the page where you changed the option to prevent the reboot, what are the other settings? "Write an event to the system log" is checked. For "Write debugging information" Kernel memory dump is selected, and the Dump file points to %SystemRoot%\MEMORY.DMP (this file was not created/updated since 12/25 crash) "Overwrite any existing file" is also checked. Did you try searching on the hard drive for *.dmp? Maybe it's not putting it in the locations we're expecting (for some unknown reason). couldn't find anything. is it interesting that once I enabled verifier I cannot get the logs anymore? Did you update the wifi driver as suggested above? yes I did. the intel 5100 wifi adapter driver was installed from the intel website, after uninstalling gateway's driver for this card. the intel site had the latest drivers for this wifi adapter. this was done also for the video driver, but the sata driver was from the gateway site. I wonder if this is just windows 7 64 bit bugginess. I installed it from a cd from scratch, the laptop originally came with vista 32 bit. at least with the stock OS it has been tested. if it is hardware related I only have until middle of next week to return it. Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

It's very odd that a memory dump isn't being created anymore. In some rare cases, that can be caused by a driver bug too.I went through one of your earlier dump files, to see if there were any old or odd drivers that stood out.I am not blaming these drivers for causing your problem, it's just a suggestion at things you might want to look at.1) Make sure your Symantec software is up to date (not just the antivirus signatures, but the apps/drivers)2) I see you have PowerISO software installed. You might want to try uninstalling this, to see if it this problem goes away.3) You might want to try updating your Intel video drivers.Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

thanks for taking the time Mark. the wireless and video drivers are both fully up to date. i uninstalled poweriso and i updated Symantec but turned it off for now (i think both are 32 bit software) I have until the end of the week to set up an RMA for return, i just want to find out if it's faulty hardware or not by then.

The Symantec software loads drivers. Those drivers have to be 64-bit, or they wouldn't load. I think most AV software includes 32/64-bit drivers these days.In my experience, these sorts of problems are either caused by bad hardware (like RAM) or bad drivers. You've already tested the RAM with no problems, so that's why I'm still suspecting drivers. Hopefully the info from the crash screen the next time it happens will help.Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

just to give an overview: -bios, video, wireless, and sata drivers are all up to date -memory tests (9 passes) have yielded 0 errors -uninstalled PowerISO and disabled symantec -crash blue screen every 1-2 days, not certain if playing movies/wireless file transfer have helped make it crash or not. if it is indeed drivers, then running under my 32 bit ubuntu OS (on another partition) should not yield any "freezes". I may give that a shot if this approach doesn't pan out. also I still haven't tried swapping out the memory. (is memtest 100% accurate?)

also I still haven't tried swapping out the memory. (is memtest 100% accurate?) Sorry, I haven't used that app myself, so I can't speak to its accuracy. I have seen a lot of people suggesting its use, and I haven't seen anyone complaining about incorrect results from the tool.Another thing you could consider doing is getting the system back in the original out of the box state.The next time it happens, try to jot down any notes you can about what was happening on the machine at the time. What apps were running (include the one you're working in as well as any others in the background)? Try to recall the exact set of steps you ran since the last time you resumed the machine, then try to repeat those steps to see if you can make the problem happen again. You might not have enough info after one crash, but if you hit a few more, you might see a common pattern.Sorry that this is so difficult. If you're running up against your return deadline, I'd suggest going ahead with the return just in case it's a hardware issue. If you run into these same issues with the replacement (I HOPE NOT!), you'll at least have a good starting point. Maybe install a few apps, use the machine for a few days, then install more apps, use it for a few more days, etc. That would help you narrow down if it's caused by an application. Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

I had them send me a replacement. who knows maybe disabling symantic fixed it, but I have no way of knowing but it hasn't crashed yet since. I think this time around, instead of wiping it and installing Windows 7 Ultimate 64 bit, I will just use their Windows 7 32 bit upgrade cd to upgrade from vista to windows 7. several applications were buggy under this 64 bit version, including: vlc, winscp, chrome

since i still want to crash it i started up 2 movies and a file transfer of winscp, and the screen blinked a few times, and then said that windows manager had stopped, now windows media player is just hung. also today, it showed i have connected to my wireless router but i could not ping it! (or of course access anything on the internet). as another note, maybe it is better to use the drivers available at the laptop vendor's website, rather then getting the "stock" driver from the manufacterer. The former may have been tested specifically for your computer. just food for thought.

Mark, I have one last dump info for you, the screen said: DRIVER-IRQL-NOT-LESS-OR-EQUAL STOP: Ox000000D1 and then the next sequences were preceeded by zeros: C, OE, 02, 00, XFFFFFA8005256153 verifier was turned off for this unfortunately cheers : )

Patrice here is a step by step guide on how to analyse a dump file so you can do it yourself:http://clintboessen.blogspot.com/2009/12/how-to-analyze-dump-file.htmlClint Boessen MCSE, MCITP: Messaging Perth, Western Australia Blog: http://clintboessen.blogspot.com/

Pat,I don't see that latest dump on your skydrive site. Can you post it on your skydrive page please?I'm not sure that it's going to be too helpful, but I'm willing to take a look :)At this point, I think the only way we're going to track it down to the particular driver is for you to run with verifier enabled all the time. Edit: That's not really ideal, and I wouldn't suggest that people do this as a normal thing. But in your case, to track down this specific problem, I think it would be warranted.Are there any devices that you only connect to the PC every now and then? Maybe it's not happening all the time because it only happens when one of those devices is in use.Anything you can think of that's common in the cases where you've seen the crash could be helpful in narrowing this down.Thanks,Mark Want to know if your current hardware & software will work with Windows 7? Check out these links: **Windows 7 Upgrade Advisor ** **Windows 7 Compatibility Center**

Wow, this thread (the OP problem) could have been written by me! I own a Gateway laptop, and am having the exact same problems. Mine came with Vista64, which I upgraded to W7-64. The basic error message (pointing to the intel driver) is the same. The blue screen crashes seem to happen when there's a large data transfer going on. For instance, sometimes the crash happens when I'm watching streamed content (HD through HDHomerun) in Media Center. For what it's worth, I have run Ubuntu on the same hardware for a day or so, and no crashes or errors there, so I'm suspecting that driver. I have uninstalled that Intel driver, then reinstalled fresh the latest version, but to no avail; if anything the BSOD's seem to increase lately.