Hi Guys,
I am in a need of urgent help, because of the BSOD that I'm constantly having.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88002F88850
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Windows OEM 7 Home Premium x64
Alienware M15x
i7 Q720, 4GB DDR3 RAM, NVIDIA GeForce GTX 260M
The minidumps is attached.
Thank you so much.
I am in a need of urgent help, because of the BSOD that I'm constantly having.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88002F88850
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Windows OEM 7 Home Premium x64
Alienware M15x
i7 Q720, 4GB DDR3 RAM, NVIDIA GeForce GTX 260M
The minidumps is attached.
Thank you so much.
Sorry no minidump. No download of any kind.
Please read these threads and post back. We will be glad to help you.
[1 - Novice] How to ask for help with a BSOD problem
http://www.sevenforums.com/crashes-d...tructions.html
Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.
You can make this easier by downloading Speccy.
[1 - Novice] How to ask for help with a BSOD problem
http://www.sevenforums.com/crashes-d...tructions.html
Please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.
You can make this easier by downloading Speccy.
Thank you for the replies.
I have follow the instruction and put all the minidumps and system health reports in a RAR files.
Do I have to use WINZIP? or will it be fine with WINRAR?
I have attached the files to my post, and I don't understand why doesn't it shows.
I have follow the instruction and put all the minidumps and system health reports in a RAR files.
Do I have to use WINZIP? or will it be fine with WINRAR?
I have attached the files to my post, and I don't understand why doesn't it shows.
�� Quote: Originally Posted by sawwei 
Thank you for the replies.
I have follow the instruction and put all the minidumps and system health reports in a RAR files.
Do I have to use WINZIP? or will it be fine with WINRAR?
I have attached the files to my post, and I don't understand why doesn't it shows.
I have follow the instruction and put all the minidumps and system health reports in a RAR files.
Do I have to use WINZIP? or will it be fine with WINRAR?
I have attached the files to my post, and I don't understand why doesn't it shows.
How big is it? if more than 8 Mb you will have to put it on an upload service like rapidshare.
Ken
It's only 326kb
I uploaded it again in this post.
Please let me know if you can access it.
I have also updated my User CP with more detailed information of my system.
I have just performed a system recovery two days ago and last night I turned on my notebook for the whole night because I was downloading some torrents files.
When I woke up in the morning I found out that my notebook was restarted and there was the BSOD notifications on the screen.
This is time the BSOD occured when I did not do anything at all.
BSOD happened several times before I did the system recovery and everytime when I checked the windows solutions it was always stated that Video Hardware Error caused the Windows to stop working properly.
I just bought my notebook last February, and it is still under warranty, and I am thinking to send them to the manufacturer, but I can't seem to be able to trigger the BSOD whenever I want to, so how can I be sure if they fixed the problems.
Thank you.
I uploaded it again in this post.
Please let me know if you can access it.
I have also updated my User CP with more detailed information of my system.
I have just performed a system recovery two days ago and last night I turned on my notebook for the whole night because I was downloading some torrents files.
When I woke up in the morning I found out that my notebook was restarted and there was the BSOD notifications on the screen.
This is time the BSOD occured when I did not do anything at all.
BSOD happened several times before I did the system recovery and everytime when I checked the windows solutions it was always stated that Video Hardware Error caused the Windows to stop working properly.
I just bought my notebook last February, and it is still under warranty, and I am thinking to send them to the manufacturer, but I can't seem to be able to trigger the BSOD whenever I want to, so how can I be sure if they fixed the problems.
Thank you.
Error code 1E KMODE_EXCEPTION_NOT_HANDLED - Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
The dumps blames nwifi.sys and points to memory corruption. This is a hardware/hardware related error. Usually this is related to a network adapter/driver problem.
I find the following out of date drivers on your system:
AnyDVD.sys Thu Apr 09 20:40:36 2009 - AnyDVD Filter Driver or Watch & copy any DVD! belongs to the software AnyDVD by SlySoft, Inc (www.slysoft.com). Update the driver or the software or uninstall it.
BCM42RLY.sys Tue Jul 07 20:34:55 2009 - Broadcom iLine10(tm) PCI Network Adapter Proxy Protocol Driver belongs to the software BCM42RLY or Broadcom iLine10(tm) PCI Network Adapter by Broadcom Corporation (www.broadcom.com). I suspect this driver had a lot to do with your crash. Update this driver
e1k62x64.sys Mon Jun 22 14:05:53 2009 - Intel 82577LM Gigabit LAN Driver. Update this driver.
ElbyCDIO.sys Tue Feb 17 12:11:23 2009 - ElbyCD Windows NT/2000/XP I/O driver or ElbyCD Windows NT/2000 I/O driver belongs to the software CDRTools or ElbyCDIO Driver or DVD Region Killer or VirtualCloneDrive by Elaborate Bytes AG (www.elby.ch). Update the driver or the software or uninstall the software.
rimspx64.sys Mon Mar 03 04:19:03 2008 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com This driver is very obsolete. If you cannot update the driver, upgrade your card reader to one that is certified Win 7 compatible.
rixdpx64.sys Fri Jul 27 06:45:50 2007 - See above.
Update these drivers from the manufacturers' websites. Win 7 does not like older drivers. They can and do cause memory corruption. Reboot and run your system and lets see if you have another crash. If you do, upload that BSOD file to us. And we will go from there. If your system runs smoothly, please let us know that, too. If you need help with the drivers, please post and ask.
By the way, we do prefer that you use zip instead of RAR.
What antivirus and firewall are you running?
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff88002f88850, 0, 0} Probably caused by : nwifi.sys ( nwifi!Dot11AllocateSendPacket+58 ) Followup: MachineOwner --------- 2: 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: fffff88002f88850, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, 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: +575e952f007ad868 fffff880`02f88850 6897f80280 push 0FFFFFFFF8002F897h EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb40e0 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002f89768 -- (.exr 0xfffff88002f89768) ExceptionAddress: fffff80002a7f905 (nt!ExpInterlockedPopEntrySListFault16) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88002f89810 -- (.trap 0xfffff88002f89810) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000002a81940007 rbx=0000000000000000 rcx=fffff88008b1c280 rdx=48dd6f4b988e70e1 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a7f905 rsp=fffff88002f899a0 rbp=fffff88002f89a30 r8=48dd6f4b988e70e0 r9=00000000646e5344 r10=fffff88008b1c280 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!ExpInterlockedPopEntrySListFault16: fffff800`02a7f905 498b08 mov rcx,qword ptr [r8] ds:0001:48dd6f4b`988e70e0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002b0ebdb to fffff80002a7c740 STACK_TEXT: fffff880`02f88798 fffff800`02b0ebdb : 00000000`0000001e ffffffff`c0000005 fffff880`02f88850 00000000`00000000 : nt!KeBugCheckEx fffff880`02f887a0 fffff800`02acdd30 : fffffa80`0800e920 fffff800`02a44f7a fffffa80`0800e920 00000000`00000001 : nt!KipFatalFilter+0x1b fffff880`02f887e0 fffff800`02aaad1c : 00000000`00000000 fffff880`02f88f30 fffff880`02f88a01 fffff880`02f88f58 : nt! ?? ::FNODOBFM::`string'+0x95d fffff880`02f88820 fffff800`02aa240d : fffff800`02bc8bc4 fffff880`02f8aec0 00000000`00000000 fffff800`02a0c000 : nt!_C_specific_handler+0x8c fffff880`02f88890 fffff800`02aa9a90 : fffff800`02bc8bc4 fffff880`02f88908 fffff880`02f89768 fffff800`02a0c000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02f888c0 fffff800`02ab69ef : fffff880`02f89768 fffff880`02f88fd0 fffff880`00000000 fffffa80`00000005 : nt!RtlDispatchException+0x410 fffff880`02f88fa0 fffff800`02a7bd82 : fffff880`02f89768 fffff880`08b1c280 fffff880`02f89810 fffffa80`06ad7790 : nt!KiDispatchException+0x16f fffff880`02f89630 fffff800`02a7a68a : fffff880`02f89dd1 fffffa80`04c3ac60 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`02f89810 fffff800`02a7f905 : fffff880`08b1c280 fffff880`08ae21cc 00000000`00000001 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a fffff880`02f899a0 fffff880`08ae21cc : 00000000`00000001 00000000`00000001 fffff880`02f89a30 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16 fffff880`02f899b0 fffff880`08ae6142 : 00000000`00000001 fffffa80`07c45f10 00000000`00000000 fffffa80`07427010 : nwifi!Dot11AllocateSendPacket+0x58 fffff880`02f899e0 fffff880`08ae651b : fffffa80`07427010 00000000`00000000 fffffa80`07427010 00000000`00000000 : nwifi!MP6SendOneNBL+0x262 fffff880`02f89b30 fffff880`08aebf67 : 00000000`00000302 fffffa80`07c45d30 00000000`00000000 00000000`00000000 : nwifi!MP6SendNBLInternal+0x67 fffff880`02f89b80 fffff880`016e7af4 : fffffa80`04fd7270 00000000`00000001 00000000`00000000 fffffa80`04c3ac60 : nwifi!FilterSendNetBufferLists+0x7f fffff880`02f89bb0 fffff880`040de199 : fffffa80`07c45d30 fffffa80`05d871a0 00000000`00000000 fffff880`02f89ca0 : ndis!NdisFSendNetBufferLists+0x64 fffff880`02f89bf0 fffff880`016e7a39 : 00000000`00000001 00000000`00000000 fffffa80`079e8080 00000000`00000011 : pacer!PcFilterSendNetBufferLists+0x29 fffff880`02f89cf0 fffff880`017a3785 : fffff880`0681a625 00000000`00000000 fffffa80`05d871a0 fffff880`02f8a200 : ndis!ndisSendNBLToFilter+0x69 fffff880`02f89d50 fffff880`0186634e : 00000000`00000000 00000000`0000000e fffffa80`07419410 fffffa80`079e8080 : ndis!NdisSendNetBufferLists+0x85 fffff880`02f89db0 fffff880`01867a67 : fffff880`0196c9a0 00000000`00000000 fffffa80`077a0000 00000000`01960800 : tcpip!IppFragmentPackets+0x39e fffff880`02f89ed0 fffff880`018637d5 : 00000000`00000000 00000000`00000000 00000054`00000320 00000000`0000000e : tcpip!IppDispatchSendPacketHelper+0x87 fffff880`02f89f90 fffff880`01865124 : fffffa80`081f9006 00000000`00009900 fffffa80`00000014 00000000`00000000 : tcpip!IppPacketizeDatagrams+0x2d5 fffff880`02f8a0b0 fffff880`0186a1ee : fffffa80`04bb0f00 fffffa80`0827b007 fffff880`0196c9a0 fffffa80`081f9010 : tcpip!IppSendDatagramsCommon+0x754 fffff880`02f8a380 fffff880`0185ce2a : fffffa80`0827b010 00000000`00000000 00000000`00000001 00000000`00000002 : tcpip!IpNlpSendDatagrams+0x3e fffff880`02f8a3c0 fffff880`018791f7 : 00000000`0000c97b ffff0000`036ec5f5 fffffa80`00000002 fffffa80`0741d860 : tcpip!TcpTcbHeaderSend+0x5ea fffff880`02f8a570 fffff880`01874a56 : 00000000`00000000 fffffa80`04ba7000 fffff880`01966128 fffff880`01840ac2 : tcpip!TcpTcbSend+0x807 fffff880`02f8a7f0 fffff880`0187c44c : fffff880`06968000 00000000`00000000 00000000`00000000 fffff880`0185f700 : tcpip!TcpFlushDelay+0x316 fffff880`02f8a8d0 fffff880`0185e6c7 : fffffa80`04ba998c fffffa80`04bcb9b0 fffffa80`04bb998c 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x20c fffff880`02f8a980 fffff880`0185e799 : fffff880`02f8ab00 fffff880`0196c9a0 fffff880`02f8ab10 fffffa80`04a00ad0 : tcpip!IppDeliverListToProtocol+0x97 fffff880`02f8aa40 fffff880`0185ec90 : fffffa80`075c9cb0 fffffa80`081a6b00 00000000`00000011 fffff880`02f8ab00 : tcpip!IppProcessDeliverList+0x59 fffff880`02f8aab0 fffff880`0185db21 : 00000000`6401a8c0 fffffa80`04ba7000 fffff880`0196c9a0 00000000`07419401 : tcpip!IppReceiveHeaderBatch+0x231 fffff880`02f8ab90 fffff880`0185c592 : fffffa80`07415a30 00000000`00000000 fffffa80`07419401 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651 fffff880`02f8ad90 fffff880`01875e5a : fffffa80`07419410 fffff880`02f8aec0 fffffa80`07419410 fffff880`01960000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff880`02f8ae70 fffff800`02a8be5a : fffffa80`075c9cb0 fffff880`02f86000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`02f8aec0 fffff880`01875882 : fffff880`01875d80 fffff880`02f8afd0 fffffa80`07c45d02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda fffff880`02f8afa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2 STACK_COMMAND: kb FOLLOWUP_IP: nwifi!Dot11AllocateSendPacket+58 fffff880`08ae21cc 4885c0 test rax,rax SYMBOL_STACK_INDEX: a SYMBOL_NAME: nwifi!Dot11AllocateSendPacket+58 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nwifi IMAGE_NAME: nwifi.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc3b FAILURE_BUCKET_ID: X64_0x1E_nwifi!Dot11AllocateSendPacket+58 BUCKET_ID: X64_0x1E_nwifi!Dot11AllocateSendPacket+58 Followup: MachineOwner --------- I find the following out of date drivers on your system:
AnyDVD.sys Thu Apr 09 20:40:36 2009 - AnyDVD Filter Driver or Watch & copy any DVD! belongs to the software AnyDVD by SlySoft, Inc (www.slysoft.com). Update the driver or the software or uninstall it.
BCM42RLY.sys Tue Jul 07 20:34:55 2009 - Broadcom iLine10(tm) PCI Network Adapter Proxy Protocol Driver belongs to the software BCM42RLY or Broadcom iLine10(tm) PCI Network Adapter by Broadcom Corporation (www.broadcom.com). I suspect this driver had a lot to do with your crash. Update this driver
e1k62x64.sys Mon Jun 22 14:05:53 2009 - Intel 82577LM Gigabit LAN Driver. Update this driver.
ElbyCDIO.sys Tue Feb 17 12:11:23 2009 - ElbyCD Windows NT/2000/XP I/O driver or ElbyCD Windows NT/2000 I/O driver belongs to the software CDRTools or ElbyCDIO Driver or DVD Region Killer or VirtualCloneDrive by Elaborate Bytes AG (www.elby.ch). Update the driver or the software or uninstall the software.
rimspx64.sys Mon Mar 03 04:19:03 2008 - Ricoh Memory Card Reader driver OEM - none at http://www.ricoh.com This driver is very obsolete. If you cannot update the driver, upgrade your card reader to one that is certified Win 7 compatible.
rixdpx64.sys Fri Jul 27 06:45:50 2007 - See above.
Update these drivers from the manufacturers' websites. Win 7 does not like older drivers. They can and do cause memory corruption. Reboot and run your system and lets see if you have another crash. If you do, upload that BSOD file to us. And we will go from there. If your system runs smoothly, please let us know that, too. If you need help with the drivers, please post and ask.
By the way, we do prefer that you use zip instead of RAR.
What antivirus and firewall are you running?
Code:
2: kd> r Last set context: rax=0000002a81940007 rbx=0000000000000000 rcx=fffff88008b1c280 rdx=48dd6f4b988e70e1 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a7f905 rsp=fffff88002f899a0 rbp=fffff88002f89a30 r8=48dd6f4b988e70e0 r9=00000000646e5344 r10=fffff88008b1c280 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=0001 es=0000 fs=0000 gs=0000 efl=00010202 nt!ExpInterlockedPopEntrySListFault16: fffff800`02a7f905 498b08 mov rcx,qword ptr [r8] ds:0001:48dd6f4b`988e70e0=???????????????? 2: kd> .formats 48dd6f4b988e70e0 Evaluate expression: Hex: 48dd6f4b`988e70e0 Decimal: 5250475111056568544 Octal: 0443353364563043470340 Binary: 01001000 11011101 01101111 01001011 10011000 10001110 01110000 11100000 Chars: H.oK..p. Time: Mon Feb 4 14:51:45.656 18239 (GMT-4) Float: low -3.68201e-024 high 453498 Double: 1.02565e+043
�� Quote: Originally Posted by CarlTR6 What antivirus and firewall are you running?
I will usually go to the Dell Alienware support site to keep myself updated with the latest drivers.
All of the drivers installed on my system are all current, at least according to their support page.
I did try to find a newer Video driver in the NVIDIA website, but when I installed it my screen resolutions got all weird up and also the color looks horrible.
So I changed back to the driver given on the dell's support page and everything was back to normal.
What do you suggest I should do about this driver thing ?
I consider myself as a person who likes the system to be always updated, but sometimes the latest drivers gives me lots of problems as well.
Thanks a lot for your detailed explanations...
Honestly, I'd be calling Dell and making them handle this. Most folks here have homebrew machines and don't have an OEM to go to when things fail, but assuming this is still under warranty I'd be harassing them for a better Win7 driver.
�� Quote: Originally Posted by cluberti Honestly, I'd be calling Dell and making them handle this. Most folks here have homebrew machines and don't have an OEM to go to when things fail, but assuming this is still under warranty I'd be harassing them for a better Win7 driver.
I had all of those drivers installed on my system, yet I am still experiencing this BSOD.
I can help but think that maybe their system is not stable enough to handle all this stuffs.
Well, Dell can put a lot more pressure on vendors to fix drivers than you can.
�� Quote: Originally Posted by sawwei �� Quote: Originally Posted by CarlTR6 What antivirus and firewall are you running?
I will usually go to the Dell Alienware support site to keep myself updated with the latest drivers.
All of the drivers installed on my system are all current, at least according to their support page.
I did try to find a newer Video driver in the NVIDIA website, but when I installed it my screen resolutions got all weird up and also the color looks horrible.
So I changed back to the driver given on the dell's support page and everything was back to normal.
What do you suggest I should do about this driver thing ?
I consider myself as a person who likes the system to be always updated, but sometimes the latest drivers gives me lots of problems as well.
Thanks a lot for your detailed explanations...
NVidia drivers are interesting. I had to try five before I could get my video card and system working properly. I ended up using the third or fourth one down the list. I can confirm that the latest drivers from NVidia are not always the best.
The big question here is your Broadcom driver and the Intel driver. Are these the ones you could not update? You did properly by going to the Dell website. Many times, laptop manufactures modify the manufactures' drivers for the particular laptop systems. Sometimes, however, you have to try the manufactures' sites.
�� Quote: Originally Posted by cluberti Honestly, I'd be calling Dell and making them handle this. Most folks here have homebrew machines and don't have an OEM to go to when things fail, but assuming this is still under warranty I'd be harassing them for a better Win7 driver.
Did you try to see if the Broadcom site has an updated driver? Or the Intel site?
From your explanations above, you did not mention any Intel driver that I should look into or did you ?
I tried to access the Broadcom site but it was very confusing and I tried to use their search engine to look for my driver but it returned with no result.
When I search the web for the Broadcom driver that suits my system, I found that my driver is the latest one.
I have removed some other drivers/softwares you mentioned in the report above, since I think I don't need them anyway.(eg.ANYDVD, Region DVD Killer, etc)
I tried to access the Broadcom site but it was very confusing and I tried to use their search engine to look for my driver but it returned with no result.
When I search the web for the Broadcom driver that suits my system, I found that my driver is the latest one.
I have removed some other drivers/softwares you mentioned in the report above, since I think I don't need them anyway.(eg.ANYDVD, Region DVD Killer, etc)
Good job on removing the obsolete software. Here is the driver I was talking about:
e1k62x64.sys Mon Jun 22 14:05:53 2009 - Intel 82577LM Gigabit LAN Driver
Were you able to update this one? Actually, removing/uninstalling the card reader may be enough to give you a stable system. But the dump does point to the network adapter/drivers. Check this link and see what you can find: Broadcom.com - Ethernet NIC Driver Downloads
Have you had any more BSOD's since the one you uploaded? If not let your system run. If you get another BSOD, upload it to us and then enable Driver Verifier. Upload any Driver Verifier enabled dumps.
Driver Verifier - Enable and Disable
e1k62x64.sys Mon Jun 22 14:05:53 2009 - Intel 82577LM Gigabit LAN Driver
Were you able to update this one? Actually, removing/uninstalling the card reader may be enough to give you a stable system. But the dump does point to the network adapter/drivers. Check this link and see what you can find: Broadcom.com - Ethernet NIC Driver Downloads
Have you had any more BSOD's since the one you uploaded? If not let your system run. If you get another BSOD, upload it to us and then enable Driver Verifier. Upload any Driver Verifier enabled dumps.
Driver Verifier - Enable and Disable
�� Quote: Originally Posted by CarlTR6 e1k62x64.sys Mon Jun 22 14:05:53 2009 - Intel 82577LM Gigabit LAN Driver
Were you able to update this one?
Have you had any more BSOD's since the one you uploaded? If not let your system run. If you get another BSOD, upload it to us and then enable Driver Verifier. Upload any Driver Verifier enabled dumps.
I also have not experienced more BSOD since my upload, and hopefully it stays that way...
Carl, I think I found what caused all of those problem I'm having.
First of all it was because when you log into Dell Alienware's support page, you need to log in with your Service Tag Number, and then they will redirect you to the support page that suitable for your system needs.
Because of that, I thought that every single one of the drivers on that page were needed by my system.
Later on I thought that since Alienware is a custom build notebook, than the drivers could have been for other hardwares that weren't even in my notebook.
My network adapter is Intel 82577LM Gigabit LAN, and I installed both the drivers for that adapter and Broadcom's WLAN adapter. I think those two drivers caused the system conflict, hence resulted in the BSOD. Do you think this was the cause, Carl ?
Yes, I think so. The stack in your BSOD analysis is a network stack crash; so your network adapter and wi-fi adapter were involved in the crash. Such can easily be caused by a faulty or old driver.
I surely hope the drivers have fixed your problem. It is good to hear that you have not had another BSOD. Report back to us in a couple of day and let us know how your system is doing. I hope we can mark the thread as solved.
Of course if you have another crash, upload the dump file to us. Good luck and happy computing.
I surely hope the drivers have fixed your problem. It is good to hear that you have not had another BSOD. Report back to us in a couple of day and let us know how your system is doing. I hope we can mark the thread as solved.
Of course if you have another crash, upload the dump file to us. Good luck and happy computing. Hi Carl,
I haven't got a BSOD since that last one, but I actually did a System Recovery last Saturday and it was because my Wi-Fi can' connect to my wireless router at home.
It detected the connection but can't connect to it. Even after the System Recovery, I still could not connect the WLAN. I thought there must have been some problem with my WLAN hardware, but after a while I managed to connect it. I am hoping that I will not have a hardware related problems, since I hate it to send it back to the manufacturer.
When everything ran smoothly I decided to back up my system, just in case if I had another problems in the future. Hopefully I would not need them....
Thanks so much for helping me solving my problems.
I haven't got a BSOD since that last one, but I actually did a System Recovery last Saturday and it was because my Wi-Fi can' connect to my wireless router at home.
It detected the connection but can't connect to it. Even after the System Recovery, I still could not connect the WLAN. I thought there must have been some problem with my WLAN hardware, but after a while I managed to connect it. I am hoping that I will not have a hardware related problems, since I hate it to send it back to the manufacturer.
When everything ran smoothly I decided to back up my system, just in case if I had another problems in the future. Hopefully I would not need them....
Thanks so much for helping me solving my problems.
That is news we love to hear!! You are very welcome and thank you for reporting back. We will ask the moderators to mark this one as solved. Happy Computing.
You are very welcome and thank you for reporting back. We will ask the moderators to mark this one as solved. Happy Computing. Hi Carl,
The BSOD happened again this morning !!!
I attached the dump files.
The BSOD happened again this morning !!!
I attached the dump files.
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M. Usual caused by Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.
This one points to memory corruption.
Let's test your RAM
RAM - Test with Memtest86+
Post back with the results.
Code:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c90e50 Debug session time: Mon Aug 30 19:13:28.617 2010 (GMT-4) System Uptime: 0 days 7:40:23.006 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80002b45a86, fffff880033e78a8, fffff880033e7110} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49705 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002b45a86, The address that the exception occurred at Arg3: fffff880033e78a8, Exception Record Address Arg4: fffff880033e7110, Context Record Address 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! ?? ::FNODOBFM::`string'+49705 fffff800`02b45a86 488b00 mov rax,qword ptr [rax] EXCEPTION_RECORD: fffff880033e78a8 -- (.exr 0xfffff880033e78a8) ExceptionAddress: fffff80002b45a86 (nt! ?? ::FNODOBFM::`string'+0x0000000000049705) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880033e7110 -- (.cxr 0xfffff880033e7110) rax=6d3d6362b5379cf8 rbx=0000000000000000 rcx=6d3d6362b5379cf8 rdx=fffffa80079a7000 rsi=fffff880033e7ba0 rdi=fffffa800438ab48 rip=fffff80002b45a86 rsp=fffff880033e7ae0 rbp=0000000000000002 r8=0000000000000001 r9=fffffa800438ab48 r10=0000000000000005 r11=0000000000000000 r12=0000000000000001 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt! ?? ::FNODOBFM::`string'+0x49705: fffff800`02b45a86 488b00 mov rax,qword ptr [rax] ds:002b:6d3d6362`b5379cf8=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: LogonUI.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfb0e0 ffffffffffffffff FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+49705 fffff800`02b45a86 488b00 mov rax,qword ptr [rax] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff80002ad7ee2 to fffff80002b45a86 STACK_TEXT: fffff880`033e7ae0 fffff800`02ad7ee2 : 00000000`00006be7 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x49705 fffff880`033e7b80 fffff800`02ad8173 : 00000000`00000008 fffff880`033e7c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e fffff880`033e7bd0 fffff800`02d67c06 : fffffa80`03b7c680 00000000`00000080 fffffa80`03b50990 00000000`00000001 : nt!KeBalanceSetManager+0x1c3 fffff880`033e7d40 fffff800`02aa1c26 : fffff880`009b1180 fffffa80`03b7c680 fffff880`009bc0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033e7d80 00000000`00000000 : fffff880`033e8000 fffff880`033e2000 fffff880`033e7710 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+49705 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880033e7110 ; kb FAILURE_BUCKET_ID: X64_0x7E_nt!_??_::FNODOBFM::_string_+49705 BUCKET_ID: X64_0x7E_nt!_??_::FNODOBFM::_string_+49705 Followup: MachineOwner --------- Let's test your RAM
RAM - Test with Memtest86+
Post back with the results.
Update your InterVideo drivers: Enable driver verifier: Driver Verifier - Enable and Disable
Code:
regi.sys Tue Oct 31 04:22:11 2006
�� Quote: Originally Posted by CarlTR6 This one points to memory corruption.
I have tested my RAM for 7 passed and it did not show any errors.
You mentioned in the mail that many possibility can caused this particular BSOD, but the error pointed to memory corruption.
What do you think we should do next to check and configure the real problems?
�� Quote: Originally Posted by Jonathan_King Update your InterVideo drivers: Enable driver verifier: Driver Verifier - Enable and Disable
Code:
regi.sys Tue Oct 31 04:22:11 2006
Do you think that one was the cause of my BSOD ?
Come to think of it, I don't recall I have install anything from Intervideo.
How can I delete that driver ?
I enabled the Driver Verifier, restarted, but then I stucked on the Windows 7 logo and my system was not responding.
Looking through your list of installed programs, I see Cyberlink YouCam. Please go into Programs and Features, and remove that. It probably came pre-installed on your computer.
Keep trying to boot with Verifier enabled. If it is a hardware issue, it will likely boot after a few tries. If it is a low-level driver causing the issue, it may not boot ever.
Your Intel networking drivers should be updated. Try these ones: � Intel® PRO/Wireless and WiFi Link Drivers-Only for Windows 7*
Keep trying to boot with Verifier enabled. If it is a hardware issue, it will likely boot after a few tries. If it is a low-level driver causing the issue, it may not boot ever.
Your Intel networking drivers should be updated. Try these ones: � Intel® PRO/Wireless and WiFi Link Drivers-Only for Windows 7*
�� Quote: Originally Posted by Jonathan_King Looking through your list of installed programs, I see Cyberlink YouCam. Please go into Programs and Features, and remove that. It probably came pre-installed on your computer.
Keep trying to boot with Verifier enabled. If it is a hardware issue, it will likely boot after a few tries. If it is a low-level driver causing the issue, it may not boot ever.
Your Intel networking drivers should be updated. Try these ones: � Intel® PRO/Wireless and WiFi Link Drivers-Only for Windows 7*
Keep trying to boot with Verifier enabled. If it is a hardware issue, it will likely boot after a few tries. If it is a low-level driver causing the issue, it may not boot ever.
Your Intel networking drivers should be updated. Try these ones: � Intel® PRO/Wireless and WiFi Link Drivers-Only for Windows 7*
Is the Cyberlink YouCam related to the Intervideo Driver or that's the program that caused my BSOD?
How long should I try to boot with the Verifier enabled ?
Try booting perhaps 6 times with Verifier enabled.
We don't know if the Intervideo driver is causing the problem, but we're trying to eliminate possible causes. My best guess at what program is using that driver is YouCam.
We don't know if the Intervideo driver is causing the problem, but we're trying to eliminate possible causes. My best guess at what program is using that driver is YouCam.
�� Quote: Originally Posted by Jonathan_King Try booting perhaps 6 times with Verifier enabled.
We don't know if the Intervideo driver is causing the problem, but we're trying to eliminate possible causes. My best guess at what program is using that driver is YouCam.
We don't know if the Intervideo driver is causing the problem, but we're trying to eliminate possible causes. My best guess at what program is using that driver is YouCam.
I also boot the system with Verifier Enabled.
After two failed attempts to boot, the system managed to do it on the third.
So, what should I do now ?
Should I just Enabled the Verifier or turn it off?
Leave the computer running, with Verifier enabled, and wait for it to crash. When it does, boot back up (you may have to disable driver verifier), and follow the BSOD Posting Instructions again.
�� Quote: Originally Posted by Jonathan_King Leave the computer running, with Verifier enabled, and wait for it to crash. When it does, boot back up (you may have to disable driver verifier), and follow the BSOD Posting Instructions again.
�� Quote: Originally Posted by sawwei �� Quote: Originally Posted by Jonathan_King Leave the computer running, with Verifier enabled, and wait for it to crash. When it does, boot back up (you may have to disable driver verifier), and follow the BSOD Posting Instructions again.
�� Quote: Originally Posted by sawwei �� Quote: Originally Posted by Jonathan_King Leave the computer running, with Verifier enabled, and wait for it to crash. When it does, boot back up (you may have to disable driver verifier), and follow the BSOD Posting Instructions again.
I let my system run for the night, but I did not have any BSOD.
What should I do now ?
What should I do now ?
Let it run for another day and use your system as you normally would.
�� Quote: Originally Posted by sawwei Hi Jonathan,
I am just wondering how to delete the Intervideo driver from my system.
When I use my old notebook, I used to have the Intervideo WinDVD program for the DVD playback, but on my new system I did not install any Intervideo program, only the Corel WinDVD.
I am trying to run my system with the Verifier Enabled for another day since I did not get any BSOD last night.
Thank you.
I am just wondering how to delete the Intervideo driver from my system.
When I use my old notebook, I used to have the Intervideo WinDVD program for the DVD playback, but on my new system I did not install any Intervideo program, only the Corel WinDVD.
I am trying to run my system with the Verifier Enabled for another day since I did not get any BSOD last night.
Thank you.
I did not install AnyDVD in my system.
I am running my system at home now.
What should I do if it did not show any errors until tonight?
Should I keep Enabling the Verifier or should I turn it off?
I am thinking of installing a new memory today, so do I have to Disable the Verifier before the installation?
Well, I gotta say that I'm a bit frustrated of the BSOD that I'm having lately.
For the last twice BSOD that occured, it was when I did not have any activities running on my system except for Bittorent.
This last BSOD even happen only one day after I did a System Recovery
I used to let my Bittorent run on my system every night and I have never experienced any BSOD.
The previous BSODs I had happened when I did various activities, once when I was watching a movie file with WMP, the other one when I was browsing through my files in windows explorer.
I am running my system at home now.
What should I do if it did not show any errors until tonight?
Should I keep Enabling the Verifier or should I turn it off?
I am thinking of installing a new memory today, so do I have to Disable the Verifier before the installation?
Well, I gotta say that I'm a bit frustrated of the BSOD that I'm having lately.
For the last twice BSOD that occured, it was when I did not have any activities running on my system except for Bittorent.
This last BSOD even happen only one day after I did a System Recovery
I used to let my Bittorent run on my system every night and I have never experienced any BSOD.
The previous BSODs I had happened when I did various activities, once when I was watching a movie file with WMP, the other one when I was browsing through my files in windows explorer.
Use your computer normally, with Verifier enabled, for about 12 more hours from now. If no BSODs until then, go ahead and disable verifier.
�� Quote: Originally Posted by Jonathan_King Use your computer normally, with Verifier enabled, for about 12 more hours from now. If no BSODs until then, go ahead and disable verifier.
After that, I enabled the Verifier, changed the regi.sys to regi.old and restarted my system.
I tried 6 times, but this time I failed to boot into the Windows this time, so I disable the Verifier.
I did enable the Verifier and ran the system for at least 24 hours without any BSOD's
What should I do next ?
I think you may disable driver verifier, and hope the BSODs don't return!
�� Quote: Originally Posted by Jonathan_King I think you may disable driver verifier, and hope the BSODs don't return!
Thank you Jonathan.
I've been using my system for almost a week without any problems until tonight.
My monitor suddenly shut off, but the system was still on.
I waited a while but nothing happened, so I restarted manually.
The weird thing is that I did not get any BSOD notifications, and this is the first time something like this ever happened to me.
Btw, I have just upgraded my BIOS 2 days ago.
My monitor suddenly shut off, but the system was still on.
I waited a while but nothing happened, so I restarted manually.
The weird thing is that I did not get any BSOD notifications, and this is the first time something like this ever happened to me.
Btw, I have just upgraded my BIOS 2 days ago.
It's hard to say, honestly. It could be a graphics driver problem, but since it doesn't seem like a huge recurring problem, you might consider overlooking it.
Here is a graphics driver update for you: NVIDIA DRIVERS 258.96 WHQL
Here is a graphics driver update for you: NVIDIA DRIVERS 258.96 WHQL
�� Quote: Originally Posted by Jonathan_King It's hard to say, honestly. It could be a graphics driver problem, but since it doesn't seem like a huge recurring problem, you might consider overlooking it.
Here is a graphics driver update for you: NVIDIA DRIVERS 258.96 WHQL
Here is a graphics driver update for you: NVIDIA DRIVERS 258.96 WHQL
Help !!!
Another BSOD
Another BSOD
There is no dump file attached.
Carl -- no dumps exist. That's why they are not in the report.
I see some evidence of the crash in Event Viewer: The logs indicate there was a memory dump 101910-18891-01.dmp at one time, but that file is nowhere to be found.
What is the page file set to? I see the page file is 7.99GB, for your 8GB RAM. Did you set it this way, or is the page file set to System Managed? Make sure it is the latter.
I don't see any cleaning programs installed, but if you are using any, remove them for now.
The logs also indicate that the memory.dmp file was updated, which may be our key here. Find that file in C:\Windows, and move it to the desktop. Right-click on it, and select Send to>Compressed folder.
Upload that .zip folder to Rapidshare or another site.
Now I see WMP and some other programs are crashing a lot. Also, you are getting errors such as these: That all points to network trouble to me.
Your Intel Ethernet drivers are old, dated 6/23/2009. That could be the problem. Install these ones: http://downloadcenter.intel.com/Deta...=3244&lang=eng
Dated 07/29/2010, they are 13 months newer.
Explorer.exe crashed too, though we may overlook this for now. Just run a system files check. Run sfc /scannow from an elevated command prompt.
You're also getting quite a few Kernel Power error 41 events. That is often a sign of bad hardware, but can also be caused by software.
In short, update those network drivers, and upload the memory.dmp file. Disable any cleaning programs for now.
I see some evidence of the crash in Event Viewer:
Code:
Event[298]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2010-10-19T10:40:11.000 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: W31-4L13NW4R3 Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000003, 0xfffff80002e4c980, 0xfffff80002e4c980, 0x1a45f57133ef39af). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101910-18891-01.
Code:
Event[48]: Log Name: Application Source: Windows Error Reporting Date: 2010-10-19T10:48:11.000 Event ID: 1001 Task: N/A Level: Information Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: W31-4L13NW4R3 Description: Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: P2: P3: P4: P5: P6: P7: P8: P9: P10: Attached files: C:\Windows\Minidump\101910-18891-01.dmp C:\Users\54W W31\AppData\Local\Temp\WER-472433-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0387ad10 Analysis symbol: Rechecking for solution: 0 Report Id: 101910-18891-01 Report Status: 0
What is the page file set to? I see the page file is 7.99GB, for your 8GB RAM. Did you set it this way, or is the page file set to System Managed? Make sure it is the latter.
I don't see any cleaning programs installed, but if you are using any, remove them for now.
The logs also indicate that the memory.dmp file was updated, which may be our key here. Find that file in C:\Windows, and move it to the desktop. Right-click on it, and select Send to>Compressed folder.
Upload that .zip folder to Rapidshare or another site.
Now I see WMP and some other programs are crashing a lot. Also, you are getting errors such as these:
Code:
Event[13]: Log Name: System Source: Service Control Manager Date: 2010-10-19T11:00:54.281 Event ID: 7022 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: W31-4L13NW4R3 Description: The Windows Update service hung on starting. ~~~~~ Event[32]: Log Name: System Source: Service Control Manager Date: 2010-10-19T10:57:10.538 Event ID: 7024 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: W31-4L13NW4R3 Description: The HomeGroup Listener service terminated with service-specific error %%-2147023143. ~~~~ Event[76]: Log Name: System Source: Service Control Manager Date: 2010-10-19T10:55:53.109 Event ID: 7024 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: W31-4L13NW4R3 Description: The Windows Firewall service terminated with service-specific error Access is denied.. ~~~~ Event[136]: Log Name: System Source: Microsoft Antimalware Date: 2010-10-19T10:55:39.000 Event ID: 2004 Task: N/A Level: Error Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: W31-4L13NW4R3 Description: Microsoft Antimalware has encountered an error trying to load signatures and will attempt reverting back to a known-good set of signatures. Signatures Attempted: Current Error Code: 0x80070002 Error description: The system cannot find the file specified. Signature version: 0.0.0.0;0.0.0.0 Engine version: 0.0.0.0 ~~~ Event[505]: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2010-10-19T02:14:12.496 Event ID: 20 Task: Windows Update Agent Level: Error Opcode: Installation Keyword: Installation,Failure User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: W31-4L13NW4R3 Description: Installation Failure: Windows failed to install the following update with error 0x800f020b: Broadcom - Bus Controllers and Ports - Dell Wireless 370 Bluetooth Mini-card.
Your Intel Ethernet drivers are old, dated 6/23/2009. That could be the problem. Install these ones: http://downloadcenter.intel.com/Deta...=3244&lang=eng
Dated 07/29/2010, they are 13 months newer.
Explorer.exe crashed too, though we may overlook this for now. Just run a system files check. Run sfc /scannow from an elevated command prompt.
You're also getting quite a few Kernel Power error 41 events.
Code:
Event[3127]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2010-09-17T21:15:00.736 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: W31-4L13NW4R3 Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
In short, update those network drivers, and upload the memory.dmp file. Disable any cleaning programs for now.
What is the page file set to? I see the page file is 7.99GB, for your 8GB RAM. Did you set it this way, or is the page file set to System Managed? Make sure it is the latter.
I don't quite get this part.
How can I check the settings ?
The logs also indicate that the memory.dmp file was updated, which may be our key here. Find that file in C:\Windows, and move it to the desktop. Right-click on it, and select Send to>Compressed folder.
I've tried to look for it but so far I have no luck.
In short, update those network drivers, and upload the memory.dmp file. Disable any cleaning programs for now.
I have updated the network drivers.
I do have Revo Uninstaller installed on my system.
Is this the cleaning program that you are referring to ?
Thank yo so much for your help
I don't quite get this part.
How can I check the settings ?
The logs also indicate that the memory.dmp file was updated, which may be our key here. Find that file in C:\Windows, and move it to the desktop. Right-click on it, and select Send to>Compressed folder.
I've tried to look for it but so far I have no luck.
In short, update those network drivers, and upload the memory.dmp file. Disable any cleaning programs for now.
I have updated the network drivers.
I do have Revo Uninstaller installed on my system.
Is this the cleaning program that you are referring to ?
Thank yo so much for your help
I was thinking of programs like CCleaner, that clean up temporary files, and more relevantly, memory dumps. Revo includes a cleaning function, I believe. Go ahead and remove Revo for now...you can always reinstall it later.
Do you run the Disk Cleanup tool at all? That would also delete memory dumps.
To check page file, first, go to Control Panel>System.
Do you run the Disk Cleanup tool at all? That would also delete memory dumps.
To check page file, first, go to Control Panel>System.
Quote:
In the left pane, click Advanced system settings. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
On the Advanced tab, under Performance, click Settings.
Click the Advanced tab, and then, under Virtual memory, click Change.
Check the Automatically manage paging file size for all drives check box.
On the Advanced tab, under Performance, click Settings.
Click the Advanced tab, and then, under Virtual memory, click Change.
Check the Automatically manage paging file size for all drives check box.
�� Quote: Originally Posted by Lancaster I was thinking of programs like CCleaner, that clean up temporary files, and more relevantly, memory dumps. Revo includes a cleaning function, I believe. Go ahead and remove Revo for now...you can always reinstall it later.
Do you run the Disk Cleanup tool at all? That would also delete memory dumps.
To check page file, first, go to Control Panel>System.
Do you run the Disk Cleanup tool at all? That would also delete memory dumps.
To check page file, first, go to Control Panel>System.
Quote:
In the left pane, click Advanced system settings. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
On the Advanced tab, under Performance, click Settings.
Click the Advanced tab, and then, under Virtual memory, click Change.
Check the Automatically manage paging file size for all drives check box.
On the Advanced tab, under Performance, click Settings.
Click the Advanced tab, and then, under Virtual memory, click Change.
Check the Automatically manage paging file size for all drives check box.
I have check the Page File and the automatically manage paging file size box have already been checked.
Remove Revo, or at least turn off its cleaning features. If you get another BSOD, immediately check for a minidump or full dump.
�� Quote: Originally Posted by Lancaster Remove Revo, or at least turn off its cleaning features. If you get another BSOD, immediately check for a minidump or full dump.
According to all the reports that you can get your hands on, what do you think caused the BSOD ?
Looking at an early post in this thread, by Carl: http://www.sevenforums.com/crashes-d...tml#post923576
A Windows network driver was blamed.
Without reading through the thread, I independently came to a network card issue: http://www.sevenforums.com/crashes-d...ml#post1023069
That's the closest I can come at this point.
I also see regi still: I see that was pointed out as a suspect driver earlier. You must have removed the regi.sys file, but since YouCam is still installed, it is throwing errors.
Please uninstall Youcam.
A Windows network driver was blamed.
Without reading through the thread, I independently came to a network card issue: http://www.sevenforums.com/crashes-d...ml#post1023069
That's the closest I can come at this point.
I also see regi still:
Code:
Event[61]: Log Name: System Source: Service Control Manager Date: 2010-10-19T10:55:58.271 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: W31-4L13NW4R3 Description: The regi service failed to start due to the following error: The system cannot find the file specified.
Please uninstall Youcam.
�� Quote: Originally Posted by Lancaster A Windows network driver was blamed.
Without reading through the thread, I independently came to a network card issue: http://www.sevenforums.com/crashes-d...ml#post1023069
That's the closest I can come at this point.
I see that was pointed out as a suspect driver earlier. You must have removed the regi.sys file, but since YouCam is still installed, it is throwing errors.
Please uninstall Youcam.
What should I do ?
Are you suggesting that I should not install YouCam or should I install a newer version?
Because without the YouCam, I will not be able to use my webcam.
Having said that, I almost never used my webcam, so how can it triggered BSOD error if we did not even execute it ?
My latest and a few BSODs before that, happened when I did not do anything with my system, I simply just ran Bittorent o the background, that's it.
When I found out, my system was restarted.
What do you think have caused this ?
Thank you
You should install a newer version - if it is compatible with Win 7. I had to ditch my webcam when I installed Win 7. Whether you use the webcam frequently or not, it is installed on your system and your system loads the drivers.
�� Quote: Originally Posted by CarlTR6 You should install a newer version - if it is compatible with Win 7. I had to ditch my webcam when I installed Win 7. Whether you use the webcam frequently or not, it is installed on your system and your system loads the drivers.
Hopefully it will fix my problem.
Thank you
After a while, I experienced another BSOD this morning.
Hello,
Could you test your hard drive with SeaTools?
...Summary of the dumps:
Could you test your hard drive with SeaTools?
...Summary of the dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Dec 22 20:26:50.644 2010 (UTC - 5:00) System Uptime: 0 days 4:55:49.049 *** WARNING: Unable to verify timestamp for iaStor.sys *** ERROR: Module load completed but symbols could not be loaded for iaStor.sys Probably caused by : iaStor.sys ( iaStor+52a14 ) BUGCHECK_STR: 0x4E_7 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x4E_7_iaStor+52a14 ��������������������������������������������������������������������������������������``
I have tried the Seatools to check my hard drive and it passed everything.
This is almost certainly caused by hardware, sawwei. Just to make sure, enable driver verifier:
Driver Verifier - Enable and Disable
Run Prime95: http://www.sevenforums.com/tutorials...t-prime95.html
Driver Verifier - Enable and Disable
Run Prime95: http://www.sevenforums.com/tutorials...t-prime95.html
Không có nhận xét nào:
Đăng nhận xét