BSOD win7 pro 32bit

[dg862]

Hello!

Lately, I have been experiencing sporadic BSOD, four times in the past two weeks. I am using Windows 7 Professional 32 bit on an MSI CR-720 notebook. I am a university student, so I downloaded the operating system from MSDNAA, wrote it to DVD and installed it from that. I had the notebook for about a year, and if I remember correctly, I have only reinstalled once about four months ago.

I completed the steps suggested in the sticky and attached the resulting report files. I have also uploaded the four minidump files.

Help?

 

[zigzag3143]

Hello!

Lately, I have been experiencing sporadic BSOD, four times in the past two weeks. I am using Windows 7 Professional 32 bit on an MSI CR-720 notebook. I am a university student, so I downloaded the operating system from MSDNAA, wrote it to DVD and installed it from that. I had the notebook for about a year, and if I remember correctly, I have only reinstalled once about four months ago.

I completed the steps suggested in the sticky and attached the resulting report files. I have also uploaded the four minidump files.

Help?

The two older ones related to your athr.sys dirver (atheros wifi) the two never ones memory corruption possible from the same driver or possibly from Opera.


I would run memtest


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86.com - Memory Diagnostic

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.


Re-install the athrx.sys driver with the newest version from the mfr.

If this doesnt fix it I would run driver verifier to find whaich driver is the true casue

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051211-23478-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0x82e40000 PsLoadedModuleList = 0x82f88810
Debug session time: Thu May 12 14:06:09.459 2011 (GMT-4)
System Uptime: 0 days 5:01:32.973
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
............
3: kd> 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 000474a1, page frame number
Arg3: 00000002, current page state
Arg4: 00046c9f, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  opera.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82f29804 to 82f1ce3c

STACK_TEXT:  
b5ffd748 82f29804 0000004e 00000099 000474a1 nt!KeBugCheckEx+0x1e
b5ffd760 82ee9487 c0802000 b5ffd808 85c366d0 nt!MiBadShareCount+0x24
b5ffd7ac 82ee0474 85c364e0 89329d48 85c364e0 nt!MiDeletePfnList+0x312
b5ffdc14 82ee51d0 85c364e0 85c364e0 00000000 nt!MiDeleteAddressesInWorkingSet+0x118
b5ffdc40 830891fe 97ea4fb8 89329d48 c0000354 nt!MmCleanProcessAddressSpace+0x8c
b5ffdcb4 830bd630 00000000 86b05c70 00000001 nt!PspExitThread+0x683
b5ffdccc 82ee825b 86b05c70 b5ffdcf8 b5ffdd04 nt!PsExitSpecialApc+0x22
b5ffdd1c 82e834d4 00000001 00000000 b5ffdd34 nt!KiDeliverApc+0x28b
b5ffdd1c 76ed6344 00000001 00000000 b5ffdd34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
1b1af730 00000000 00000000 00000000 00000000 0x76ed6344


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+24
82f29804 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+24

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fd915

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24

BUCKET_ID:  0x4E_99_nt!MiBadShareCount+24

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

 

[dg862]

Wow, thanks for the quick reply! I'll run memtest over the weekend then.

Now that I think back, I had some problems with the wifi driver. I remember that I had to install and reinstall it a couple of times to get it working. Might have messed something up.

Thank you again. I'll see if a new driver fixes the problem or if memtest turns up something interesting.