Windows VistaPost your Windows Vista related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
I am currently in much grief after having constant BSOD!
Issues started whilst using Windows 7 RC x64. For some reason I started getting BSOD after BSOD. I naturally assumed it was some dodgy Windows 7 driver that windows had automatically downloaded. To cut a long story short i then re-installed Windows Vista Ultimate x86 and to my surprise continued to get BSOD. I then figured bad RAM, so I ran memtest for hours on end and got no errors, also tried using completly differnt memory sticks. However I am still getting them.
A Quick System Rundown:
Windows Vista Ultimate X86 (Currently havent downloaded service pack... Downloading updates now)
Asus Crosshair AM2 Motherboard.
AMD Athlon 64 X2 6400+
2x 1GB Ram Sticks (Previous 2x 2GB) - DDR2
NVidia GeForce 8400GS
Unfortunatly I do not still have my minidumps from Windows 7 however here are the results from my Vista dumps from WinDBG.
Dump 1:
Quote:
Loading Dump File [C:\Windows\Minidump\Mini060409-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
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Machine Name:
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
Debug session time: Thu Jun 4 21:49:27.520 2009 (GMT+1)
System Uptime: 0 days 0:56:36.377
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
......
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, c080115a, ffff, 0}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
---------
*** Memory manager detected 5 instance(s) of page corruption, target is likely to have memory corruption.
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041790, The subtype of the bugcheck.
Arg2: c080115a
Arg3: 0000ffff
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: SetupX.exe
CURRENT_IRQL: 0
BAD_PAGES_DETECTED: 5
LAST_CONTROL_TRANSFER: from 818c11c1 to 8184047e
STACK_TEXT:
9a023bd0 818c11c1 112a0002 115fcfff 85a4c4b0 nt!MiDeleteVirtualAddresses+0x941
9a023ca8 818c0d51 85a4c4b0 854e68b8 86b34388 nt!MiRemoveMappedView+0x44a
9a023cd0 819e0eb7 86b34388 00000000 ffffffff nt!MiRemoveVadAndView+0xe3
9a023d34 819e0c45 85a4c4b0 112a0000 00000000 nt!MiUnmapViewOfSection+0x256
9a023d54 8188c96a ffffffff 112a0000 0b91f3a0 nt!NtUnmapViewOfSection+0x55
9a023d54 77460f34 ffffffff 112a0000 0b91f3a0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0b91f3a0 00000000 00000000 00000000 00000000 0x77460f34
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 5 instance(s) of page corruption, target is likely to have memory corruption.
Dump 2:
Quote:
Loading Dump File [C:\Windows\Minidump\Mini060509-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
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Machine Name:
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
Debug session time: Fri Jun 5 21:05:01.289 2009 (GMT+1)
System Uptime: 0 days 2:14:20.161
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.........
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, c0801794, ffff, 0}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
---------
*** Memory manager detected 2 instance(s) of page corruption, target is likely to have memory corruption.
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041790, The subtype of the bugcheck.
Arg2: c0801794
Arg3: 0000ffff
Arg4: 00000000
Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.
Ok, well my problem is that I have run memtest on my old RAM for hours and hours and returned no problem, so placed the ram. And was still getting BSOD's. I may have been unlucky enough to replace bad ram with bad ram, they were not replaced with brand new sticks.
I will run memtest again today whilst at work, and have just flashed my bios so will let you know of the results!
Yes, those dumps talk a lot about memory. You have changed the memory, but then there is what Pete informed.
You have not touched the gold connectors on the memory modules? Oil from your fingers can block the connection. If so, you would need to clean the connectors (both on the modules and the slots), try using "contact cleaner".
I might try going into the BIOS and make the "Default" settings (you could otherwise "Clear the CMOS" or pull out the motherboard battery out for say, half an hour).
See if SetupX.exe comes up again. That is a Nero "installer" file. I searched at the Nero website and there is a "clean uninstaller" for Nero.
