Hello
First of all I would like to say that I would be very great full at whoever can help me.
I have received over 50 blue screen errors due to "Ntoskrnl.exe"
I have windows 7 ultimate-64bit and do not have a instilation disk.
WHat could I do
MAny Thanks
First of all I would like to say that I would be very great full at whoever can help me.
I have received over 50 blue screen errors due to "Ntoskrnl.exe"
I have windows 7 ultimate-64bit and do not have a instilation disk.
WHat could I do
MAny Thanks
Hi, and welcome to the forum. Please read this thread, follow the instructions and post back. We will be glad to help you.
http://www.sevenforums.com/crashes-d...tructions.html
http://www.sevenforums.com/crashes-d...tructions.html
here are the files you have requested
Thanks for uploading the files. Please turn off Driver Verifier. The Driver Verifier enable dumps are pointing Widows system driver which are very unlikely to be the cause. Upload the next non-Driver Verifier dump that you get.
I find some outdated drivers load on your system. Older drivers can and do cause memory corruption and BSOD's. Update these drivers.
How to update drivers -
Please post if you need help with the drivers. After you update them, reboot and let's see how your system does.
I find some outdated drivers load on your system. Older drivers can and do cause memory corruption and BSOD's. Update these drivers.
Quote:
ALSysIO64.sys Sun Apr 19 15:41:04 2009 - Core Temp - CPU temperature monitorCore Temp
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ALPHA Filter Driver, Alpha Networks Inc
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - KMWDFilter Driver from UASSOFT.COM. I think this is a wireless mouse driver. from Kensington? Keyboard Software Home Page
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ALPHA Filter Driver, Alpha Networks Inc
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - KMWDFilter Driver from UASSOFT.COM. I think this is a wireless mouse driver. from Kensington? Keyboard Software Home Page
Quote:
The anodlwfx.sys driver may belong to an antivirus program and is likely to be causing problems.
Please go to C:\Windows\System32\drivers and locate the anodlwfs.sys driver there. Right click on it, select Properties, then select the Details tab.
Then please let us know the information about the File description and product name (to help us in identifying the source of this driver).
Please go to C:\Windows\System32\drivers and locate the anodlwfs.sys driver there. Right click on it, select Properties, then select the Details tab.
Then please let us know the information about the File description and product name (to help us in identifying the source of this driver).
Quote:
- I have listed links to most of the drivers in the code box above. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Please post if you need help with the drivers. After you update them, reboot and let's see how your system does.
Hello again,
I have attached the details about anodlwfx.sys named "driva"
I have installed the latest version of coretemp
KMWDFILTER.sys drive however i do not kno... My keyboard is "trust" branded and i have installed the latest drivers
Once again thanks for your help
what else would you like me to do
I have attached the details about anodlwfx.sys named "driva"
I have installed the latest version of coretemp
KMWDFILTER.sys drive however i do not kno... My keyboard is "trust" branded and i have installed the latest drivers
Once again thanks for your help
what else would you like me to do
Thank you for the details. Did you try to update that driver above?
I am not sure how to update the driver.
I have received anothe BSOD named ntoskrnl yet again.
thanks for all your help
I have received anothe BSOD named ntoskrnl yet again.
thanks for all your help
Alpha Networks, Inc is a spin of from D-Link. Here is their website: Alpha Networks Inc.. I did not tske the time to see if they have drivers you can download; but you can explore the site. You can also try the D-Link website: D-Link - Home & Home Office.
Please upload your latest dump file. ntoskrnl is a Windows system core file. It is very unlikely to be the real cause. When DBug can't find an exact cause, it has to blame the crash on something.
Please upload your latest dump file. ntoskrnl is a Windows system core file. It is very unlikely to be the real cause. When DBug can't find an exact cause, it has to blame the crash on something.
i have updated the driver..i think.. it is a DWA-140 D-link usb wireless
is there anything else i need to do
thank y ou very much
is there anything else i need to do
thank y ou very much
i also get application cannot run in win32 mode??? could you help me on this?
many thanks
many thanks
What is the application? You might get a better answer if you start a new thread about the application in Software Section: Software - Windows 7 Forums
How is your system doing? Any more BSOD's?
How is your system doing? Any more BSOD's?
yeah i have had 4 mode BSOD's with the file name win32k ???any ideas
Win32K is a Windows file and not likely the real cause. Please upload the dumps and we will take a look.
hi,
is ther any chance that the keyboard could be the cause?
is ther any chance that the keyboard could be the cause?
There is a chance most anything could be the cause. Please upload the dumps and will see what they show.
the crash files
I looked at your three latest dumps. All are indicating memory corruption. The out of date drivers I listed in a previous post are still loading on your system. Update these drivers.
To answer your question, I think your keyboard or your mouse could be involved in the crashes due to the out of date driver, KMWDFILTER.sys. Have you tried to update this driver from the Kensington? I did not see a keyboard listed for Win 7. Is your keyboard a Kensington keyboard? What kind of mouse do you have?
Quote:
ALSysIO64.sys Sun Apr 19 15:41:04 2009 - Core Temp - CPU temperature monitorCore Temp
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ALPHA Filter Driver, Alpha Networks Inc. This company is a spin off from D-Link. I know you have a D-Link range booster and that may be where this driver comes from. See if you can update the driver from D-Link.
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - KMWDFilter Driver from UASSOFT.COM. I think this is a wireless mouse driver. from Kensington? Keyboard Software Home Page
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ALPHA Filter Driver, Alpha Networks Inc. This company is a spin off from D-Link. I know you have a D-Link range booster and that may be where this driver comes from. See if you can update the driver from D-Link.
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - KMWDFilter Driver from UASSOFT.COM. I think this is a wireless mouse driver. from Kensington? Keyboard Software Home Page
Code:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`03249000 PsLoadedModuleList = 0xfffff800`03486e50 Debug session time: Tue Nov 16 14:49:28.041 2010 (GMT-5) System Uptime: 0 days 1:27:06.039 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff96000104540, fffff880062b1bb0, 0} Probably caused by : win32k.sys ( win32k!xxxClearWakeMask+24 ) Followup: MachineOwner --------- 4: 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: fffff96000104540, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880062b1bb0, 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!xxxClearWakeMask+24 fffff960`00104540 488b8370010000 mov rax,qword ptr [rbx+170h] CONTEXT: fffff880062b1bb0 -- (.cxr 0xfffff880062b1bb0) rax=000000000f99a027 rbx=f7fff900c3258010 rcx=00004fbe317e5b28 rdx=0000000000000004 rsi=000000000248f9e0 rdi=0000000000000003 rip=fffff96000104540 rsp=fffff880062b2580 rbp=fffff880062b2660 r8=fffff80003249000 r9=0000000000000000 r10=ffffffffffffffef r11=fffff880009b2101 r12=0000000000000000 r13=0000000000000000 r14=00000000ffffffff r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 win32k!xxxClearWakeMask+0x24: fffff960`00104540 488b8370010000 mov rax,qword ptr [rbx+170h] ds:002b:f7fff900`c3258180=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff96000104540 STACK_TEXT: fffff880`062b2580 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxClearWakeMask+0x24 FOLLOWUP_IP: win32k!xxxClearWakeMask+24 fffff960`00104540 488b8370010000 mov rax,qword ptr [rbx+170h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!xxxClearWakeMask+24 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c7dc13c STACK_COMMAND: .cxr 0xfffff880062b1bb0 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!xxxClearWakeMask+24 BUCKET_ID: X64_0x3B_win32k!xxxClearWakeMask+24 Followup: MachineOwner --------- 4: kd> lmtsmn start end module name fffff880`00f95000 fffff880`00fec000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02a00000 fffff880`02a8a000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`03e87000 fffff880`03e9d000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`0839a000 fffff880`083a2000 ALSysIO64 ALSysIO64.sys Sun Apr 19 15:41:04 2009 (49EB7E50) fffff880`04114000 fffff880`04129000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00dcc000 fffff880`00dd7000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`03f2c000 fffff880`03f35000 anodlwfx anodlwfx.sys Fri Mar 06 05:10:08 2009 (49B0F680) fffff880`00d99000 fffff880`00da2000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00da2000 fffff880`00dcc000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff960`00900000 fffff960`00961000 ATMFD ATMFD.DLL Thu May 27 00:11:31 2010 (4BFDF0F3) fffff880`02b4e000 fffff880`02b55000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`040dd000 fffff880`040ee000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`064dc000 fffff880`064fa000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00790000 fffff960`007b7000 cdd cdd.dll Wed May 19 15:48:26 2010 (4BF4408A) fffff880`02aee000 fffff880`02b18000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00cbf000 fffff880`00d7f000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`010bf000 fffff880`010ef000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00c61000 fffff880`00cbf000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01000000 fffff880`01073000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`03e77000 fffff880`03e87000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`05af8000 fffff880`05b06000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`0403c000 fffff880`040bf000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`040bf000 fffff880`040dd000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03e68000 fffff880`03e77000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01209000 fffff880`0121f000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`03af3000 fffff880`03bed000 Dnetr28ux Dnetr28ux.sys Wed Aug 05 09:59:46 2009 (4A799052) fffff880`05ac4000 fffff880`05ae6000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`05b12000 fffff880`05b1b000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05b06000 fffff880`05b12000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05b1b000 fffff880`05b2e000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`05aec000 fffff880`05af8000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`148c0000 fffff880`149b4000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`149b4000 fffff880`149fa000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`08364000 fffff880`0839a000 fastfat fastfat.SYS Mon Jul 13 19:23:28 2009 (4A5BC1F0) fffff880`13c1c000 fffff880`13c29000 fdc fdc.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6) fffff880`0113f000 fffff880`01153000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`0425a000 fffff880`04265000 flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6) fffff880`010f3000 fffff880`0113f000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`013ee000 fffff880`013f8000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`00c00000 fffff880`00c3a000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`0148b000 fffff880`014d5000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`03200000 fffff800`03249000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`04000000 fffff880`04024000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`05b59000 fffff880`05b72000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`05b72000 fffff880`05b7a080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`05b4b000 fffff880`05b59000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`06414000 fffff880`064dc000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`01200000 fffff880`01209000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`0431e000 fffff880`0432d000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`05b87000 fffff880`05b95000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00baa000 fffff800`00bb4000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`05b7b000 fffff880`05b87000 KMWDFILTER KMWDFILTER.sys Wed Apr 29 02:20:48 2009 (49F7F1C0) fffff880`0433e000 fffff880`04381000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9) fffff880`013c3000 fffff880`013dd000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01460000 fffff880`0148b000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`05ae6000 fffff880`05aeb200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`03a6d000 fffff880`03a82000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`03a29000 fffff880`03a4c000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c40000 fffff880`00c4d000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`03a00000 fffff880`03a0e000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`0432d000 fffff880`0433c000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`05b95000 fffff880`05ba2000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00d7f000 fffff880`00d99000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02b18000 fffff880`02b45000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`064fa000 fffff880`06512000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`06512000 fffff880`0653f000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`0653f000 fffff880`0658d000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`0658d000 fffff880`065b0000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`02bb3000 fffff880`02bbe000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00ff5000 fffff880`00fff000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01160000 fffff880`011be000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03e5d000 fffff880`03e68000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`015ea000 fffff880`015fc000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`014d9000 fffff880`015cb000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04030000 fffff880`0403c000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`03ad5000 fffff880`03ae8000 ndisuio ndisuio.sys Mon Jul 13 20:09:25 2009 (4A5BCCB5) fffff880`0428e000 fffff880`042bd000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`04265000 fffff880`0427a000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`03f35000 fffff880`03f44000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02a8a000 fffff880`02acf000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01400000 fffff880`01460000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`02bbe000 fffff880`02bcf000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03e51000 fffff880`03e5d000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`03249000 fffff800`03825000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01220000 fffff880`013c3000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`02b45000 fffff880`02b4e000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`148be000 fffff880`148bf180 nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA) fffff880`13c2c000 fffff880`148bde00 nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E) fffff880`03a82000 fffff880`03ad5000 nwifi nwifi.sys Mon Jul 13 20:07:23 2009 (4A5BCC3B) fffff880`03edc000 fffff880`03f02000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`041df000 fffff880`041fc000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00e40000 fffff880`00e55000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e00000 fffff880`00e33000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00ec6000 fffff880`00ecd000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00ecd000 fffff880`00edd000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`013dd000 fffff880`013ee000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`07ebb000 fffff880`07f61000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`05a87000 fffff880`05ac4000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c4d000 fffff880`00c61000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`01153000 fffff880`0115f040 PxHlpa64 PxHlpa64.sys Tue Oct 20 14:08:42 2009 (4ADDFCAA) fffff880`03e9d000 fffff880`03ec1000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`042bd000 fffff880`042d8000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`042d8000 fffff880`042f9000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`042f9000 fffff880`04313000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03e00000 fffff880`03e51000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`04313000 fffff880`0431e000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`02b98000 fffff880`02ba1000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02ba1000 fffff880`02baa000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02baa000 fffff880`02bb3000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`011be000 fffff880`011f8000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`05ba2000 fffff880`05bba000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04132000 fffff880`04189000 Rt64win7 Rt64win7.sys Fri Sep 03 01:58:32 2010 (4C808E88) fffff880`05869000 fffff880`05a86300 RTKVHD64 RTKVHD64.sys Tue Dec 08 05:20:05 2009 (4B1E2855) fffff880`07f61000 fffff880`07f6c000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`04024000 fffff880`04030000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`03f44000 fffff880`03f61000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`015e3000 fffff880`015ea000 speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798) fffff880`015db000 fffff880`015e3000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`082ce000 fffff880`08364000 srv srv.sys Thu Aug 26 23:38:00 2010 (4C773318) fffff880`07e00000 fffff880`07e67000 srv2 srv2.sys Thu Aug 26 23:37:46 2010 (4C77330A) fffff880`07f6c000 fffff880`07f99000 srvnet srvnet.sys Thu Aug 26 23:37:24 2010 (4C7732F4) fffff880`0433c000 fffff880`0433d480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01602000 fffff880`017ff000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`07f99000 fffff880`07fab000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`02bed000 fffff880`02bfa000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02bcf000 fffff880`02bed000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03fd3000 fffff880`03fe7000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00460000 fffff960`0046a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`040ee000 fffff880`04114000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`04381000 fffff880`04393000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`05b2e000 fffff880`05b4b000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`043bf000 fffff880`043c0f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`13c0b000 fffff880`13c1c000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04200000 fffff880`0425a000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`13c00000 fffff880`13c0b000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04189000 fffff880`041df000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`043b0000 fffff880`043bf000 usbrpm usbrpm.sys Mon Jul 13 20:35:14 2009 (4A5BD2C2) fffff880`03a0e000 fffff880`03a29000 USBSTOR USBSTOR.SYS Mon Jul 13 20:06:34 2009 (4A5BCC0A) fffff880`00e33000 fffff880`00e40000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`02b55000 fffff880`02b63000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`02b63000 fffff880`02b88000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`015cb000 fffff880`015db000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00e55000 fffff880`00e6a000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e6a000 fffff880`00ec6000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01073000 fffff880`010bf000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`043c1000 fffff880`043fd000 vpchbus vpchbus.sys Tue Sep 22 21:32:32 2009 (4AB97AB0) fffff880`03f18000 fffff880`03f2c000 vpcnfltr vpcnfltr.sys Tue Sep 22 21:32:30 2009 (4AB97AAE) fffff880`04393000 fffff880`043b0000 vpcusb vpcusb.sys Tue Sep 22 21:32:39 2009 (4AB97AB7) fffff880`03f7c000 fffff880`03fd2580 vpcvmm vpcvmm.sys Thu Dec 31 02:27:33 2009 (4B3C5265) fffff880`03bed000 fffff880`03bfa000 vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39) fffff880`03f02000 fffff880`03f18000 vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A) fffff880`03f61000 fffff880`03f7c000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`02b88000 fffff880`02b98000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00ee2000 fffff880`00f86000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f86000 fffff880`00f95000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02acf000 fffff880`02ad8000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00030000 fffff960`0033f000 win32k win32k.sys Tue Aug 31 22:58:04 2010 (4C7DC13C) fffff880`04129000 fffff880`04132000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00fec000 fffff880`00ff5000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`03a4c000 fffff880`03a6d000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`08200000 fffff880`08271000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`00dd7000 fffff880`00de5000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`00de5000 fffff880`00df1000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`00df1000 fffff880`00dfa000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`02adb000 fffff880`02aee000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Debug session time: Sun Nov 14 15:59:06.302 2010 (GMT-5) System Uptime: 0 days 0:11:03.300 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck DE, {2, fffff8a009daaab0, f7fff8a009daaab1, 3025868c0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d260 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* POOL_CORRUPTION_IN_FILE_AREA (de) A driver corrupted pool memory used for holding pages destined for disk. This was discovered by the memory manager when dereferencing the file. Arguments: Arg1: 0000000000000002 Arg2: fffff8a009daaab0 Arg3: f7fff8a009daaab1 Arg4: 00000003025868c0 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xDE PROCESS_NAME: MpSigStub.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800032783f3 to fffff800032d3740 STACK_TEXT: fffff880`097e2d58 fffff800`032783f3 : 00000000`000000de 00000000`00000002 fffff8a0`09daaab0 f7fff8a0`09daaab1 : nt!KeBugCheckEx fffff880`097e2d60 fffff800`032b8b82 : 00000000`00000000 fffffa80`0dde7e00 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2d260 fffff880`097e2e50 fffff880`012ba447 : fffffa80`0d77f958 00000000`00000000 fffff8a0`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172 fffff880`097e2ec0 fffff880`012d3c0a : fffff880`097e3730 fffff8a0`091d7b40 fffff8a0`090f7140 fffff880`097e31bc : Ntfs!NtfsDeleteFile+0x57b fffff880`097e3140 fffff880`01241aa9 : fffffa80`0da37c68 fffffa80`0da37c68 fffff880`097e3690 fffff880`097d2000 : Ntfs!NtfsCommonCleanup+0x15da fffff880`097e3550 fffff800`032e2e5a : fffff880`097e3690 fffffa80`0da27d60 fffff8a0`02e1a4e8 00000000`00000000 : Ntfs!NtfsCommonCleanupCallout+0x19 fffff880`097e3580 fffff880`01241662 : fffff880`01241a90 fffff880`097e3690 fffff880`097e3900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda fffff880`097e3660 fffff880`012e3244 : fffff880`097e3730 fffff880`097e3730 fffff880`097e3730 00000000`00000000 : Ntfs!NtfsCommonCleanupOnNewStack+0x42 fffff880`097e36d0 fffff880`010f223f : fffff880`097e3730 fffffa80`0dcb4010 fffffa80`0dcb43b0 fffffa80`0d4aac30 : Ntfs!NtfsFsdCleanup+0x144 fffff880`097e3940 fffff880`010f06df : fffffa80`0d9af8e0 00000000`00000000 fffffa80`0d8a5b00 fffffa80`0dcb4010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`097e39d0 fffff800`035e9a0f : fffffa80`0dcb4010 fffffa80`0ce6ab30 00000000`00000000 fffffa80`0d825890 : fltmgr!FltpDispatch+0xcf fffff880`097e3a30 fffff800`035cfa24 : 00000000`00000000 fffffa80`0ce6ab30 fffffa80`0dcb0100 fffffa80`0d825890 : nt!IopCloseFile+0x11f fffff880`097e3ac0 fffff800`035e9501 : fffffa80`0ce6ab30 fffffa80`00000001 fffff8a0`092d3620 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4 fffff880`097e3b40 fffff800`035e9414 : 00000000`00000144 fffffa80`0ce6ab30 fffff8a0`092d3620 00000000`00000144 : nt!ObpCloseHandleTableEntry+0xb1 fffff880`097e3bd0 fffff800`032d2993 : fffffa80`0d85db60 fffff880`097e3ca0 00000000`00000000 fffffa80`0d1908e0 : nt!ObpCloseHandle+0x94 fffff880`097e3c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+2d260 fffff800`032783f3 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2d260 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0xDE_nt!_??_::FNODOBFM::_string_+2d260 BUCKET_ID: X64_0xDE_nt!_??_::FNODOBFM::_string_+2d260 Followup: MachineOwner --------- Trust.com - ComfortLine Mouse -- my mouse
Trust.com - Multimedia Scroll Keyboard KB-2200 -- my keyboard (changed it yesterday due to old one
not working anymore)
Trust.com - Multimedia Scroll Keyboard KB-2200 -- my keyboard (changed it yesterday due to old one
not working anymore)
�� Quote: Originally Posted by cemcilfa 
Trust.com - ComfortLine Mouse -- my mouse
Trust.com - Multimedia Scroll Keyboard KB-2200 -- my keyboard (changed it yesterday due to old one
not working anymore)
Trust.com - Multimedia Scroll Keyboard KB-2200 -- my keyboard (changed it yesterday due to old one
not working anymore)
Quote:
Where can I get software/drivers for my Trust product? This product doesn't need any software/drivers to function.Just connect and the product should work
It looks like your keyboard drivers are up to date. Your keyboard uses the same drivers for Vista and Win 7. Here is where you download drivers for your keyboard: Trust.com - Multimedia Scroll Keyboard KB-2200
Is this your current keyboard or is this the one you replaced?
�� Quote: Originally Posted by cemcilfa what if i use driver robot to update my drivers??? I do not know how to update drivers
1. Update drivers through Windows Updates.
2. Update drivers through Device Manager.
3. Update drivers through a third party program (not generally recommended).
4. Update drivers by downloading them from the respective manufacturers' websites and install them yourself. This is what we generally recommend.
Here is how to update drivers:
1. go to the manufacturer's webpage of the software or hardware fo which you are updating the driver. For example, if you were updating your video card drivers, you would go to NVidia's website. If you were updating chipset drivers, you would go to your motherboard manufacturer's website.
2. Download the latest drivers to your desktop. This will generally be a zipped file. Extract the zipped files contents to a folder on your desktop.
3. If there is an .exe file in that folder, click on it and it will install the drivers.
4. If there is no .exe file, open Device Manager and find the device you are trying to update. For example, let's say it is your video card. In Device manger, you would click on the arrow to the left of Display adapters. Now right click on your NVidia graphics card adapter and click on Properties. Click on the Driver tab. Click on the Update Driver button. Now click on Browse my computer for driver software. Enter the path to the folder on your desktop and click Next.
For your Core Temp driver, ALSysIO64.sys, go here and install the latest version of the Core Temp: Core Temp. You may already have the latest driver available. If you do, it should not be a problem.
If you have installed a new Keyboard, run your system and let's see how it does. If you get another BSOD, upload the dump and we will test hardware and enable Driver Verifier. But we may not need to do that . Let's see if the changes you have made solved the problem.
hello again,
Just received another bsod
. This time the code was "fltmgr.sys" and all these problems started when I installed norton a while back.
Thank you
Just received another bsod
. This time the code was "fltmgr.sys" and all these problems started when I installed norton a while back.Thank you
Do you still have Norton installed? I do not see any of its drivers.
yeah, when I first purchased this pc, I installed the chipset driviers via a instilation disc, roughly a week later i found out that there was a trial version or norton, so I installed it, ever since that day I have been receiving these BSOD's.
Thank you
Thank you
SYMTDIV.SYS , yet another BSOD
So i uninstalled, reinstalled,uninstalled and then reinstalled norton, I have a fealing that norton is the cause of all this horrible mess. how do you think I could compleatly remove norton, because I have researched that norton uninstaller does not compleatly remove it.
Yet again, Thank you
Yet again, Thank you
SYMTDIV.SYS (Network Dispatch Driver/Symantec ...
Best solution Uninstall symantec and use Microsoft Security Essentials instead...
Download Revo Uninstaller
Best solution Uninstall symantec and use Microsoft Security Essentials instead...
Download Revo Uninstaller
Thanks, I have uninstalled it compleatly now,
I will let you know of any future BSOD's
I will let you know of any future BSOD's
Fingers crossed...
Tews is spot on. Norton is a known and documented cause of BSOD's on some Win 7 systems. Here is the removal tool for getting rid of it completely: Tool. I hope your BSOD's are behind you.
Another BSOD.. ,,,dxgmms1.sys
I have posted the dump files
,,,dxgmms1.sysI have posted the dump files
It is another error code 3B. dxgmms1.sys is a Windows Direct X driver and most likely not the real cause. I still see this outdated driver on your system: It appears to be a security program that I suspect is interfering with your graphics and Direct X. Uninstall this software. If you cannot find the software in Programs and Features, download Revo Uninstaller (free) and see if Revo finds it. If it does, uninstall the software. Otherwise, using Windows Explorer, navigate to C:\Windows\system32\DRIVERS, locate this driver and rename it from .sys to .old. Reboot and the driver will not load.
You also still have this obsolete XP driver loading on your system. This is XP hardware is not going to work with Win 7. If you have a new mouse, rename this driver in the manner described above.
It looks like you have updated the rest of your drivers.
Quote:
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ALPHA Filter Driver, ANOD network security, Alpha Networks Inc (D-Link subsidiary).
You also still have this obsolete XP driver loading on your system. This is XP hardware is not going to work with Win 7.
Quote:
KMWDFILTER.sys Thu Mar 29 03:00:40 2007 - wireless mouse driver from Trust MI-4950R/TRUST MI-7700R or Medion, or Tevion mouse. Update this mouse driver or upgrade to a new mouse compatible with Win 7.
It looks like you have updated the rest of your drivers.
My mouse- Trust.com - ComfortLine Mouse -is windows 7 compatible. Is there any way In which you could tell me what the windows xp driver or software is, so I can uninstall it.
I have Windows security Essentials now that I have removed Norton Using the like you provided
Thanks
I have Windows security Essentials now that I have removed Norton Using the like you provided
Thanks
Since I am not sure what this driver is for and you have a Win 7 compatible mouse, create a restore point or a system image or both. Navigate to C:\Windows\System32\Drivers, locate KMWDFILTER.sys and rename it from .sys to .old. Reboot and it will not load. This will break whatever hardware or software it is associated with.
I have done what you have told me to do. My mouse was disconnected from my pc when i changed the sys. to .old
Now I am really confused, because my mouse says it is windows 7 compatible
Now I am really confused, because my mouse says it is windows 7 compatible
That driver is apparently not Windows 7 compatible. Do you have another mouse you can try while you rename that driver to .old? I would like to see how your system runs without that driver; then we will know. If your mouse depends on that driver, I have my doubts that it is Win 7 compatible.
Is the East tune 6 levels ideal???
Received another Bsod, but this time, it took a much longer time period
Received another Bsod, but this time, it took a much longer time period
Those levels look fine; but I am not a hardware expert. The biggest problem I can see at this time is outdated drivers. Try and other mouse and rename that mouse driver to old. Update the following drivers or uninstall the software.
Follow the above suggestions and see if this helps your system. Post back and let us know.
Quote:
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ALPHA Filter Driver, ANOD network security, Alpha Networks Inc (D-Link subsidiary). Update this driver or uninstall the securityy program or rename the driver.
AODDriver.sys Mon Oct 13 00:38:55 2008 - AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Drivers & Support | GAME.AMD.COM. Uninstall this software.
gdrv.sys Thu Mar 12 23:22:29 2009 - Known problem with Win 7. GIGABYTE Tools - Windows (R) Server 2003 DDK driver; belongs to EasySaver. Uninstall EasySaver.
GVTDrv64.sys Tue Sep 05 03:10:02 2006 - Gigabyte EasyTune6 driver (known issues w/Win7), GIGABYTE - Support & Downloads - Utility - Motherboard. This is XP software; uninstall.
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - wireless mouse driver from Trust MI-4950R/TRUST MI-7700R or Medion, or Tevion mouse. Update this mouse driver or upgrade to a new mouse compatible with Win 7. Try another mouse and rename the driver.
AODDriver.sys Mon Oct 13 00:38:55 2008 - AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Drivers & Support | GAME.AMD.COM. Uninstall this software.
gdrv.sys Thu Mar 12 23:22:29 2009 - Known problem with Win 7. GIGABYTE Tools - Windows (R) Server 2003 DDK driver; belongs to EasySaver. Uninstall EasySaver.
GVTDrv64.sys Tue Sep 05 03:10:02 2006 - Gigabyte EasyTune6 driver (known issues w/Win7), GIGABYTE - Support & Downloads - Utility - Motherboard. This is XP software; uninstall.
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - wireless mouse driver from Trust MI-4950R/TRUST MI-7700R or Medion, or Tevion mouse. Update this mouse driver or upgrade to a new mouse compatible with Win 7. Try another mouse and rename the driver.
I have updated the d-link driver many times, yet is still says update driver???????
BSOS's starting to come on a regular basis???
BSOS's starting to come on a regular basis???
do i have to get a new mouse i have changes is to old as you told me earlier
i have changes is to old as you told me earlier Have you uninstalled Easy Saver and Easy Tune? If not uninstall them. Then lets see how your system runs. Your mouse driver is a Vista driver and it may work. The anodlwfx.sys driver is also a Vista driver. It may work; but the fact that it is a security driver raises a red flag. Let's see how your system does with Easy Saver and Easy Tune gone. Upload any dumps you get after you uninstall those two programs.
all of my other dumbs were without Easy tune and Energy saver. I feel that they have no relevance. But then again your the Pro.
are there any tests I could do and then send them to you?
I really want these BSOD's to go away
Many thanks
are there any tests I could do and then send them to you?
I really want these BSOD's to go away
Many thanks
Just uninstall those two obsolete programs and let's see how your system does. Maybe those Vista drivers will work OK. Troubleshooting is often a process of elimination. And you are very welcome. You will solve this thing.
Received BSOD's dump files are up
Thanks
Thanks
Quote:
Error code 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
Error code 34, CACHE_MANAGER. Usual causes: Insufficient physical memory, Indexing, Device driver.
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
Error code 34, CACHE_MANAGER. Usual causes: Insufficient physical memory, Indexing, Device driver.
Code:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`03268000 PsLoadedModuleList = 0xfffff800`034a5e50 Debug session time: Tue Nov 30 16:41:50.750 2010 (GMT-5) System Uptime: 0 days 6:12:33.092 Loading Kernel Symbols ............................................................... ................................................................ ................................. Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8000359e521, fffff88008bbd080, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+ec67 ) Followup: MachineOwner --------- 0: 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: fffff8000359e521, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88008bbd080, 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: nt! ?? ::NNGAKEGL::`string'+ec67 fffff800`0359e521 f0480fba2900 lock bts qword ptr [rcx],0 CONTEXT: fffff88008bbd080 -- (.cxr 0xfffff88008bbd080) rax=fffffa801017e6b0 rbx=0000000000000000 rcx=f7fff8a000d9a718 rdx=fffffa80116e64e0 rsi=fffffa80116e64e0 rdi=fffffa80116e64f0 rip=fffff8000359e521 rsp=fffff88008bbda50 rbp=fffffa80116e64c0 r8=fffff8a0026ac870 r9=0000000000000a1c r10=0000000000000a1c r11=fffff88008bbdb38 r12=f7fff8a000d9a5f0 r13=fffff80003268000 r14=0000000000000000 r15=fffff8a001f8a6a0 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt! ?? ::NNGAKEGL::`string'+0xec67: fffff800`0359e521 f0480fba2900 lock bts qword ptr [rcx],0 ds:002b:f7fff8a0`00d9a718=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800035d49dd to fffff8000359e521 STACK_TEXT: fffff880`08bbda50 fffff800`035d49dd : 00000000`00000000 fffffa80`10c53b30 fffffa80`116e64e0 fffff800`032dd8bc : nt! ?? ::NNGAKEGL::`string'+0xec67 fffff880`08bbdac0 fffff800`035ee501 : 00000000`00000000 fffffa80`00000000 fffff8a0`01f8a6a0 00000000`00000000 : nt!ObpDecrementHandleCount+0x6d fffff880`08bbdb40 fffff800`035ee414 : 00000000`00000a1c fffffa80`10c53b30 fffff8a0`01f8a6a0 00000000`00000a1c : nt!ObpCloseHandleTableEntry+0xb1 fffff880`08bbdbd0 fffff800`032d7993 : fffffa80`1017e6b0 fffff880`08bbdca0 00000000`00000000 00000000`00000000 : nt!ObpCloseHandle+0x94 fffff880`08bbdc20 00000000`7770fe4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`09eff448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7770fe4a FOLLOWUP_IP: nt! ?? ::NNGAKEGL::`string'+ec67 fffff800`0359e521 f0480fba2900 lock bts qword ptr [rcx],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+ec67 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff88008bbd080 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!_??_::NNGAKEGL::_string_+ec67 BUCKET_ID: X64_0x3B_nt!_??_::NNGAKEGL::_string_+ec67 Followup: MachineOwner --------- Debug session time: Thu Dec 2 04:02:22.658 2010 (GMT-5) System Uptime: 0 days 0:12:20.001 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80003230b6c, fffff88002f91fd8, fffff88002f91840} Probably caused by : cng.sys ( cng!GatherRandomKey+294 ) Followup: MachineOwner --------- 5: 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: fffff80003230b6c, The address that the exception occurred at Arg3: fffff88002f91fd8, Exception Record Address Arg4: fffff88002f91840, 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!ExpGetLookasideInformation+8c fffff800`03230b6c 0fb742c0 movzx eax,word ptr [rdx-40h] EXCEPTION_RECORD: fffff88002f91fd8 -- (.exr 0xfffff88002f91fd8) Cannot read Exception record @ fffff88002f91fd8 CONTEXT: fffff88002f91840 -- (.cxr 0xfffff88002f91840) rax=0000000000000110 rbx=0000000000000ff4 rcx=fffff8800c22a590 rdx=f7fff88002d65c40 rsi=0000000000000000 rdi=0000000000000001 rip=fffff80003230b6c rsp=fffff88002f92210 rbp=00000000000000a1 r8=fffff80003427720 r9=0000000000000000 r10=0000000000000000 r11=0000fffffffff000 r12=fffff88002f922e0 r13=0000000000000000 r14=000000000001fe90 r15=fffff88002f92840 iopl=0 nv up ei ng nz na pe cy cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010283 nt!ExpGetLookasideInformation+0x8c: fffff800`03230b6c 0fb742c0 movzx eax,word ptr [rdx-40h] ds:002b:f7fff880`02d65c00=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: NULL_DEREFERENCE PROCESS_NAME: System 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: 0000000000000000 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ba0e0 0000000000000000 FOLLOWUP_IP: cng!GatherRandomKey+294 fffff880`01108b04 85c0 test eax,eax BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff800035807bb to fffff80003230b6c STACK_TEXT: fffff880`02f92210 fffff800`035807bb : 00000000`00000000 fffff800`00000ff4 fffff880`02f922e0 00000000`00000000 : nt!ExpGetLookasideInformation+0x8c fffff880`02f922a0 fffff800`035811e5 : fffff8a0`0c354170 00000000`00000000 00000000`00000004 00000000`00000000 : nt!ExpQuerySystemInformation+0x15bc fffff880`02f92640 fffff800`03281993 : fffff8a0`0c370000 fffff800`0328093d 00000000`00000041 fffffa80`0d8bbe10 : nt!NtQuerySystemInformation+0x4d fffff880`02f92680 fffff800`0327df30 : fffff880`01108b04 00000000`00020000 fffff880`02f92844 fffff8a0`0c354148 : nt!KiSystemServiceCopyEnd+0x13 fffff880`02f92818 fffff880`01108b04 : 00000000`00020000 fffff880`02f92844 fffff8a0`0c354148 00000000`00000000 : nt!KiServiceLinkage fffff880`02f92820 fffff880`0110856d : fffffa80`0d8bbe10 00000000`00000000 fffff800`20206f49 fffff800`0328d2a1 : cng!GatherRandomKey+0x294 fffff880`02f92be0 fffff800`0357ec5d : 00000000`00000000 fffffa80`0d925820 fffffa80`0d925820 fffffa80`0ca8f040 : cng!scavengingWorkItemRoutine+0x3d fffff880`02f92c80 fffff800`0328f961 : fffff800`03427500 fffff800`0357ec20 fffffa80`0ca8f040 00000000`00000000 : nt!IopProcessWorkItem+0x3d fffff880`02f92cb0 fffff800`03526c06 : 00000000`00000000 fffffa80`0ca8f040 00000000`00000080 fffffa80`0ca7b040 : nt!ExpWorkerThread+0x111 fffff880`02f92d40 fffff800`03260c26 : fffff880`02ea4180 fffffa80`0ca8f040 fffff880`02eaf040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`02f92d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: cng!GatherRandomKey+294 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cng IMAGE_NAME: cng.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc814 STACK_COMMAND: .cxr 0xfffff88002f91840 ; kb FAILURE_BUCKET_ID: X64_0x7E_cng!GatherRandomKey+294 BUCKET_ID: X64_0x7E_cng!GatherRandomKey+294 Followup: MachineOwner --------- Debug session time: Thu Dec 2 03:09:53.744 2010 (GMT-5) System Uptime: 0 days 0:06:55.087 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 34, {50830, fffff880070b4718, fffff880070b3f80, fffff800032a3942} Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceObjectDeferDeleteWithTag+1e ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CACHE_MANAGER (34) See the comment for FAT_FILE_SYSTEM (0x23) Arguments: Arg1: 0000000000050830 Arg2: fffff880070b4718 Arg3: fffff880070b3f80 Arg4: fffff800032a3942 Debugging Details: ------------------ EXCEPTION_RECORD: fffff880070b4718 -- (.exr 0xfffff880070b4718) ExceptionAddress: fffff800032a3942 (nt!ObDereferenceObjectDeferDeleteWithTag+0x000000000000001e) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880070b3f80 -- (.cxr 0xfffff880070b3f80) rax=ffffffffffffffff rbx=fffffa80057fc030 rcx=f7fffa800e936070 rdx=00000000746c6644 rsi=0000000000000002 rdi=f7fffa800e936070 rip=fffff800032a3942 rsp=fffff880070b4950 rbp=fffffa800daed790 r8=00000000057fc030 r9=0000000000000000 r10=0000058000000000 r11=fffff880070b4988 r12=0000000000000002 r13=0000000000000000 r14=fffffa800d7e8f10 r15=fffffa800a3d3040 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!ObDereferenceObjectDeferDeleteWithTag+0x1e: fffff800`032a3942 f0480fc147d0 lock xadd qword ptr [rdi-30h],rax ds:002b:f7fffa80`0e936040=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_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 fffff800034b80e0 ffffffffffffffff FOLLOWUP_IP: nt!ObDereferenceObjectDeferDeleteWithTag+1e fffff800`032a3942 f0480fc147d0 lock xadd qword ptr [rdi-30h],rax FAULTING_IP: nt!ObDereferenceObjectDeferDeleteWithTag+1e fffff800`032a3942 f0480fc147d0 lock xadd qword ptr [rdi-30h],rax BUGCHECK_STR: 0x34 LAST_CONTROL_TRANSFER: from fffff80003271894 to fffff800032a3942 STACK_TEXT: fffff880`070b4950 fffff800`03271894 : fffffa80`057fc030 fffffa80`057fc030 ffffffff`ffffffff 00000000`00000002 : nt!ObDereferenceObjectDeferDeleteWithTag+0x1e fffff880`070b4990 fffff800`03227dd4 : fffffa80`0daed790 00000000`00000000 00000000`00000000 fffffa80`10dc4b60 : nt!MiWaitForInPageComplete+0x4e4 fffff880`070b4a70 fffff800`03227b7a : 00000000`00000000 00000000`00000000 fffff800`034255a0 00000000`00000000 : nt!MiPfCompletePrefetchIos+0x54 fffff880`070b4aa0 fffff800`03232ab5 : fffffa80`10dc4b60 00000000`88b00000 00000000`88b00000 fffff800`034255a0 : nt!MmWaitForCacheManagerPrefetch+0x1e fffff880`070b4ad0 fffff800`03274576 : fffffa80`0dbc17b0 fffffa80`10dc4b00 00000000`00000005 00000000`00000090 : nt!CcPerformReadAhead+0x341 fffff880`070b4c00 fffff800`0328d961 : fffffa80`0ca97ee0 fffff880`014213d0 fffff800`03487150 00000000`00000002 : nt!CcWorkerThread+0x21e fffff880`070b4cb0 fffff800`03524c06 : 00000000`124bcf70 fffffa80`10dc4b60 00000000`00000080 fffffa80`0ca7b040 : nt!ExpWorkerThread+0x111 fffff880`070b4d40 fffff800`0325ec26 : fffff880`009b2180 fffffa80`10dc4b60 fffff880`009bd040 fffff880`0123da90 : nt!PspSystemThreadStartup+0x5a fffff880`070b4d80 00000000`00000000 : fffff880`070b5000 fffff880`070af000 fffff880`070b46e0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ObDereferenceObjectDeferDeleteWithTag+1e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880070b3f80 ; kb FAILURE_BUCKET_ID: X64_0x34_nt!ObDereferenceObjectDeferDeleteWithTag+1e BUCKET_ID: X64_0x34_nt!ObDereferenceObjectDeferDeleteWithTag+1e Followup: MachineOwner --------- 1: kd> lmtsmn start end module name fffff880`00eb0000 fffff880`00f07000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02a00000 fffff880`02a8a000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`03dab000 fffff880`03dc1000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`07b72000 fffff880`07b7a000 ALSysIO64 ALSysIO64.sys Sun Apr 19 15:41:04 2009 (49EB7E50) fffff880`03d30000 fffff880`03d45000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00e4d000 fffff880`00e58000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`03ad5000 fffff880`03ade000 anodlwfx anodlwfx.sys Fri Mar 06 05:10:08 2009 (49B0F680) fffff880`00e1a000 fffff880`00e23000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e23000 fffff880`00e4d000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff960`00860000 fffff960`008c1000 ATMFD ATMFD.DLL unavailable (00000000) fffff880`02b19000 fffff880`02b20000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03cf9000 fffff880`03d0a000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`06d82000 fffff880`06da0000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`007b0000 fffff960`007d7000 cdd cdd.dll unavailable (00000000) fffff880`02ab9000 fffff880`02ae3000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00d28000 fffff880`00de8000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01074000 fffff880`010a4000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00cca000 fffff880`00d28000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01132000 fffff880`011a5000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`03d9b000 fffff880`03dab000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`06bdc000 fffff880`06bea000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03c58000 fffff880`03cdb000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`03cdb000 fffff880`03cf9000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03a00000 fffff880`03a0f000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01213000 fffff880`01229000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`09aca000 fffff880`09bc4000 Dnetr28ux Dnetr28ux.sys Wed Aug 05 09:59:46 2009 (4A799052) fffff880`06ab7000 fffff880`06ad9000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`06bf6000 fffff880`06bff000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`06bea000 fffff880`06bf6000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`06800000 fffff880`06813000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`06adf000 fffff880`06aeb000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`04207000 fffff880`042fb000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`042fb000 fffff880`04341000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`07b3c000 fffff880`07b72000 fastfat fastfat.SYS Mon Jul 13 19:23:28 2009 (4A5BC1F0) fffff880`051f2000 fffff880`051ff000 fdc fdc.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6) fffff880`010b3000 fffff880`010c7000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`05545000 fffff880`05550000 flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6) fffff880`00e58000 fffff880`00ea4000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`01200000 fffff880`0120a000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`0103a000 fffff880`01074000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`01597000 fffff880`015e1000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`037ec000 fffff800`03835000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`03d4e000 fffff880`03d72000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`06b05000 fffff880`06b1e000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`06b1e000 fffff880`06b26080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`06af7000 fffff880`06b05000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`06cba000 fffff880`06d82000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`0120a000 fffff880`01213000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`03df1000 fffff880`03e00000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`06b51000 fffff880`06b5f000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bad000 fffff800`00bb7000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`06aeb000 fffff880`06af7000 KMWDFILTER KMWDFILTER.sys Wed Apr 29 02:20:48 2009 (49F7F1C0) fffff880`0542c000 fffff880`0546f000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9) fffff880`013cf000 fffff880`013e9000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`0156c000 fffff880`01597000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`06ad9000 fffff880`06ade200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`05565000 fffff880`0557a000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`06813000 fffff880`06836000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00ca9000 fffff880`00cb6000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`06b7a000 fffff880`06b88000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`02bc5000 fffff880`02bd4000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`06b27000 fffff880`06b34000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00e00000 fffff880`00e1a000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02ae3000 fffff880`02b10000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`077b2000 fffff880`077c2000 MpNWMon MpNWMon.sys Sat Mar 20 01:58:00 2010 (4BA463E8) fffff880`06da0000 fffff880`06db8000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`06db8000 fffff880`06de5000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`06c00000 fffff880`06c4e000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`06c4e000 fffff880`06c71000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`02b7e000 fffff880`02b89000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00f10000 fffff880`00f1a000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`010d4000 fffff880`01132000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03bed000 fffff880`03bf8000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01400000 fffff880`01412000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`0141a000 fffff880`0150c000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`03de5000 fffff880`03df1000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`055cd000 fffff880`055e0000 ndisuio ndisuio.sys Mon Jul 13 20:09:25 2009 (4A5BCCB5) fffff880`03c00000 fffff880`03c2f000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`05550000 fffff880`05565000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`03ade000 fffff880`03aed000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`03a37000 fffff880`03a7c000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`0150c000 fffff880`0156c000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`02b89000 fffff880`02b9a000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03be1000 fffff880`03bed000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`03210000 fffff800`037ec000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`0122c000 fffff880`013cf000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`02b10000 fffff880`02b19000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`051f0000 fffff880`051f1180 nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88) fffff880`04616000 fffff880`051efa80 nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E) fffff880`0557a000 fffff880`055cd000 nwifi nwifi.sys Mon Jul 13 20:07:23 2009 (4A5BCC3B) fffff880`03a85000 fffff880`03aab000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`03d7e000 fffff880`03d9b000 parport parport.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`00f5a000 fffff880`00f6f000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00f1a000 fffff880`00f4d000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00fe0000 fffff880`00fe7000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00fe7000 fffff880`00ff7000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`013e9000 fffff880`013fa000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`076d4000 fffff880`0777a000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`06a7a000 fffff880`06ab7000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00cb6000 fffff880`00cca000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`010c7000 fffff880`010d3040 PxHlpa64 PxHlpa64.sys Tue Oct 20 14:08:42 2009 (4ADDFCAA) fffff880`03dc1000 fffff880`03de5000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`03c2f000 fffff880`03c4a000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`03a0f000 fffff880`03a30000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`02a8a000 fffff880`02aa4000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03b90000 fffff880`03be1000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`03c4a000 fffff880`03c55000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`02b63000 fffff880`02b6c000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b6c000 fffff880`02b75000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b75000 fffff880`02b7e000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01000000 fffff880`0103a000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`055e0000 fffff880`055f8000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04341000 fffff880`04398000 Rt64win7 Rt64win7.sys Fri Sep 03 01:58:32 2010 (4C808E88) fffff880`0685c000 fffff880`06a79300 RTKVHD64 RTKVHD64.sys Tue Dec 08 05:20:05 2009 (4B1E2855) fffff880`0777a000 fffff880`07785000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`03d72000 fffff880`03d7e000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`03aed000 fffff880`03b0a000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`015f1000 fffff880`015f9000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`09a00000 fffff880`09a71000 spsys spsys.sys Mon May 11 13:20:58 2009 (4A085E7A) fffff880`07aa6000 fffff880`07b3c000 srv srv.sys Thu Aug 26 23:38:00 2010 (4C773318) fffff880`07600000 fffff880`07667000 srv2 srv2.sys Thu Aug 26 23:37:46 2010 (4C77330A) fffff880`07785000 fffff880`077b2000 srvnet srvnet.sys Thu Aug 26 23:37:24 2010 (4C7732F4) fffff880`043f9000 fffff880`043fa480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`077c2000 fffff880`077d4000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`02bb8000 fffff880`02bc5000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02b9a000 fffff880`02bb8000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03b7c000 fffff880`03b90000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00560000 fffff960`0056a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`03d0a000 fffff880`03d30000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`06b88000 fffff880`06bdc000 udfs udfs.sys Mon Jul 13 19:23:37 2009 (4A5BC1F9) fffff880`0546f000 fffff880`05481000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`06b34000 fffff880`06b51000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`054ad000 fffff880`054aef00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`04600000 fffff880`04611000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`054eb000 fffff880`05545000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`04398000 fffff880`043a3000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`043a3000 fffff880`043f9000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`0549e000 fffff880`054ad000 usbrpm usbrpm.sys Mon Jul 13 20:35:14 2009 (4A5BD2C2) fffff880`06b5f000 fffff880`06b7a000 USBSTOR USBSTOR.SYS Mon Jul 13 20:06:34 2009 (4A5BCC0A) fffff880`00f4d000 fffff880`00f5a000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`02b20000 fffff880`02b2e000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`02b2e000 fffff880`02b53000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`015e1000 fffff880`015f1000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00f6f000 fffff880`00f84000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00f84000 fffff880`00fe0000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`011a5000 fffff880`011f1000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`054af000 fffff880`054eb000 vpchbus vpchbus.sys Tue Sep 22 21:32:32 2009 (4AB97AB0) fffff880`03ac1000 fffff880`03ad5000 vpcnfltr vpcnfltr.sys Tue Sep 22 21:32:30 2009 (4AB97AAE) fffff880`05481000 fffff880`0549e000 vpcusb vpcusb.sys Tue Sep 22 21:32:39 2009 (4AB97AB7) fffff880`03b25000 fffff880`03b7b580 vpcvmm vpcvmm.sys Thu Dec 31 02:27:33 2009 (4B3C5265) fffff880`09bc4000 fffff880`09bd1000 vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39) fffff880`03aab000 fffff880`03ac1000 vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A) fffff880`03b0a000 fffff880`03b25000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`02b53000 fffff880`02b63000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00c00000 fffff880`00ca4000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00de8000 fffff880`00df7000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`03a7c000 fffff880`03a85000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`000b0000 fffff960`003bf000 win32k win32k.sys unavailable (00000000) fffff880`03d45000 fffff880`03d4e000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00f07000 fffff880`00f10000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`06836000 fffff880`06857000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`010a4000 fffff880`010b2000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`011f1000 fffff880`011fd000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`00ea4000 fffff880`00ead000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`02aa6000 fffff880`02ab9000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Quote:
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ALPHA Filter Driver, ANOD network security, Alpha Networks Inc (D-Link subsidiary). Update this driver or uninstall the security program or rename the driver.
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - wireless mouse driver from Trust MI-4950R/TRUST MI-7700R or Medion, or Tevion mouse. Update this mouse driver or upgrade to a new mouse compatible with Win 7. Try another mouse and rename the driver.
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - wireless mouse driver from Trust MI-4950R/TRUST MI-7700R or Medion, or Tevion mouse. Update this mouse driver or upgrade to a new mouse compatible with Win 7. Try another mouse and rename the driver.
If you have another mouse you can try, rename KMWDFILTER.sys also, reboot and see if this helps your system. Renaming this driver will likely disable your current mouse.
Yes, you are correct, my wireless adapter has stopes working (now on my old laptop).. What would you like me to do now. Many thanks
Does your computer run without a BSOD now that that driver did not load? If it does, you need a new wireless adapter. To get your wireless working again, you can rename that driver back to .sys. But do run your computer some without it to see how it behaves.
Yes I am prety sure that the driver you have said is the cause of the BSOD's..
I will keep the driver unloaded for a further 2 days just to check
How could i get a new wireless adapter, my adapter is http://www.dlink.co.uk/cs/Satellite?...e-GB/DLWrapper
I have two of these, one never been used
Many thanks
I will keep the driver unloaded for a further 2 days just to check
How could i get a new wireless adapter, my adapter is http://www.dlink.co.uk/cs/Satellite?...e-GB/DLWrapper
I have two of these, one never been used
Many thanks
(name of the wireless adapter)..."D-Link DWA-140"
Depending on the revision, the D-Link DWA 140 is compatible with Windows 7. Here are the versions. Apparently the first one listed is not compatible with Win 7 based on the dates of the drivers shown in Support.. The second one appears to be.
Let me suggest that you uninstall your adapter completely. Reinstall just the adapter. Don't install any utilities with it. The main thing you are trying to eliminate is that security driver. This may do away with that driver. It is worth a try. You can also try downloading the latest drivers from D-Link. If none of this works, you will need to get an updated adapter.
Let me suggest that you uninstall your adapter completely. Reinstall just the adapter. Don't install any utilities with it. The main thing you are trying to eliminate is that security driver. This may do away with that driver. It is worth a try. You can also try downloading the latest drivers from D-Link. If none of this works, you will need to get an updated adapter.
how do you think i should remove the driver?
You have renamed it, correct? That will do the trick.
The BSOD'd have started again
had 3 whithin the last hour
my dumps are up
had 3 whithin the last hour
my dumps are up
Quote:
Error code 7E, Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
Error code 34, CACHE_MANAGER. Usual causes: Insufficient physical memory, Indexing, Device driver
Error code 34, CACHE_MANAGER. Usual causes: Insufficient physical memory, Indexing, Device driver
Quote:
anodlwfx.sys Fri Mar 06 05:10:08 2009 - ALPHA Filter Driver, ANOD network security, Alpha Networks Inc (D-Link subsidiary). Update this driver or uninstall the security program or rename the driver.
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - wireless mouse driver from Trust MI-4950R/TRUST MI-7700R or Medion, or Tevion mouse. Update this mouse driver or upgrade to a new mouse compatible with Win 7. Try another mouse and rename the driver.
KMWDFILTER.sys Wed Apr 29 02:20:48 2009 - wireless mouse driver from Trust MI-4950R/TRUST MI-7700R or Medion, or Tevion mouse. Update this mouse driver or upgrade to a new mouse compatible with Win 7. Try another mouse and rename the driver.
I recommend that you upgrade your wireless adapter and uninstall the current one.
here is a screen shot of the memtest, I have cancled the test because there were errors as shown
many thanks
many thanks
Good job of reporting back. But you are not done. Memtest shows that you have a RAM problem; it does not tell you what the problem is. It could be a bad RAM stick, incompatible be RAM, mismatched RAM, a bad RAM slot on your motherboard, or a bad memory controller (motherboard).
Remove all of your RAM except for the stick in the first slot. Run Memtest on this stick for at least seven passes. If passes, remove that stick, mark it as good and test the next stick. Repeat until you have tested all sticks. If a stick fails, mark it as bad. If all sticks fail, test one in the next slot. Test each slot with a known good stick. Post your results.
Boot your computer with one stick of RAM known to be good and see how your system does. Post back and let us know.
Remove all of your RAM except for the stick in the first slot. Run Memtest on this stick for at least seven passes. If passes, remove that stick, mark it as good and test the next stick. Repeat until you have tested all sticks. If a stick fails, mark it as bad. If all sticks fail, test one in the next slot. Test each slot with a known good stick. Post your results.
Boot your computer with one stick of RAM known to be good and see how your system does. Post back and let us know.
when installing my new wireless adapter N speed. would I Have to thange the anodlwfx driver back to sys?
I don't think so. Installing the new adapter should install the necessary drivers.
umm :/
When the anodlwfx is named (.bak) on the end, my pc will not join the wireless network (says it has limited access, But my laptop joins it fine)but when its (.sys) it does.
And also when its (.sys) i receive BSOD's
what do you think I should do
Thanks for your time
When the anodlwfx is named (.bak) on the end, my pc will not join the wireless network (says it has limited access, But my laptop joins it fine)but when its (.sys) it does.
And also when its (.sys) i receive BSOD's
what do you think I should do
Thanks for your time
Did you try to set the connection from scratch with anodlwfx renamed to bak?
I simple pluged the pci in and then downloaded the drivers, It does not work, I done as instructed on the box
Uninstall it completely and reboot. Then turn your computer off, put the card back in and boot. Let Windows detect the hardware. Do you still have anodlwfx renamed? You may have to disable your old card in Device Manager.
it was the same with the old card
I had the DWA-140, then baught an "g" pci wireless, then you told me to upgrade so I got an "n"
I think that the anodlwfx is definitely the cause of all these Blue screens
I had the DWA-140, then baught an "g" pci wireless, then you told me to upgrade so I got an "n"
I think that the anodlwfx is definitely the cause of all these Blue screens
Will the new card work with anodlwfx renamed to old or bak?
it only works when it is renames as sys
bak (doesnt work)
old (havent tried yet)
would you like me to rename it to bak??
bak (doesnt work)
old (havent tried yet)
would you like me to rename it to bak??
No, renaming it to anything stops the driver from loading. I have askes for a networking guru to take a look at this thread. I hope to he/she will have some insight.
I know little about Networking so I wouldn't want to attempt helping in that dept. but ...
Did you try the suggestion of testing each RAM stick individually to try and isolate the problem there?
I think at this point you may want to take a step back, and try to find out what exactly is causing all the RAM errors.
If it comes down to a bad RAM module, simply run the PC with the 1 good for now, (if ones is good)
Bad hardware can and will cause all forms instability within Windows, making it much more difficult to isolate other issues.
Did you try the suggestion of testing each RAM stick individually to try and isolate the problem there?
I think at this point you may want to take a step back, and try to find out what exactly is causing all the RAM errors.
If it comes down to a bad RAM module, simply run the PC with the 1 good for now, (if ones is good)
Bad hardware can and will cause all forms instability within Windows, making it much more difficult to isolate other issues.
But I am sure it is anodlwfx
I tried for a whole day with it on .bak (not loading the drivers) and has no Blue screens
When ever It is .sys (and loading) I get blue screens.
I tried for a whole day with it on .bak (not loading the drivers) and has no Blue screens
When ever It is .sys (and loading) I get blue screens.
And it very well may be.
But all I am saying is if the RAM is still throwing all of those errors in MEMtest, it really should be pinpointed before moving on.
All Im saying is Bad RAM can cause all types of issues.
Overall Instability, Driver Crashes, App Crashes, File corruption etc.
Because, it is quite possible you fix one problem, and then another arises. Fix that, now something else.
And it will all come back to unstable or Bad RAM.
But all I am saying is if the RAM is still throwing all of those errors in MEMtest, it really should be pinpointed before moving on.
All Im saying is Bad RAM can cause all types of issues.
Overall Instability, Driver Crashes, App Crashes, File corruption etc.
Because, it is quite possible you fix one problem, and then another arises. Fix that, now something else.
And it will all come back to unstable or Bad RAM.
Wishmaster is correct. You need to address the RAM issue first and then we can work on that driver issue.
Yes I agree,
But I do not trust myself with the inside of the machine.
I will be asking a computer technician for him to do things with the RAM
I understand what you are saying, but I would just like to get this driver issue sorted
But I do not trust myself with the inside of the machine.
I will be asking a computer technician for him to do things with the RAM
I understand what you are saying, but I would just like to get this driver issue sorted
Are there any tests such as MEMtest that could identify which RAM(s) is/are causing the problem
The person I brought my pc from says that I can only send back 1 Memory stick back (i have 4x4gb)
The person I brought my pc from says that I can only send back 1 Memory stick back (i have 4x4gb)
I just realized you have 16GB of RAM.
As mentioned, a Bad stick could be a possibility.
It is also possible, that having all the DIMM slots populated with that much RAM could be the issue (depending on what the RAM is rated for & speed its set at) as it could be too much of a strain at default settings)
As already suggested, the best way is to test each stick individually.
If they all test good, try running with just 2x4 (8GB) and see if passes then.
As mentioned, a Bad stick could be a possibility.
It is also possible, that having all the DIMM slots populated with that much RAM could be the issue (depending on what the RAM is rated for & speed its set at) as it could be too much of a strain at default settings)
As already suggested, the best way is to test each stick individually.
If they all test good, try running with just 2x4 (8GB) and see if passes then.
I agree, you do need to fix the RAM at some stage.
Duplicate thread, for reference - Constant BSOD's...HELP NEEDED - Tech Support Forum
Duplicate thread, for reference - Constant BSOD's...HELP NEEDED - Tech Support Forum
ok, I have taken out one of my RAM sticks and havent received a BSOD yet (1day)
What would you like me to do now?
thanks
What would you like me to do now?
thanks
Let it run another day like it is and then add one more RAM stick and see how it does.
At this moment I have 3 RAM in there. I only took one stick out
OK. I am not a hardware Guru at all. I will ask the hardware guys to take a look at this thread and offer their help.
�� Quote: Originally Posted by cemcilfa At this moment I have 3 RAM in there. I only took one stick out
Carl is right, when running that much RAM you will likely need to adjust some settings.
First ensure all the RAM sticks are good.
Use this tutorial for guidance: How to Test and Diagnose RAM Issues with Memtest86+
I'm afraid that if RAM passes one or two memtest86+ doesn't guarentee there are no RAM problems.
If you follow the above tutorial your chances of finding the correct fix will be much better.
Test each RAM card one at a time, looking for RAM cards that pass and motherboard slots that pass.
If you are not comfortable removing and testing RAM cards then you will need to find someone to help you or take it to a local repair shop. After reading through this thread, the RAM issue needs to be explored first. This can cause the errors and BSoDs you are having.
D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Speed Fan or Core Temp , run one of these and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the North Bridge (NB) voltages are, look under the M.I.T. page you should see 'CPU NB VID Control'.
It's on page 43 of your motherboard manual.
Gigabyte Motherboard Manual GA-MA78LMT-US2H
There known issues with AMD integrated memory controllers, the CPUZ tabs will give the information needed to check this, that much RAM will usually require a NB (memory controller) voltage bump.
Post the revision number of your motherboard.
If you don't know it, then open your case and look in the lower left corner on the motherboard, it is printed there.
Do your BSoDs happen when you first start your computer or randomly?
First ensure all the RAM sticks are good.
Use this tutorial for guidance: How to Test and Diagnose RAM Issues with Memtest86+
I'm afraid that if RAM passes one or two memtest86+ doesn't guarentee there are no RAM problems.
If you follow the above tutorial your chances of finding the correct fix will be much better.
Test each RAM card one at a time, looking for RAM cards that pass and motherboard slots that pass.
If you are not comfortable removing and testing RAM cards then you will need to find someone to help you or take it to a local repair shop. After reading through this thread, the RAM issue needs to be explored first. This can cause the errors and BSoDs you are having.
D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Speed Fan or Core Temp , run one of these and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the North Bridge (NB) voltages are, look under the M.I.T. page you should see 'CPU NB VID Control'.
It's on page 43 of your motherboard manual.
Gigabyte Motherboard Manual GA-MA78LMT-US2H
There known issues with AMD integrated memory controllers, the CPUZ tabs will give the information needed to check this, that much RAM will usually require a NB (memory controller) voltage bump.
Post the revision number of your motherboard.
If you don't know it, then open your case and look in the lower left corner on the motherboard, it is printed there.
Do your BSoDs happen when you first start your computer or randomly?
Thanks, I will be posting the info on my next post
Do you think that there is any possibility that the faulty RAM can cause my PSU to burn out
(after receiving a BSoD my pc restarted and made a electrical burn sound) about a month ago.
Would it be fair to ask the company I bought the pc from to send me another PSU??
Thank you for your time
Do you think that there is any possibility that the faulty RAM can cause my PSU to burn out
(after receiving a BSoD my pc restarted and made a electrical burn sound) about a month ago.
Would it be fair to ask the company I bought the pc from to send me another PSU??
Thank you for your time
I think it could be a faulty PSU that damaged your RAM rather than the RAM causing your PSU to burn out. There is the possibility that there is a short somewhere on the motherboard; but most likely, the PSU is just going bad. I would definitely have the company check your PSU and replace it if necessary.
The BSoD's were happening before my PSU broke
Coretemp temperatures:23(Normal)--30-40(under load)
Coretemp temperatures:23(Normal)--30-40(under load)
'CPU NB VID Control' was shown as [AUTO]
CPU VOLT [AUTO]
NORMAL CORE VOLT 1.4000V
CPU VOLT [AUTO]
NORMAL CORE VOLT 1.4000V
The PSU could have been on its way out for a while and intermittently causing problems.
You should check the PSU if you suspect it to be faulty.
Carl is right, it's more likely a short on something, maybe the motherboard, is causing the PSU problems.
If the PSU is faulty it will cause all kinds of issues.
Please answer these questions.
For the 'CPU NB VID Control', check in your motherboard manual on how to set it to manual.
This is the setting we need to adjust to get all your RAM stable.
Carl is right, it's more likely a short on something, maybe the motherboard, is causing the PSU problems.
If the PSU is faulty it will cause all kinds of issues.
Please answer these questions.
Quote:
Go to your BIOS and tell us what the North Bridge (NB) voltages are, look under the M.I.T. page you should see 'CPU NB VID Control'.
It's on page 43 of your motherboard manual.
Gigabyte Motherboard Manual GA-MA78LMT-US2H
There known issues with AMD integrated memory controllers, the CPUZ tabs will give the information needed to check this, that much RAM will usually require a NB (memory controller) voltage bump.
Post the revision number of your motherboard.
If you don't know it, then open your case and look in the lower left corner on the motherboard, it is printed there.
Do your BSoDs happen when you first start your computer or randomly?
It's on page 43 of your motherboard manual.
Gigabyte Motherboard Manual GA-MA78LMT-US2H
There known issues with AMD integrated memory controllers, the CPUZ tabs will give the information needed to check this, that much RAM will usually require a NB (memory controller) voltage bump.
Post the revision number of your motherboard.
If you don't know it, then open your case and look in the lower left corner on the motherboard, it is printed there.
Do your BSoDs happen when you first start your computer or randomly?
This is the setting we need to adjust to get all your RAM stable.
Revision ujmber of motherboard--- 1.3 SPDIF 10 COM
Would you like me to insert the RAM I have taken out and then set the "CPU NB VID Control" to manual?
Would you like me to insert the RAM I have taken out and then set the "CPU NB VID Control" to manual?
Any problems with the PSU?
Are you still having any BSoDs?
Did they stop when you took one RAM card out?
Change the "CPU NB VID Control" to manual, check what the voltage is set at and post it here.
What is the DDR3 Voltage Control reading?
If you can't see a number, like 1.5v, then set it to manual and tell us what the voltage is.
If you have not had any BSoDs since you took the RAM card out then you can put the RAM card back in and bump the CPU NB VID Control by 0.1v.
If it's at 1.1V then change it to 1.2v.
Run memtest86+ for seven passes, best to do it overnight as it should take 6-7 hours, might take longer with 16GB RAM.
If you see any errors you can stop the test and let us know how long it ran, what test # it was on and the approximate number of errors.
Are you still having any BSoDs?
Did they stop when you took one RAM card out?
Change the "CPU NB VID Control" to manual, check what the voltage is set at and post it here.
What is the DDR3 Voltage Control reading?
If you can't see a number, like 1.5v, then set it to manual and tell us what the voltage is.
If you have not had any BSoDs since you took the RAM card out then you can put the RAM card back in and bump the CPU NB VID Control by 0.1v.
If it's at 1.1V then change it to 1.2v.
Run memtest86+ for seven passes, best to do it overnight as it should take 6-7 hours, might take longer with 16GB RAM.
If you see any errors you can stop the test and let us know how long it ran, what test # it was on and the approximate number of errors.
I have replaces the PSU
NO BSoD's after removing on of the RAM sticks
NO BSoD's after removing on of the RAM sticks
I am glad that you have found the source of the problem.
I am very thankful that you have helped me all this time to find it
I have inserted my Ram stick back into the slot and boosted my vis controll by o.100V
It now shows 1.2250V
It now shows 1.2250V
�� Quote: Originally Posted by cemcilfa I am very thankful that you have helped me all this time to find it
Have you ran memtest86+?
i will run memtest tonight
If the errors come early shall i reboot or shall I wait for the whole 7 tests?
how would you like me to present the infomation to you?
If the errors come early shall i reboot or shall I wait for the whole 7 tests?
how would you like me to present the infomation to you?
I have received another BSod after inserting the RAM stick back in?
How would you like me to tun memtest86+
How would you like me to tun memtest86+
Run memtest86+ from a USB memory stick or DVD.
If you get errors you can stop the test.
If you get any errors just note them, if there are too many just note the first couple of errors.
Tell us if there are a couple of errors or 100 or 1,000.
After running memtest86+ if you get errors or not, bump the DRAM voltage 0.05v.
If it is 1.5v now bump it to 1.55v.
In your BIOS it's called 'DDR3 Voltage Control'.
Page 42 of your motherboard manual.
Then run memtest86+ again.
If you get any error, same as above, let us know.
If you get errors you can stop the test.
If you get any errors just note them, if there are too many just note the first couple of errors.
Tell us if there are a couple of errors or 100 or 1,000.
After running memtest86+ if you get errors or not, bump the DRAM voltage 0.05v.
If it is 1.5v now bump it to 1.55v.
In your BIOS it's called 'DDR3 Voltage Control'.
Page 42 of your motherboard manual.
Then run memtest86+ again.
If you get any error, same as above, let us know.
I did not get any errors with the Module taken out
Now that I found the cause of the issue I beleive I can handle it from here
both CarlTR6 and Dave76....THANK YOU VERY MUCH
Now that I found the cause of the issue I beleive I can handle it from here
both CarlTR6 and Dave76....THANK YOU VERY MUCH
You are very welcome. I am glad we could help. Dave did the work; he is the RAM Guru.
Did you bump the RAM voltage and run memtest86+?
This doesn't mean you have a bad RAM card.
When you have large capacity RAM cards it usually takes a little more voltage to run them, when you have four RAM cards it will also take more voltage to run stable.
You have both, it will take voltage bumps for the RAM cards and for the CPU NB VID to run stable.
With one card taken out your system runs stable, the possibilities are they need a voltage bump, maybe bad RAM card, maybe bad RAM slot.
Easy way to test this is to follow the memtest86+ tutorial.
If you test the RAM cards, usually one at a time, since your system runs stable with three cards I would test two cards at a time, if they pass testing them in all four slots then the RAM and slots are good.
You just need to find the right voltage settings, RAM and CPU NB VID.
If you get different RAM at 16GB, 4 X 4gb, you will likely still have to adjust voltages to get it to run.
Let us know if you want to continue.
This doesn't mean you have a bad RAM card.
When you have large capacity RAM cards it usually takes a little more voltage to run them, when you have four RAM cards it will also take more voltage to run stable.
You have both, it will take voltage bumps for the RAM cards and for the CPU NB VID to run stable.
With one card taken out your system runs stable, the possibilities are they need a voltage bump, maybe bad RAM card, maybe bad RAM slot.
Easy way to test this is to follow the memtest86+ tutorial.
If you test the RAM cards, usually one at a time, since your system runs stable with three cards I would test two cards at a time, if they pass testing them in all four slots then the RAM and slots are good.
You just need to find the right voltage settings, RAM and CPU NB VID.
If you get different RAM at 16GB, 4 X 4gb, you will likely still have to adjust voltages to get it to run.
Let us know if you want to continue.
I will be asking my supplier for a new RAM module..If that doesnt work then I will post a thread to continue
Thanks for your time
Thanks for your time
Không có nhận xét nào:
Đăng nhận xét