Pc has been working fine for about 2 weeks since you guys helped me with my last BSOD........and today there is a new one. I'm getting so frustrated with this crap. It seems like every time there are updates for Win 7 there is a new problem.
Thanks for help!
Last edited by stumpedplshelp; 12 Jun 2010 at 18:55.
Sorry I forgot to add that these BSODs only occur on start up for me. I'm running all up to date drivers (as far as I know)and I have tested memory and CPU for hours looking for errors and none have been identified.
Last edited by stumpedplshelp; 12 Jun 2010 at 12:36.
bump
Second BSOD of the day, windows is not even reaching desktop before this happens. I have added no new software or hardware. Only thing that was added were new 7 updates the other day.
Any Ideas?
AAAAAAAAAAAAAAAnd another......
Here is what whocrashed gave me:
On Sat 6/12/2010 10:56:11 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFFB8005E0329B, 0x0, 0xFFFFF80002CE543B, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\061210-19234-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 6/12/2010 10:13:41 PM your computer crashed
This was likely caused by the following module: mrxsmb10.sys
Bugcheck code: 0xD3 (0xFFFFF88005E03260, 0x0, 0x1, 0xFFFFF80002CDDDC2)
Error: DRIVER_PORTION_MUST_BE_NONPAGED
Dump file: C:\Windows\Minidump\061210-16146-01.dmp
file path: C:\Windows\system32\drivers\mrxsmb10.sys
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: Longhorn SMB Downlevel SubRdr
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
And another....
On Sat 6/12/2010 11:45:44 PM your computer crashed
This was likely caused by the following module: srv2.sys
Bugcheck code: 0xD3 (0xFFFFF88005E03260, 0x0, 0x1, 0xFFFFF80002CE8E8D)
Error: DRIVER_PORTION_MUST_BE_NONPAGED
Dump file: C:\Windows\Minidump\061210-14492-01.dmp
file path: C:\Windows\system32\drivers\srv2.sys
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: Smb 2.0 Server driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
another
Please enable driver verifier: Using Driver Verifier to identify issues with Drivers
I suspect it is a driver issue, but I can't tell which one.
You may also try a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Your infared drivers are out of date. Make sure Windows Update is enabled, and install the latest updates.
You may try disabling that device and see what happens.
BSOD BUGCHECK SUMMARYCode:Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sat Jun 12 18:12:27.426 2010 (GMT-4) System Uptime: 0 days 0:00:18.080 BugCheck D3, {fffff88005e03260, 0, 1, fffff80002cdddc2} Probably caused by : win32k.sys ( win32k!memset+80 ) BUGCHECK_STR: 0xD3 PROCESS_NAME: explorer.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sat Jun 12 10:44:14.864 2010 (GMT-4) System Uptime: 0 days 0:00:17.518 BugCheck D3, {fffff88005e03260, 0, 1, fffff80002ca6e8d} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) BUGCHECK_STR: 0xD3 PROCESS_NAME: dwm.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sat Jun 12 20:05:43.610 2010 (GMT-4) System Uptime: 0 days 0:00:20.874 BugCheck 4E, {7, fffffff55574ccb8, fffff88001568785, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+351d5 ) BUGCHECK_STR: 0x4E_7 PROCESS_NAME: explorer.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sat Jun 12 19:45:01.627 2010 (GMT-4) System Uptime: 0 days 0:00:19.891 BugCheck D3, {fffff88005e03260, 0, 1, fffff80002ce8e8d} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) BUGCHECK_STR: 0xD3 PROCESS_NAME: MsMpEng.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sat Jun 12 18:55:11.555 2010 (GMT-4) System Uptime: 0 days 0:03:03.210 BugCheck 50, {fffffb8005e0329b, 0, fffff80002ce543b, 7} Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+41b ) BUGCHECK_STR: 0x50 PROCESS_NAME: MOM.exe จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ
so I set up verifier and we will see if there is a crash....I ran memtest for about 36 gours last week with no errors at all. I am not aware of an infrared device that is on my PC. I am using a G15 that I have suspected of making my rig crash. Thanks for your help I will post with an update.
THANKS!
Quote