Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after changing from 4GB to 8GB SODIMM RAM

04 Aug 2013   #11
x BlueRobot

 

I did notice the other dump files, but this particular file was the most interesting:

Code:
BugCheck D6, {fffff98008933000, 0, fffff8800643feb9, 0}

*** WARNING: Unable to verify timestamp for uxpatch.sys
*** ERROR: Module load completed but symbols could not be loaded for uxpatch.sys

Could not read faulting driver name
Probably caused by : uxpatch.sys ( uxpatch+1eb9 )
Code:
Usual causes:  Device driver
The driver has referenced memory beyond it's current pool allocation, and then created a illegal page fault by referencing invalid memory addresses. This is buffer overrun situation.

Code:
kd> lmvm uxpatch
start             end                 module name
fffff880`0643e000 fffff880`06448000   uxpatch  T (no symbols)           
    Loaded symbol image file: uxpatch.sys
    Image path: \??\C:\Windows\system32\drivers\uxpatch.sys
    Image name: uxpatch.sys
    Timestamp:        Mon Jul 13 06:09:18 2009 (4A5AC17E)
    CheckSum:         00013F48
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
The driver seems to belong to a program called Within Network, please update the driver from here - UxStyle - no more patching.

Code:
kd> k
Child-SP          RetAddr           Call Site
fffff880`02f892f8 fffff800`02f43be0 nt!KeBugCheckEx
fffff880`02f89300 fffff800`02ec3d2e nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`02f89460 fffff880`0643feb9 nt!KiPageFault+0x16e
fffff880`02f895f0 00000000`c0000023 uxpatch+0x1eb9
fffff880`02f895f8 ffffffff`80000318 0xc0000023
fffff880`02f89600 fffff880`064423e0 0xffffffff`80000318
fffff880`02f89608 fffff800`02ec144f uxpatch+0x43e0
fffff880`02f89610 00000000`00000010 nt!KiIdleLoop+0x15f
fffff880`02f89618 fffff880`02f89648 0x10
fffff880`02f89620 fffff880`001c001a 0xfffff880`02f89648
fffff880`02f89628 fffff880`06440c30 0xfffff880`001c001a
fffff880`02f89630 00000000`00000086 uxpatch+0x2c30
fffff880`02f89638 fffff880`06440081 0x86
fffff880`02f89640 fffff880`064423e0 uxpatch+0x2081
fffff880`02f89648 fffff880`00000010 uxpatch+0x43e0
fffff880`02f89650 fffff880`064423e8 0xfffff880`00000010
fffff880`02f89658 00000000`00000000 uxpatch+0x43e8
You can disable Driver Verifier now if you haven't done so.


My System SpecsSystem Spec
.
05 Aug 2013   #12
AlexBrunt

Windows 7 Ultimate x64
 
 

I have disabled driver verifier and deleted uxpatch.sys already,
but BSOD still persists and I am unsure why.

I have attached the latest dump.
My System SpecsSystem Spec
05 Aug 2013   #13
x BlueRobot

 

Code:
BugCheck BE, {fffff8a00cf6e5b8, af300001a8a4b822, fffff88009427660, e}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamLogForNL+7b )
Code:
Usual causes:  Device driver, Memory
Code:
kd> !pte af300001a8a4b822
                                           VA af300001a8a4b822
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00030    PDE at FFFFF6FB40006A28    PTE at FFFFF68000D45258
Unable to get PXE FFFFF6FB7DBED000
WARNING: noncanonical VA, accesses will fault !
It seems that a device driver has referenced, and then attempted to write to a read only section of memory. We can see from the PTE, that the virtual address was non-canonical, being that the address was invalid.

Code:
kd> lmvm atikmdag
start             end                 module name
fffff880`04844000 fffff880`05000000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Mon Sep 20 02:47:42 2010 (4C96BD3E)
    CheckSum:         0076D892
    ImageSize:        007BC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your AMD graphics card driver seems to be causing problems, please update the driver from here - AMD Graphics Drivers & Software

Quote:
WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104
My System SpecsSystem Spec
.

05 Aug 2013   #14
AlexBrunt

Windows 7 Ultimate x64
 
 

After re-installing windows I got my driver from the link you specified it also said 13.4
but after installing it only installed the 12.104 driver and immediately bluescreened again I will upload new dump later today.

Edit: I came back to my computer today and uninstalled my graphics driver until further notice but here are the dumps from when it was installed after the BSOD

Edit #2: Even with the graphics driver uninstalled the BSODs still persist I am really unsure why, I'll upload the latest dump as a second attachment.
Please help.

Also i'm pretty sure every bluescreen has something to do with ntfs.sys

My System SpecsSystem Spec
06 Aug 2013   #15
x BlueRobot

 

Code:
BugCheck 1000007E, {ffffffffc0000005, fffff88005d8f446, fffff88002d5f7e8, fffff88002d5f040}

Probably caused by : AtihdW76.sys ( AtihdW76+4446 )
Code:
kd> lmvm AtihdW76
start             end                 module name
fffff880`05d8b000 fffff880`05da7000   AtihdW76 T (no symbols)           
    Loaded symbol image file: AtihdW76.sys
    Image path: \SystemRoot\system32\drivers\AtihdW76.sys
    Image name: AtihdW76.sys
    Timestamp:        Thu Feb 14 22:11:09 2013 (511D60FD)
    CheckSum:         00019F88
    ImageSize:        0001C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your ATI Function Driver for HD Audio Service seems to be causing problems, please update the driver from here - Support & Drivers

---------------------------------------------------------------------------

Code:
BugCheck 24, {1904fb, fffff8800297ad38, fffff8800297a590, fffff880012f9c11}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 )
Code:
Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
Code:
EXCEPTION_RECORD:  fffff8800297ad38 -- (.exr 0xfffff8800297ad38)
ExceptionAddress: fffff880012f9c11 (Ntfs!NtfsFindPrefix+0x0000000000000121)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
If we compare the two dump files, the type of exception which occurred, is exactly the same, a driver has referenced and accessed a invalid memory address. The function call which caused the exception in this case is the Ntfs!NtfsFindPrefix, which is used to find the file path for a particular file or directory. The file may have already been in memory, but the memory address was inaccessible.

I would update or remove the driver from the other dump, and then run Driver Verifier again.
My System SpecsSystem Spec
07 Aug 2013   #16
AlexBrunt

Windows 7 Ultimate x64
 
 

My uncle has had the same problem after he upgraded he's ram,
so has my dad and here is my uncles dump:
My System SpecsSystem Spec
07 Aug 2013   #17
x BlueRobot

 

Code:
BugCheck 1000007E, {ffffffffc0000005, fffff880046a8eba, fffff880009e19e8, fffff880009e1240}

Probably caused by : hardware ( usbhub!UsbhFdoPower_PowerSequence+26 )
Code:
EXCEPTION_RECORD:  fffff880009e19e8 -- (.exr 0xfffff880009e19e8)
ExceptionAddress: fffff880046a8eba (usbhub!UsbhFdoPower_PowerSequence+0x0000000000000026)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000038b841
Attempt to write to address 000000000038b841
The address is non-paged pool, and is a similar issue to your dump files.

I would recommend running Driver Verifier on your Uncle's laptop too, since there appears to quite few power related IRP calls within the call stack.

I would recommend checking for any BIOS updates, which will usually resolve hardware compatibility problems, which also raises the question of have you checked the RAM is compatible and supported by the motherboard?

Code:
TOSHIBA 1.60, 2/03/2010
What are the results from my suggestion for your computer?
My System SpecsSystem Spec
08 Aug 2013   #18
AlexBrunt

Windows 7 Ultimate x64
 
 

I have run driver verifier on my uncle's computer and the BSOD returned but not as a driver violation,
I urge you when you look through this dump to search for an error relating to IRQL_NOT_LESS_OR_EQUAL

STOP: 0x0000000A (0xFFFFF80003372958, 0x0000000000000002, 0x0000000000000000, 0xFFFFF8000309F242)

Edit #1: My uncle's laptop has BSOD again before driver verifier even started doing it's job,
stop code was different and I have uploaded the dump with Later on the end of the filename.
My System SpecsSystem Spec
08 Aug 2013   #19
x BlueRobot

 

Code:
BugCheck A, {fffff80003372958, 2, 0, fffff8000309f242}

Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
Code:
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Code:
2: kd> !thread
GetPointerFromAddress: unable to read from fffff800032ad000
THREAD fffffa800a1d2b50  Cid 0288.029c  Teb: 000007fffffdc000 Win32Thread: fffff900c0adac20 RUNNING on processor 2
IRP List:
    Unable to read nt!_IRP @ fffff98002df6b80
Not impersonating
GetUlongFromAddress: unable to read from fffff800031ecba4
Owning Process            fffffa800a1b4960       Image:         winlogon.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      3625         
Context Switch Count      719            IdealProcessor: 0                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x000000007758fbc0
Stack Init fffff88002a99d10 Current fffff88002a98ea0
Base fffff88002a9b000 Limit fffff88002a92000 Call fffff88002a99d60
Priority 14 BasePriority 13 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Code:
2: kd> lmvm WRkrn
start             end                 module name
fffff880`0103d000 fffff880`0105b000   WRkrn    T (no symbols)           
    Loaded symbol image file: WRkrn.sys
    Image path: \SystemRoot\System32\drivers\WRkrn.sys
    Image name: WRkrn.sys
    Timestamp:        Wed Jul 31 19:34:53 2013 (51F958CD)
    CheckSum:         0002A79F
    ImageSize:        0001E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
The Webroot SecureAnywhere Essentials driver/Webroot SecureAnywhere Anti-virus driver seems to be causing problems, please remove the program completely with Revo Uninstaller Pro - Uninstall Software, Remove Programs easily, Forced Uninstall, Leftovers Uninstaller (couldn't find a removal tool), and then install and run full scans with these free and proven alternatives which work best with the operating system due to compatibility and lightweight nature on system resources.

Install and perform full scans with:
information   Information
Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:
My System SpecsSystem Spec
08 Aug 2013   #20
AlexBrunt

Windows 7 Ultimate x64
 
 

Oh and my laptop is not doing the usual ntfs.sys BSOD, but another one,
could you please check this dump. thanks

Edit #1: My laptop did another ntfs.sys BSOD again,
I attached the new dump file.
I have still not found the source of the problem any chance that it could be faulty ram.
Even though memtest did 10 passes on my uncles laptop.
I would also note that we all bought the same kits of ram and that my laptop is different to my uncles,
but my uncles and my dads laptop are the same.
My System SpecsSystem Spec
Reply

 BSOD after changing from 4GB to 8GB SODIMM RAM




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD after changing ram
Hello there, I have an asus motherboard p7p55-m currentley runing win 7 64 bit. everything was runing fine for 3 years with my good old 2X2GB kit. I Bought 2X4GB sticks, and since then, i get BSOD on my pc for every 10 minutes. very furstrating, can't work.
BSOD Help and Support
Changing account type - changing GUI and desktop customizations, too?
I originally made one account with admin rights on my PC in June. I added a standard account for my dad last week, but the only way I could customize the desktop and theme for him with larger fonts, non-Aero theme, fewer desktop icons, etc was to make his account an admin account also. Otherwise...
General Discussion
Cooler-running SODIMM RAM for notebook??
wondering if any of you hardware gurus are convinced that one type of RAM vs another runs cooler? I see that, on the desktop side, Corsair has some current generation DDR3's that have a heat spreader that, I guess, is supposed to make them cool efficiently, but I have not seen such for notebook. ...
Hardware & Devices
Font size changing whenever changing settings in personalization.
Hello sevenforums! I have a problem with my computer i recently purchased. Here is my story. This all started whenever I wanted to change my text size different by changing my DPI settings. What I did was right click, go to screen resolution, and clicked on "Make text and other items larger or...
General Discussion
Explaining of SODIMM RAM
Hello master... I have acer 4740, and I happened to add to his SODIMM 2gb ram so now 3GB, but even after use for 2 hours vga is damaged. my friend said it was because installing SODIMM with a different PC.:cry: right. sodim originally 1GB DDR3 pc8500 The new 2GB DDR3 10 600 pc. ...
Hardware & Devices
BSOD after changing already changing rams
hi, my system is stock ; vertex2 120gb i7 860 p55a-ud3p value rams ddr3 1333 2x2gb odin pro 550w gtx 460 1gb windows 7 x64 ultimate
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:11.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App