Hi all,
I have been experiencing an assorted bunch of BSODs lately. I recently just upgraded my vcard to an nVidia one. I used to have an ATI gpu because I wanted an all AMD setup (790GX mobo + HD4830 gpu). Thinking that it might be a driver conflict prob, I removed the nvidia display drivers and also used DriverSweeper to clean what's left, but I am still experiencing BSODs.
I tried the windows memory diagnostic app. at first it saw errors on my RAM, so I tested both dual-channel pairs (I have 2 pairs btw, a 2GB and a 4GB) separately. The errors were gone. I even tried memtest86+ 4.10. When I tried memtest, I left it for 2 hours, all passed. I even looped test #5, it passed.
So here I am desperate for help...
Attached are al the dumps. The earliest one is when I still had my ATI HD4830 plugged in. Not sure about the 2 "not dated" ones. The others dated August 7th are already using the nVidia GTX460.
NOTE : I couldn't generate a report using perfmon /report as I am getting a "System cannot find the path specified" error. I am currently running on safe mode.
BSODs:
REFERENCE_BY_POINTER
PAGE_FAULT_IN_NON_PAGED_AREA
SYSTEM_SERVICE_EXCEPTION
IRQL_NOT_LESS_OR_EQUAL
"BAD_POOL" - forgot the error... but it was something about POOL or something
System specs:
- Windows 7 x64 Ultimate (Retail)
- AMD Phenom II 720 BE - 1 year 3 months old
- MSI 790GX-G65 - 7 months old
- 1x2 2GB GEIL DDR3 - 7 months old
- 2x2 4GB Team Elite DDR3 - 3 months old
- Inno3D GTX460 1GB - 5 days old
- Corsair HX520 PSU - 1 year 3 months old
- haven't overclocked any components
I have been experiencing an assorted bunch of BSODs lately. I recently just upgraded my vcard to an nVidia one. I used to have an ATI gpu because I wanted an all AMD setup (790GX mobo + HD4830 gpu). Thinking that it might be a driver conflict prob, I removed the nvidia display drivers and also used DriverSweeper to clean what's left, but I am still experiencing BSODs.
I tried the windows memory diagnostic app. at first it saw errors on my RAM, so I tested both dual-channel pairs (I have 2 pairs btw, a 2GB and a 4GB) separately. The errors were gone. I even tried memtest86+ 4.10. When I tried memtest, I left it for 2 hours, all passed. I even looped test #5, it passed.
So here I am desperate for help...
Attached are al the dumps. The earliest one is when I still had my ATI HD4830 plugged in. Not sure about the 2 "not dated" ones. The others dated August 7th are already using the nVidia GTX460.
NOTE : I couldn't generate a report using perfmon /report as I am getting a "System cannot find the path specified" error. I am currently running on safe mode.
BSODs:
REFERENCE_BY_POINTER
PAGE_FAULT_IN_NON_PAGED_AREA
SYSTEM_SERVICE_EXCEPTION
IRQL_NOT_LESS_OR_EQUAL
"BAD_POOL" - forgot the error... but it was something about POOL or something
System specs:
- Windows 7 x64 Ultimate (Retail)
- AMD Phenom II 720 BE - 1 year 3 months old
- MSI 790GX-G65 - 7 months old
- 1x2 2GB GEIL DDR3 - 7 months old
- 2x2 4GB Team Elite DDR3 - 3 months old
- Inno3D GTX460 1GB - 5 days old
- Corsair HX520 PSU - 1 year 3 months old
- haven't overclocked any components
�� Quote: Originally Posted by Roundhouse 
Hi all,
I have been experiencing an assorted bunch of BSODs lately. I recently just upgraded my vcard to an nVidia one. I used to have an ATI gpu because I wanted an all AMD setup (790GX mobo + HD4830 gpu). Thinking that it might be a driver conflict prob, I removed the nvidia display drivers and also used DriverSweeper to clean what's left, but I am still experiencing BSODs.
I tried the windows memory diagnostic app. at first it saw errors on my RAM, so I tested both dual-channel pairs (I have 2 pairs btw, a 2GB and a 4GB) separately. The errors were gone. I even tried memtest86+ 4.10. When I tried memtest, I left it for 2 hours, all passed. I even looped test #5, it passed.
So here I am desperate for help...
Attached are al the dumps. The earliest one is when I still had my ATI HD4830 plugged in. Not sure about the 2 "not dated" ones. The others dated August 7th are already using the nVidia GTX460.
NOTE : I couldn't generate a report using perfmon /report as I am getting a "System cannot find the path specified" error. I am currently running on safe mode.
BSODs:
REFERENCE_BY_POINTER
PAGE_FAULT_IN_NON_PAGED_AREA
SYSTEM_SERVICE_EXCEPTION
IRQL_NOT_LESS_OR_EQUAL
"BAD_POOL" - forgot the error... but it was something about POOL or something
System specs:
- Windows 7 x64 Ultimate (Retail)
- AMD Phenom II 720 BE - 1 year 3 months old
- MSI 790GX-G65 - 7 months old
- 1x2 2GB GEIL DDR3 - 7 months old
- 2x2 4GB Team Elite DDR3 - 3 months old
- Inno3D GTX460 1GB - 5 days old
- Corsair HX520 PSU - 1 year 3 months old
- haven't overclocked any components
I have been experiencing an assorted bunch of BSODs lately. I recently just upgraded my vcard to an nVidia one. I used to have an ATI gpu because I wanted an all AMD setup (790GX mobo + HD4830 gpu). Thinking that it might be a driver conflict prob, I removed the nvidia display drivers and also used DriverSweeper to clean what's left, but I am still experiencing BSODs.
I tried the windows memory diagnostic app. at first it saw errors on my RAM, so I tested both dual-channel pairs (I have 2 pairs btw, a 2GB and a 4GB) separately. The errors were gone. I even tried memtest86+ 4.10. When I tried memtest, I left it for 2 hours, all passed. I even looped test #5, it passed.
So here I am desperate for help...
Attached are al the dumps. The earliest one is when I still had my ATI HD4830 plugged in. Not sure about the 2 "not dated" ones. The others dated August 7th are already using the nVidia GTX460.
NOTE : I couldn't generate a report using perfmon /report as I am getting a "System cannot find the path specified" error. I am currently running on safe mode.
BSODs:
REFERENCE_BY_POINTER
PAGE_FAULT_IN_NON_PAGED_AREA
SYSTEM_SERVICE_EXCEPTION
IRQL_NOT_LESS_OR_EQUAL
"BAD_POOL" - forgot the error... but it was something about POOL or something
System specs:
- Windows 7 x64 Ultimate (Retail)
- AMD Phenom II 720 BE - 1 year 3 months old
- MSI 790GX-G65 - 7 months old
- 1x2 2GB GEIL DDR3 - 7 months old
- 2x2 4GB Team Elite DDR3 - 3 months old
- Inno3D GTX460 1GB - 5 days old
- Corsair HX520 PSU - 1 year 3 months old
- haven't overclocked any components
Roundhouse
These crashes have 4 apparent causes, that all seem to relate to memory. I see that you have run memtest but wonder if you ran the memory one stick at a time, and checked one mobo slot at a time.
I am assuming you are not overclocking, and not running a raid.
there are a few things you can do to find out the actual cause.
The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do>
1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW
2-Download a 3rd party app called memtestx86, burn it so cd, and run memtest for 5-6 passes. (I know but try it one stick at a time)
3-Event viewer
There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Go to the windows log>application tab.
You want to look for critical errors (they have red in the left column ).
When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.
When you find them please note the event ID, and the source codes and tell us what they are.
4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?
If your driver is missing, or there is a yellow triangle on it, you will need to update it.
5-Driver verifier
Beyond that, please run Verifier with these settings:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, 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).
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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
So, 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).
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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Let us know if you need assistance with this
Ken
Hi Ken,
Thanks for the reply.
Yes you are right, I tested all four sticks on all four slots. So I need to test each stick on its own on all 4 slots? or just on the DIMM 1 slot?
As for your instructions:
for #1, the scan returned no integrity violations
for #2, im currently working on it
- memtest86+ right?
- each stick on DIMM 1?
- what tests do i run? would looping just test #5 for 5-6 passes be alright?
for #3, i saw a couple of app hangs for explorer.exe (evet id 1002). But i think this was when i tried to boot normally but everything was black so I ended the explorer.exe process and ran a new one. so not much help on the event viewer.
for #4, i currently uninstalled the nVidia drivers and also am currently on safe mode and usually only lasts 15 seconds if i ran normally before i again see a BSOD. Is it ok for me to run the verifier while on safe mode?
Thanks for the reply.
Yes you are right, I tested all four sticks on all four slots. So I need to test each stick on its own on all 4 slots? or just on the DIMM 1 slot?
As for your instructions:
for #1, the scan returned no integrity violations
for #2, im currently working on it
- memtest86+ right?
- each stick on DIMM 1?
- what tests do i run? would looping just test #5 for 5-6 passes be alright?
for #3, i saw a couple of app hangs for explorer.exe (evet id 1002). But i think this was when i tried to boot normally but everything was black so I ended the explorer.exe process and ran a new one. so not much help on the event viewer.
for #4, i currently uninstalled the nVidia drivers and also am currently on safe mode and usually only lasts 15 seconds if i ran normally before i again see a BSOD. Is it ok for me to run the verifier while on safe mode?
Just an update...
I just finished running tests on my 2x2GB Team Elite DDR3 sticks and they passed (5 passes, standard tests). When I wake up later, I'll test the 2x1GB GEIL DDR3 sticks.
EDIT : I just used the first memory slot for all the tests.
I just finished running tests on my 2x2GB Team Elite DDR3 sticks and they passed (5 passes, standard tests). When I wake up later, I'll test the 2x1GB GEIL DDR3 sticks.
EDIT : I just used the first memory slot for all the tests.
If all the mem sticks have no errors, is it safe to say that the problem is software/driver related?
I was thinking, since my mobo has an ATI chipset and I now have an nVidia GPU, will installing the ATI southbridge drivers conflict with the nVidia GPU drivers?
I was thinking, since my mobo has an ATI chipset and I now have an nVidia GPU, will installing the ATI southbridge drivers conflict with the nVidia GPU drivers?
Please update these old drivers:
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
What is the result from system file check?
The next step should be enable Driver Verifier as Ken (Zigzag3143) suggested. Look at the instruction he posted. If you like more visible instruction, have a look at this:
Driver Verifier - Enable and Disable
regard,
Tuan
Quote:
wdcsam64 wdcsam64.sys Wed Apr 16 15:39:08 2008 (4805BB2C)
Western Digital External Drive RAID Manager download at WD Support > Downloads > Select Product
Western Digital External Drive RAID Manager download at WD Support > Downloads > Select Product
What is the result from system file check?
The next step should be enable Driver Verifier as Ken (Zigzag3143) suggested. Look at the instruction he posted. If you like more visible instruction, have a look at this:
Driver Verifier - Enable and Disable
regard,
Tuan
Thanks for the reply man!
I'll try to do that once I get back home... Now that you mention it, while doing all these restarts/boot-ups in doing the memtest and all, i experienced a problem when, upon booting-up in safe mode, windows reported an error about a USB device. So I unplugged the WD External Drive, and then was able to boot-up safe mode.
The system file check which I ran yesterday showed no integrity violations.
I'll try to remove the installed DAEMON TOOLS LITE and also run the verifier. BTW, is it ok to run the verifier in safe mode or i should run it in a normal boot-up of windows?
I'll try to do that once I get back home... Now that you mention it, while doing all these restarts/boot-ups in doing the memtest and all, i experienced a problem when, upon booting-up in safe mode, windows reported an error about a USB device. So I unplugged the WD External Drive, and then was able to boot-up safe mode.
The system file check which I ran yesterday showed no integrity violations.
I'll try to remove the installed DAEMON TOOLS LITE and also run the verifier. BTW, is it ok to run the verifier in safe mode or i should run it in a normal boot-up of windows?
It should be run in the normal mode while you use your computer. The idea is for it to stress the drivers and find faulty ones. In the safe mode many drivers do not load. However, it you can't get it to run in normal mode, do try safe mode.
Ok, I'll try to run the verifier on a normal boot.
I still have a question about ATI chipset - nVidia GPU compatibility. Will the ATI southbridge drivers interfere with the nVidia GPU drivers?
I still have a question about ATI chipset - nVidia GPU compatibility. Will the ATI southbridge drivers interfere with the nVidia GPU drivers?
It will run just fine. Nvidia make good card. I usually see Nvidia GPU with intel chipset but yours is fine
�� Quote: Originally Posted by ttran It will run just fine. Nvidia make good card. I usually see Nvidia GPU with intel chipset but yours is fine
Where can I get updates for "Western Digital External Drive RAID Manager" (wdcsam64.sys)?
I mean I have a WD My Book Essential 1TB. It has that nasty virtual drive of which I already took care of about 2 months ago and even updated the drivers for the SES thingy. My prob now is where to locate an updated version of wdcsam64.sys? I can't seem to find anything about Drive Manager drivers on their site and even on Google...
I mean I have a WD My Book Essential 1TB. It has that nasty virtual drive of which I already took care of about 2 months ago and even updated the drivers for the SES thingy. My prob now is where to locate an updated version of wdcsam64.sys? I can't seem to find anything about Drive Manager drivers on their site and even on Google...
Hi guys, this is just a follow-up on my thread:
http://www.sevenforums.com/crashes-d...-2-days-2.html
I enabled the Verifier and upon restarting Windows failed to start so I selected Startup Repair, of which it wasnt able to repair anything =P So then I proceeded to start the machine once again and then encountered a BSOD. Attached is the dump. Since I got a BSOD, I went into safe mode then disabled the Verifier.
Thanks in advance!
http://www.sevenforums.com/crashes-d...-2-days-2.html
I enabled the Verifier and upon restarting Windows failed to start so I selected Startup Repair, of which it wasnt able to repair anything =P So then I proceeded to start the machine once again and then encountered a BSOD. Attached is the dump. Since I got a BSOD, I went into safe mode then disabled the Verifier.
Thanks in advance!
What USB device(s) do you have attached, if any?
The dump is blaming usbfilter.sys, which is a Microsoft USB driver. Don't worry about updating it or anything, it is symptomatic of another cause.
I am suspicious of the driver Tpkd.sys, so check out this link: TPkd.sys Windows process - What is it?
Remove any programs listed there, and see what happens.
I have asked the staff if this thread could be merged with your previous one, just a heads-up.
...Summary of the Dumps:
The dump is blaming usbfilter.sys, which is a Microsoft USB driver. Don't worry about updating it or anything, it is symptomatic of another cause.
I am suspicious of the driver Tpkd.sys, so check out this link: TPkd.sys Windows process - What is it?
Remove any programs listed there, and see what happens.
I have asked the staff if this thread could be merged with your previous one, just a heads-up.
...Summary of the Dumps:
Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Mon Aug 9 20:16:00.936 2010 (UTC - 4:00) System Uptime: 0 days 0:00:11.668 BugCheck D5, {fffff98006dd8e40, 0, fffff880149f51aa, 0} *** WARNING: Unable to verify timestamp for usbfilter.sys *** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys Probably caused by : usbfilter.sys ( usbfilter+41aa ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xD5 PROCESS_NAME: System �������������������������������������������������������������������������������������� Thanks Jonathan_King!
Sorry if I kept on creating new threads for updates. I just wasn't sure if people would be able to see my updates if I used my old thread.
When I enabled the verifier, only the keyboard, mouse, and my netgear usb wifi were connected.
As for Tpkd.sys, it is an InterLok driver for my M-Audio USB Condenser Mic. The mic is the actual InterLok device in order for me to be able to use ProTools on my PC.
After all the memtests, I am now able to use my PC on normal boot-up. So far no BSODs. I was even able to play StarCraft 2 for 18 mins. Usually it doesnt last that long before BSODs creep-in. Seems like my WD My Book external is the culprit. I still need to verify that though. I'll try to connect it again and try to update the firmware and the smartware drivers for it. If BSODs arise, I'll post asap.
Sorry if I kept on creating new threads for updates. I just wasn't sure if people would be able to see my updates if I used my old thread.
When I enabled the verifier, only the keyboard, mouse, and my netgear usb wifi were connected.
As for Tpkd.sys, it is an InterLok driver for my M-Audio USB Condenser Mic. The mic is the actual InterLok device in order for me to be able to use ProTools on my PC.
After all the memtests, I am now able to use my PC on normal boot-up. So far no BSODs. I was even able to play StarCraft 2 for 18 mins. Usually it doesnt last that long before BSODs creep-in. Seems like my WD My Book external is the culprit. I still need to verify that though. I'll try to connect it again and try to update the firmware and the smartware drivers for it. If BSODs arise, I'll post asap.
Roundhouse, I have a WD My Book for my backups and I have no trouble with it at all. Assuming your My Book itself is good, I would suspect something else is triggering the BSOD's.
I'll try to reconfigure my WD My Book later. I need to update the firmware and drivers in order to update the wdcsam64.sys...
I searched around in google though and there are a number of similar incidents where their WD My Book crashed and threw a BAD_POOL_HEADER BSOD. I also experienced that one. It even came to a point that my machine won't boot into safe mode and was telling me that a USB device was causing an error. When I unplugged it, I was abel to boot-up. So far everything is stable. Will check though after I reconnect the external disk later.
I searched around in google though and there are a number of similar incidents where their WD My Book crashed and threw a BAD_POOL_HEADER BSOD. I also experienced that one. It even came to a point that my machine won't boot into safe mode and was telling me that a USB device was causing an error. When I unplugged it, I was abel to boot-up. So far everything is stable. Will check though after I reconnect the external disk later.
Keep us posted.
CarlTR6, You mentioned that you have a WD My Book right? Do you have your Indexing Service running on that drive?
I apologize; I have been offline running errands. No, I do not have indexing service running on mine. I use it for backups and I have it organized. I am not a real big fan of indexing service.
Well, I haven't got around to connecting the WD My Book external drive yet but I got another BSOD. I was playing starcraft 2 and then the screen locked up then the BSOD popped:
MEMORY_MANAGEMENT
I am now seriously considering doing a fresh install of windows 7 on my C: drive partition. I just want to verify with you guys that the aforementioned stop error does not point to memory sticks or hardware in general.
I'm currently running a memtest on the 2x2GB sticks that are currently installed. I have already tested them the other day on a per-stick basis and they passed, so this is just to double check.
Please let me know what you guys find out on the attached dump. thanks!
MEMORY_MANAGEMENT
Code:
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 13321 Additional information about the problem: BCCode: 1a BCP1: 0000000000003452 BCP2: 00000000095C3000 BCP3: FFFFF700010CED90 BCP4: D2100000A4B5FC46 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\081110-21356-01.dmp C:\Users\Anton\AppData\Local\Temp\WER-31090-0.sysdata.xml
I'm currently running a memtest on the 2x2GB sticks that are currently installed. I have already tested them the other day on a per-stick basis and they passed, so this is just to double check.
Please let me know what you guys find out on the attached dump. thanks!
After just 1 pass, memtest found errors!!! I'm not sure what to do next though. Not sure if I would retest the memory sticks 1-by-1 or just bring them to the shop.
Retest them one at a time, hoping you can identify whether it is a bad stick, motherboard slot, or compatibility issue.
Also, take a known good stick and test that stick in each slot.
I retested the first 2 slots with another set of dual channel sticks. The sad thing is that there are errors too. This could be a motherboard slot issue. So now I am retesting but now placing the sticks on slots 3 & 4 and seeing if errors creep up.
BTW, any news on the latest dump that I uploaded?
BTW, any news on the latest dump that I uploaded?
The last DMP you upload is stop code 1A which is memory management. MsMpEng.exe was the process running at the time of crash. It belongs to Microsoft window defender and probably not the cause.
Code:
BugCheck 1A, {3452, 95c3000, fffff700010ced90, d2100000a4b5fc46} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a23 ) Followup: MachineOwner --------- PROCESS_NAME: MsMpEng.exe Hmm... I'm sure I disabled it back when I installed Avast. Yesterday, I removed my Avast and replaced it with the MS Security Essentials. Not sure though if that enabled defender.
If it's a software related issue, the weird thing is I might also be having some motherboard issues too. So far mem slots 3 & 4 are working fine after about an hour of memtest. As for slots 1 & 2, it doesnt even last 10 mins before errors come out.
BTW, thanks for the continued help guys.
If it's a software related issue, the weird thing is I might also be having some motherboard issues too. So far mem slots 3 & 4 are working fine after about an hour of memtest. As for slots 1 & 2, it doesnt even last 10 mins before errors come out.
BTW, thanks for the continued help guys.
Sure, you are welcome
For your question regarding Microsoft security essential and the window defender. When you install MSE, it will automatically use the Microsoft Window Defender as part of its services.
Let's us know if using slot 3 and 4 completely solving the issue
Also, can you please perform system file check:
SFC /SCANNOW Command - System File Checker
I'm sorry if you've done this before
Let us know the result
Tuan
For your question regarding Microsoft security essential and the window defender. When you install MSE, it will automatically use the Microsoft Window Defender as part of its services.
Let's us know if using slot 3 and 4 completely solving the issue
Also, can you please perform system file check:
SFC /SCANNOW Command - System File Checker
I'm sorry if you've done this before
Let us know the result
Tuan
You may try RMAing the motherboard, seeing as you are getting errors.
@Jonathan_King:
Yeah. I'll RMA the mobo tomorrow...
@ttran:
Really? MSE still uses defender? weird...
Once I finish memtesting the slots/sticks, I'll try to do a normal boot while using only slots 3 & 4 and do another SFC /SCANNOW and also check for stability while playing.
Yeah. I'll RMA the mobo tomorrow...
@ttran:
Really? MSE still uses defender? weird...
Once I finish memtesting the slots/sticks, I'll try to do a normal boot while using only slots 3 & 4 and do another SFC /SCANNOW and also check for stability while playing.
�� Quote: Originally Posted by Roundhouse @Jonathan_King:
Yeah. I'll RMA the mobo tomorrow...
Yeah. I'll RMA the mobo tomorrow...
Quote:
@ttran:
Really? MSE still uses defender? weird...
Once I finish memtesting the slots/sticks, I'll try to do a normal boot while using only slots 3 & 4 and do another SFC /SCANNOW and also check for stability while playing.
Really? MSE still uses defender? weird...
Once I finish memtesting the slots/sticks, I'll try to do a normal boot while using only slots 3 & 4 and do another SFC /SCANNOW and also check for stability while playing.
Is it possible that memtest would show false errors? I mean I retested slots 1 & 2 with my good sticks and the errors were gone? Previously it would show errors even on my known good sticks.
Based on tests, my 2x1GB Geil sticks are good, while my 2x2GB Team Elite ones are bad. The Team Elite ones were tested on slots 1 & 2 then slots 3 & 4, all showing errors. While the Geil sticks threw errors while in slots 1 & 2, but no errors in slots 3 & 4. But NOW, when I retested the Geil sticks on slots 1 & 2, i can't see errors anymore and now im currently at the 6th pass. I'm still running it just to make sure though.
I'll still bring the machine to the shop tomorrow anyways for them to do their own tests. AFAIK, the Team Elite sticks and the mobo are doing something fishy.
BTW, sorry but I don't see the point of testing the sticks separately when you have dual channel kits. I mean I'll be using them as pairs anyways and if one of them is bad, i have to RMA the pair. Plus if you go dual, you need to use either slots 1&2 or 3&4, well at least for my mobo. So testing a single stick from a dual kit on each slot is a bit too much. (Don't get me wrong, I did it yesterday but with no negative results)
Based on tests, my 2x1GB Geil sticks are good, while my 2x2GB Team Elite ones are bad. The Team Elite ones were tested on slots 1 & 2 then slots 3 & 4, all showing errors. While the Geil sticks threw errors while in slots 1 & 2, but no errors in slots 3 & 4. But NOW, when I retested the Geil sticks on slots 1 & 2, i can't see errors anymore and now im currently at the 6th pass. I'm still running it just to make sure though.
I'll still bring the machine to the shop tomorrow anyways for them to do their own tests. AFAIK, the Team Elite sticks and the mobo are doing something fishy.
BTW, sorry but I don't see the point of testing the sticks separately when you have dual channel kits. I mean I'll be using them as pairs anyways and if one of them is bad, i have to RMA the pair. Plus if you go dual, you need to use either slots 1&2 or 3&4, well at least for my mobo. So testing a single stick from a dual kit on each slot is a bit too much. (Don't get me wrong, I did it yesterday but with no negative results)
The RAM plan sounds good.
MSE uses the Microsoft anti-malware engine. The late One-Care and present day Defender use(d) the same engine.
When another anti-virus is installed, Defender is turned off.
MSE uses the Microsoft anti-malware engine. The late One-Care and present day Defender use(d) the same engine.
When another anti-virus is installed, Defender is turned off.
UPDATE: I brought my PC to the service center. They found out that my 2x2GB Team Elite is really the problem and they are going to send it to the distributor for a replacement.
WEIRD THINGS: I told them I did a couple of memtests and came to a conclusion that the Team Elite ones are the problem, so they also did a memtest right there on the spot. The weird thing was that the technician was a bit impatient.He told me that he usually just uses Prime95 since it is quicker in finding errors. True enough, in less than a minute we found errors and officially tagged the sticks for RMA. So does that mean Prime95 is a better test than memtest?
Another weird thing is that the guy mentioned that mixing 2 dual channel kits with different brnds is not recommended and WILL cause errors. Is that true? The only odd thing I noticed from mixing kits from diff manufacturers is that even though they have the same speed, 1333MHz, it gets clocked down to 800MHz.
WEIRD THINGS: I told them I did a couple of memtests and came to a conclusion that the Team Elite ones are the problem, so they also did a memtest right there on the spot. The weird thing was that the technician was a bit impatient.He told me that he usually just uses Prime95 since it is quicker in finding errors. True enough, in less than a minute we found errors and officially tagged the sticks for RMA. So does that mean Prime95 is a better test than memtest?
Another weird thing is that the guy mentioned that mixing 2 dual channel kits with different brnds is not recommended and WILL cause errors. Is that true? The only odd thing I noticed from mixing kits from diff manufacturers is that even though they have the same speed, 1333MHz, it gets clocked down to 800MHz.
Yes, it is not a good idea to mix RAM, especially dual and triple channel. If possible, it's best to buy all RAM at the same time.
Interesting about the Prime95, I'll have to do some research on that with future threads.
I don't think Prime95 will identify which sticks are bad, but perhaps it could be used as a preliminary test to see if any memory issues are present.
Interesting about the Prime95, I'll have to do some research on that with future threads.
I don't think Prime95 will identify which sticks are bad, but perhaps it could be used as a preliminary test to see if any memory issues are present.
Ok. Whew, i was quite happy that mixing 2 dual channel kits from different manufacturers didn't void the warranty 
Yeah, I heard about Prime95 but was skeptic since it is ran on windows. I was thinking what if a stop error occured just as Prime95 finds the error, then the test was all for nothing. But the tech reassured me that it wont BSOD.
I might use it to burn-in the new replacement mem sticks when I get them.
Yeah, I heard about Prime95 but was skeptic since it is ran on windows. I was thinking what if a stop error occured just as Prime95 finds the error, then the test was all for nothing. But the tech reassured me that it wont BSOD.
I might use it to burn-in the new replacement mem sticks when I get them.
I am glad to hear that you isolated your problem. That is good news. Jonathan is spot on; don't mix RAM. That is asking for trouble. Post back when you get your new RAM installed and let us know how you are running.
Just an update:
I'll be getting my replacement 2x2GB DDR3s tomorrow and I'm stoked. Hehehehe.
So far my machine has been stable while using the 2x1GB sticks while waiting for the replacement sticks for the defective 2x2GBs.
Thanks guys for helping me out big time!
I'll be getting my replacement 2x2GB DDR3s tomorrow and I'm stoked. Hehehehe.
So far my machine has been stable while using the 2x1GB sticks while waiting for the replacement sticks for the defective 2x2GBs.
Thanks guys for helping me out big time!
You're welcome. 
I wish you the best of luck with the RAM...keep us posted!
I wish you the best of luck with the RAM...keep us posted!
�� Quote: Originally Posted by Roundhouse Just an update:
I'll be getting my replacement 2x2GB DDR3s tomorrow and I'm stoked. Hehehehe.
So far my machine has been stable while using the 2x1GB sticks while waiting for the replacement sticks for the defective 2x2GBs.
Thanks guys for helping me out big time!
I'll be getting my replacement 2x2GB DDR3s tomorrow and I'm stoked. Hehehehe.
So far my machine has been stable while using the 2x1GB sticks while waiting for the replacement sticks for the defective 2x2GBs.
Thanks guys for helping me out big time!
Let us know when you install the new RAM. Hey guys,
I got my RMA'd RAM last Tuesday. My system has been stable for quite a while. But just now as I was playing StarCraft 2 (yup, the app that started it all =P), I got another BSOD. A MEMORY_MANAGEMENT BSOD.
Attached is the dump. Please let me know what you find.
I got my RMA'd RAM last Tuesday. My system has been stable for quite a while. But just now as I was playing StarCraft 2 (yup, the app that started it all =P), I got another BSOD. A MEMORY_MANAGEMENT BSOD.
Attached is the dump. Please let me know what you find.
That is not the news we wanted to hear! I will take a look.
Error code 1A, MEMORY_MANAGEMENT. Usual causes are device driver, memory, kernel.
The dump does not point to anything specific. Make sure your new RAM is seated securely. I know you got new RAM, did you RMA the motherboard also?
I find a very old driver and another old driver that may be the sources of your problem. They certainly are not doing any good toward system stability.
lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. TAGES, the AAA Copy Protection System This software is way obsolete. Uninstall it.
wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID ManagerWD Support > Downloads > Select Product. Update this driver. Go to the Western Digital site and search for the driver.
Post back when you ave uninstalled that copy protection program and updated the Western Digital RAID driver.
Error code 1A, MEMORY_MANAGEMENT. Usual causes are device driver, memory, kernel.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_083010-31184-01.zip\083010-31184-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`0344f000 PsLoadedModuleList = 0xfffff800`0368ce50 Debug session time: Sun Aug 29 19:13:12.551 2010 (GMT-4) System Uptime: 0 days 9:02:03.283 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41289, ff162001, 2361, ff160c05} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a49 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041289, The subtype of the bugcheck. Arg2: 00000000ff162001 Arg3: 0000000000002361 Arg4: 00000000ff160c05 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41289 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003514379 to fffff800034bf740 STACK_TEXT: fffff880`07317988 fffff800`03514379 : 00000000`0000001a 00000000`00041289 00000000`ff162001 00000000`00002361 : nt!KeBugCheckEx fffff880`07317990 fffff800`03547cc5 : 00000000`07008001 fffffa80`063e3560 fffff880`07317ca0 fffffa80`063e3560 : nt! ?? ::FNODOBFM::`string'+0x4a49 fffff880`073179d0 fffff800`037a6f31 : fffff880`00000010 fffffa80`065ddb01 fffffa80`065ddb30 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x52eb0 fffff880`07317ac0 fffff800`034be993 : 00000000`00000898 fffffa80`0651c060 00000000`00001f80 00000000`02d2ebe8 : nt!NtQueryVirtualMemory+0x67f fffff880`07317bb0 00000000`76f3ff8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`02d2ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f3ff8a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+4a49 fffff800`03514379 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4a49 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a49 BUCKET_ID: X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a49 Followup: MachineOwner ---------
I find a very old driver and another old driver that may be the sources of your problem. They certainly are not doing any good toward system stability.
lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. TAGES, the AAA Copy Protection System This software is way obsolete. Uninstall it.
wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID ManagerWD Support > Downloads > Select Product. Update this driver. Go to the Western Digital site and search for the driver.
Post back when you ave uninstalled that copy protection program and updated the Western Digital RAID driver.
�� Quote: Originally Posted by CarlTR6 That is not the news we wanted to hear!
The Tages app was from The Chronicles of Riddick game that I just installed. As for the WD driver, i'll try to update it. It's just weird that the only updates that I could find in the WD site are firmware ones. Probably the drivers are in the included virtual cd within the firmware.
As for the Tages DRM, I don't think the game will run without it. I'll try to see if there are updates for it.
BTW, I didn't RMA the mobo. It was stable as I was waiting for the RMA'd RAM and was using a back up set of sticks.
EDIT: I just updated the Tages DRM and the WD drivers and also refitted the RAM. I'll observe how things play out and post.
Very good - and we hope for GOOD news this time!!
After almost a week of stable use, I got another BSOD.... but this time it is different.
After I re-fit the mem modules last weekend, my mem BSODs were gone. This new BSOD has the code for NTFS_FILE_SYSTEM. I left my computer open for about 2 hours so I didn't really see it bomb out. When I came back, I just saw a notification that it restarted unexpectedly. I used BlueScreenView to inspect the new dump file to be able to see the error message.
Attached is the dump.
Is my harddisk failing already?? It's not exactly old. It's just over a year old.
After I re-fit the mem modules last weekend, my mem BSODs were gone. This new BSOD has the code for NTFS_FILE_SYSTEM. I left my computer open for about 2 hours so I didn't really see it bomb out. When I came back, I just saw a notification that it restarted unexpectedly. I used BlueScreenView to inspect the new dump file to be able to see the error message.
Attached is the dump.
Is my harddisk failing already?? It's not exactly old. It's just over a year old.
I would suggest a disk check/hard drive diagnostic.
Open an elevated command prompt and enter chkdsk /r.
HD Diagnostic
Install these network drivers: Realtek
...Summary of the Dumps:
Open an elevated command prompt and enter chkdsk /r.
HD Diagnostic
Install these network drivers: Realtek
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sat Sep 4 16:25:50.358 2010 (UTC - 4:00) System Uptime: 0 days 11:23:39.090 BugCheck 24, {1904fb, fffff88007c192f8, fffff88007c18b60, fffff880010cd884} Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+164 ) PROCESS_NAME: MsMpEng.exe BUGCHECK_STR: 0x24 �������������������������������������������������������������������������������������� Alright, I'll check with those tools. Thanks!
Hi guys,
I got a couple of BSODs again. This time a couple of PFN_LIST_CORRUPT errors and 1 MEMORY_MANAGEMENT error.
Can you guys please look into these?
For good measure, I'll be doing a reformat and a clean install on my C: drive. A clean install might solve a couple of these instability issues...
Thanks in advance guys!
I got a couple of BSODs again. This time a couple of PFN_LIST_CORRUPT errors and 1 MEMORY_MANAGEMENT error.
Can you guys please look into these?
For good measure, I'll be doing a reformat and a clean install on my C: drive. A clean install might solve a couple of these instability issues...
Thanks in advance guys!
All of three of the dumps indicate memory management or memory corruption issues.
Did you run Check Disk? If so, what were the results?
I see that you updated your Realtek drivers. Good job. I still find out of date drivers including two really obsolete ones. Before you do a reinstall, update these drivers. Out of date drivers can and do cause memory corruption.
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41284, 4ade001, 0, fffff70001080000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041284, A PTE or the working set list is corrupt. Arg2: 0000000004ade001 Arg3: 0000000000000000 Arg4: fffff70001080000 --------------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, 3dacd, 2, 3da45} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 0: 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: 0000000000000099, A PTE or PFN is corrupt Arg2: 000000000003dacd, page frame number Arg3: 0000000000000002, current page state Arg4: 000000000003da45, 0 ------------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, b824b, 2, b8248} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 1: 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: 0000000000000099, A PTE or PFN is corrupt Arg2: 00000000000b824b, page frame number Arg3: 0000000000000002, current page state Arg4: 00000000000b8248, 0 I see that you updated your Realtek drivers. Good job. I still find out of date drivers including two really obsolete ones. Before you do a reinstall, update these drivers. Out of date drivers can and do cause memory corruption.
Quote:
atksgt.sys Sun May 17 09:36:34 2009 - belongs to the software atksgt by Tages SA. Update the driver or uninstall the software.
lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. This software is obsolete; uninstall it.
Tpkd.sys Thu May 21 17:36:18 2009 - InterLok system file belongs to the software InterLok(R) or InterLok Driver Kit or TPkd or Sonic RecordNow! or Adobe eBook Migration Utility or Interlok driver setup x or nGenius InfiniStream by PACE Anti-Piracy, Inc (www.paceap.com). Update the driver or uninstall the software.
wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID Manager WD Support > Downloads > Select Product. Update this driver.
lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. This software is obsolete; uninstall it.
Tpkd.sys Thu May 21 17:36:18 2009 - InterLok system file belongs to the software InterLok(R) or InterLok Driver Kit or TPkd or Sonic RecordNow! or Adobe eBook Migration Utility or Interlok driver setup x or nGenius InfiniStream by PACE Anti-Piracy, Inc (www.paceap.com). Update the driver or uninstall the software.
wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID Manager WD Support > Downloads > Select Product. Update this driver.
�� Quote: Originally Posted by CarlTR6 atksgt.sys Sun May 17 09:36:34 2009 - belongs to the software atksgt by Tages SA. Update the driver or uninstall the software.
lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. This software is obsolete; uninstall it.
Tpkd.sys Thu May 21 17:36:18 2009 - InterLok system file belongs to the software InterLok(R) or InterLok Driver Kit or TPkd or Sonic RecordNow! or Adobe eBook Migration Utility or Interlok driver setup x or nGenius InfiniStream by PACE Anti-Piracy, Inc (www.paceap.com). Update the driver or uninstall the software.
wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID Manager WD Support > Downloads > Select Product. Update this driver.
lirsgt.sys Sat Mar 06 14:53:01 2004 - belongs to the software lirsgt by Tages SA. This software is obsolete; uninstall it.
Tpkd.sys Thu May 21 17:36:18 2009 - InterLok system file belongs to the software InterLok(R) or InterLok Driver Kit or TPkd or Sonic RecordNow! or Adobe eBook Migration Utility or Interlok driver setup x or nGenius InfiniStream by PACE Anti-Piracy, Inc (www.paceap.com). Update the driver or uninstall the software.
wdcsam64.sys Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID Manager WD Support > Downloads > Select Product. Update this driver.
I have already updated that Tages driver around 2 weeks ago and also the WD drivers. I don't know why it keeps showing as unupdated....
I suspect that it updated to the latest driver available. If there is not a driver dated July 13, 2009 or later, it is not updated for Win 7. You might get by with the May 17, 2009 driver, which is a Vista driver. The 2008 driver will cause problems. You need to uninstall the Tages software associated with the 2008 driver. It is obsolete software not designed to run on Win 7. It will cause conflicts and crashes. It is like trying run a 1960's VW Beetle suspension on a new Ferrari; it ain't gonna work.
�� Quote: Originally Posted by CarlTR6 It is like trying run a 1960's VW Beetle suspension on a new Ferrari; it ain't gonna work.
I'm trying to look into a pattern here... BSODs usually creep up after around 9-10 hrs of continued computer use. Could that be an issue? I also have an nVidia GTX460 gpu and have a 520w Corsair PSU. I have read in other forums that i should be ok, but could it be voltage drops that's been causing the BSODs after a number of hours use? Is that even possible?
�� Quote: Originally Posted by Roundhouse �� Quote: Originally Posted by CarlTR6 It is like trying run a 1960's VW Beetle suspension on a new Ferrari; it ain't gonna work.
I'm trying to look into a pattern here... BSODs usually creep up after around 9-10 hrs of continued computer use. Could that be an issue? I also have an nVidia GTX460 gpu and have a 520w Corsair PSU. I have read in other forums that i should be ok, but could it be voltage drops that's been causing the BSODs after a number of hours use? Is that even possible?
If your BSOD's are caused by conflicts, they can happen anytime when the right combination of memory requests occur that conflict. It is possible for the conflict to be occurring and finally reaching the crash point - like pot of water finally reaching the boiling point. Keep in mind that Win 7 does not like obsolete third party drivers. These drivers were not engineered for the Win 7 OS. Win 7 is not an evolution from XP; it is a totally new OS.
�� Quote: Originally Posted by CarlTR6 Keep in mind that Win 7 does not like obsolete third party drivers. These drivers were not engineered for the Win 7 OS. Win 7 is not an evolution from XP; it is a totally new OS.
OK, but if you don't want to go through the hassle of reinstalling all of your apps, just uninstall the obsolete ones. Either way, let us know. We want to see you running smoothly.
As I was doing a clean install, I got a BSOD just as it came back from it's first restart and was just finishing up the install...
Does that mean that my BSODs are hardware related?
EDIT: Ouch! I tried to install again, I still got a BSOD right smack as it was completing the install.... hmmm... is it too consistent to be a hardware error? Could it be an installation disc error?
EDIT: I tried for a 3rd time, but I still got a BSOD! oh man... I can't even install Windows now? *sigh*
Does that mean that my BSODs are hardware related?
EDIT: Ouch! I tried to install again, I still got a BSOD right smack as it was completing the install.... hmmm... is it too consistent to be a hardware error? Could it be an installation disc error?
EDIT: I tried for a 3rd time, but I still got a BSOD! oh man... I can't even install Windows now? *sigh*
Yes, it can be hardware or a corrupt installation media. I will see if I can get one of the installation guys involved. In the meantime, you can try removing all but one RAM stick and see if you can complete the installation.
�� Quote: Originally Posted by CarlTR6 In the meantime, you can try removing all but one RAM stick and see if you can complete the installation.
Roundhouse,
To put your system on the level:
1. Go to the manufacturer's website. If you do not have the latest bios installed, then--download and install same.
2. Perform Step 1.
3. Perform a 100% clean install as explained in following link. Be sure to use the DiskPart CLEAN ALL command (and not simply CLEAN).
SSD / HDD : Optimize for Windows Reinstallation
4. do NOT install any additional drivers,
5. do go to the MS update site and update your system.
6. Make a complete System Image backup of your system using the procedure given in following link:
Backup Complete Computer - Create an Image Backup
7. Make a System Repair Disc. Using a computer without having a System Repair Disc is like driving a car without a spare tire.
________________________________________
DISC - CREATE A SYSTEM REPAIR DISC
START | type System Repair | Enter key | Create Disc button
________________________________________
________________________________________
To put your system on the level:
1. Go to the manufacturer's website. If you do not have the latest bios installed, then--download and install same.
2. Perform Step 1.
3. Perform a 100% clean install as explained in following link. Be sure to use the DiskPart CLEAN ALL command (and not simply CLEAN).
SSD / HDD : Optimize for Windows Reinstallation
4. do NOT install any additional drivers,
5. do go to the MS update site and update your system.
6. Make a complete System Image backup of your system using the procedure given in following link:
Backup Complete Computer - Create an Image Backup
7. Make a System Repair Disc. Using a computer without having a System Repair Disc is like driving a car without a spare tire.
________________________________________
DISC - CREATE A SYSTEM REPAIR DISC
START | type System Repair | Enter key | Create Disc button
________________________________________
________________________________________
Follow these directions for testing RAM. Particularly note Part 3: RAM - Test with Memtest86+
Either that one stick you took out is bad, the motherboard slot is faulty, or you are using incompatible RAM.
Either that one stick you took out is bad, the motherboard slot is faulty, or you are using incompatible RAM.
As I did another reboot, I came upon a BSOD, a KMODE_EXCEPTION_NOT_HANDLED.
Attached is the dump.
Attached is the dump.
�� Quote: Originally Posted by Roundhouse As I did another reboot, I came upon a BSOD, a KMODE_EXCEPTION_NOT_HANDLED.
Attached is the dump.
Attached is the dump.
Honestly, this looks like bad hardware corrupting memory - either bad RAM itself, or a bum CPU (it's failing coming out of CPU idle). I can't tell you which CPU core failed (as it's only a minidump), but the PRCB is there, so I know it is one of the cores failing to respond to an IDLE request properly (there's no overclocking going on here, btw):
Code:
0: kd> kb RetAddr : Args to Child : Call Site fffff800`02ec1c2e : fffffa80`033b0d40 fffffa80`0421ca98 fffff800`00b9c2b0 fffff800`02ef6e28 : nt!KeBugCheck fffff800`02eefbed : fffff800`030d6f78 fffff800`030151d0 fffff800`02e58000 fffff800`00b9ca58 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`02ef7250 : fffff800`03017b5c fffff800`00b9bbe8 fffff800`00b9ca58 fffff800`02e58000 : nt!RtlpExecuteHandlerForException+0xd fffff800`02f041b5 : fffff800`00b9ca58 fffff800`00b9c2b0 fffff800`00000000 00000000`00000001 : nt!RtlDispatchException+0x410 fffff800`02ec9542 : fffff800`00b9ca58 00000000`00000000 fffff800`00b9cb00 fffff800`03042e80 : nt!KiDispatchException+0x135 fffff800`02ec80ba : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`02d84240 : nt!KiExceptionDispatch+0xc2 fffff880`0213d471 : fffffa80`02d7cc10 fffff800`02ed7a3a fffffa80`0184a990 fffffa80`02d911f8 : nt!KiPageFault+0x23a fffffa80`02d7cc10 : fffff800`02ed7a3a fffffa80`0184a990 fffffa80`02d911f8 fffff800`03050c40 : 0xfffff880`0213d471 fffff800`02ed7a3a : fffffa80`0184a990 fffffa80`02d911f8 fffff800`03050c40 00000000`00000002 : 0xfffffa80`02d7cc10 fffff800`02ed26cc : fffff800`03042e80 fffff800`00000000 00000000`00000000 fffff880`00e0bf44 : nt!PoIdle+0x53a 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x2c 0: kd> !prcb 0xfffff800`03042e80 Cannot get PRCB address 0: kd> !sysinfo cpuinfo [CPU Information] ~MHz = REG_DWORD 2812 Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0 Identifier = REG_SZ AMD64 Family 16 Model 4 Stepping 2 ProcessorNameString = REG_SZ AMD Phenom(tm) II X3 720 Processor VendorIdentifier = REG_SZ AuthenticAMD
I am glad you were able to complete the installation. I felt the crashes were hardware related rather than corrupted media. I hope you followed Karl's advice and created a system image and a rescue disk. If not, please do so.
Based on Jonathan's analysis and that of culberti plus rereading this whole thread, I believe you have a serious hardware problem. I know you have just installed new RAM. But that is no guarantee that it is not defective or mismatched. As Jonathan stated you may well have a bad RAM slot. Based cluberti's and Jonathan's expertise, I will add the motherboard and CPU to my list of suspicions.
You can run Memtest and then run Prime. Here are the tutorials:
RAM - Test with Memtest86+
http://www.sevenforums.com/tutorials...t-prime95.html
But since your computer is still under warranty, I would take it back to the service center. Make a list of what you have done, what you have encountered, and when these things happened. Be sure you list the games your were running when the crashes occurred and list what you had to do to reinstall Windows. Your recent mini dumps are still on your computer? If not, they are here in this thread. I would get it repaired properly under warranty.
Please keep us updated.
Based on Jonathan's analysis and that of culberti plus rereading this whole thread, I believe you have a serious hardware problem. I know you have just installed new RAM. But that is no guarantee that it is not defective or mismatched. As Jonathan stated you may well have a bad RAM slot. Based cluberti's and Jonathan's expertise, I will add the motherboard and CPU to my list of suspicions.
You can run Memtest and then run Prime. Here are the tutorials:
RAM - Test with Memtest86+
http://www.sevenforums.com/tutorials...t-prime95.html
But since your computer is still under warranty, I would take it back to the service center. Make a list of what you have done, what you have encountered, and when these things happened. Be sure you list the games your were running when the crashes occurred and list what you had to do to reinstall Windows. Your recent mini dumps are still on your computer? If not, they are here in this thread. I would get it repaired properly under warranty.
Please keep us updated.
�� Quote: Originally Posted by pebbly �� Quote: Originally Posted by Roundhouse As I did another reboot, I came upon a BSOD, a KMODE_EXCEPTION_NOT_HANDLED.
Attached is the dump.
Attached is the dump.
�� Quote: Originally Posted by CarlTR6 I am glad you were able to complete the installation. I felt the crashes were hardware related rather than corrupted media. I hope you followed Karl's advice and created a system image and a rescue disk. If not, please do so.
Based on Jonathan's analysis and that of culberti plus rereading this whole thread, I believe you have a serious hardware problem. I know you have just installed new RAM. But that is no guarantee that it is not defective or mismatched. As Jonathan stated you may well have a bad RAM slot. Based cluberti's and Jonathan's expertise, I will add the motherboard and CPU to my list of suspicions.
You can run Memtest and then run Prime. Here are the tutorials:
RAM - Test with Memtest86+
http://www.sevenforums.com/tutorials...t-prime95.html
But since your computer is still under warranty, I would take it back to the service center. Make a list of what you have done, what you have encountered, and when these things happened. Be sure you list the games your were running when the crashes occurred and list what you had to do to reinstall Windows. Your recent mini dumps are still on your computer? If not, they are here in this thread. I would get it repaired properly under warranty.
Please keep us updated.
Based on Jonathan's analysis and that of culberti plus rereading this whole thread, I believe you have a serious hardware problem. I know you have just installed new RAM. But that is no guarantee that it is not defective or mismatched. As Jonathan stated you may well have a bad RAM slot. Based cluberti's and Jonathan's expertise, I will add the motherboard and CPU to my list of suspicions.
You can run Memtest and then run Prime. Here are the tutorials:
RAM - Test with Memtest86+
http://www.sevenforums.com/tutorials...t-prime95.html
But since your computer is still under warranty, I would take it back to the service center. Make a list of what you have done, what you have encountered, and when these things happened. Be sure you list the games your were running when the crashes occurred and list what you had to do to reinstall Windows. Your recent mini dumps are still on your computer? If not, they are here in this thread. I would get it repaired properly under warranty.
Please keep us updated.
).During the time I was still using DDR2 hardware, I even got my AMD CPU RMA'd. When I moved to DDR3, everything was peachy for around 10 months before all these BSODs happened.
Honestly, I'm dead tired of doing RAM tests on memtest86+... I might just go for Prime95 and see things from there.
I'll observe things especially right now that I have a fresh install.
BTW, I followed Karl's advice, I backed up my install and created a repair disc.
EDIT : Forgot to say this.... thanks guys for helping me out! I'll continue to update you guys as I go along.
Keep us informed and may all go well.
Just read through your thread, you've been getting some very good help.
Heat can cause crashes and will aggravate any hardware problems that you might be having.
Checking a few settings will give us more to go on.
There are a couple of questions that should help clarify some of the hardware issues.
Did you find an update for your BIOS?
Have you been checking your temperatures?
Use Speed Fan or Core Temp , run one of these and check the CPU temps when at idle, testing, and/or gaming.
Let us know the minimum and maximum temps you get.
If you don't already have CPUZ then D/L it and post a snip of the CPU, Mainboard, Memory, and SPD (for all the types of RAM your running) 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
Go to your BIOS and tell us the RAM, CPU and North Bridge (NB) voltages.
What RAM are you running in your computer now?
Your system specs states: 2x2 Team Elite DDR3 / 1x2 GEIL DDR3, are you running four RAM cards?
Four RAM cards will usually need a little adjusting to run stable.
cluberti found a reference to a core failure, this needs to be looked at. The cause can be from RAM or the CPU as he mentioned.
Lets check the settings and temperatures, to see where we can start from.
Heat can cause crashes and will aggravate any hardware problems that you might be having.
Checking a few settings will give us more to go on.
There are a couple of questions that should help clarify some of the hardware issues.
Did you find an update for your BIOS?
Have you been checking your temperatures?
Use Speed Fan or Core Temp , run one of these and check the CPU temps when at idle, testing, and/or gaming.
Let us know the minimum and maximum temps you get.
If you don't already have CPUZ then D/L it and post a snip of the CPU, Mainboard, Memory, and SPD (for all the types of RAM your running) 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
Go to your BIOS and tell us the RAM, CPU and North Bridge (NB) voltages.
What RAM are you running in your computer now?
Your system specs states: 2x2 Team Elite DDR3 / 1x2 GEIL DDR3, are you running four RAM cards?
Four RAM cards will usually need a little adjusting to run stable.
cluberti found a reference to a core failure, this needs to be looked at. The cause can be from RAM or the CPU as he mentioned.
Lets check the settings and temperatures, to see where we can start from.
�� Quote: Originally Posted by Dave76 Just read through your thread, you've been getting some very good help.
Heat can cause crashes and will aggravate any hardware problems that you might be having.
Checking a few settings will give us more to go on.
There are a couple of questions that should help clarify some of the hardware issues.
Did you find an update for your BIOS?
Have you been checking your temperatures?
Use Speed Fan or Core Temp , run one of these and check the CPU temps when at idle, testing, and/or gaming.
Let us know the minimum and maximum temps you get.
If you don't already have CPUZ then D/L it and post a snip of the CPU, Mainboard, Memory, and SPD (for all the types of RAM your running) 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
Go to your BIOS and tell us the RAM, CPU and North Bridge (NB) voltages.
What RAM are you running in your computer now?
Your system specs states: 2x2 Team Elite DDR3 / 1x2 GEIL DDR3, are you running four RAM cards?
Four RAM cards will usually need a little adjusting to run stable.
cluberti found a reference to a core failure, this needs to be looked at. The cause can be from RAM or the CPU as he mentioned.
Lets check the settings and temperatures, to see where we can start from.
Heat can cause crashes and will aggravate any hardware problems that you might be having.
Checking a few settings will give us more to go on.
There are a couple of questions that should help clarify some of the hardware issues.
Did you find an update for your BIOS?
Have you been checking your temperatures?
Use Speed Fan or Core Temp , run one of these and check the CPU temps when at idle, testing, and/or gaming.
Let us know the minimum and maximum temps you get.
If you don't already have CPUZ then D/L it and post a snip of the CPU, Mainboard, Memory, and SPD (for all the types of RAM your running) 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
Go to your BIOS and tell us the RAM, CPU and North Bridge (NB) voltages.
What RAM are you running in your computer now?
Your system specs states: 2x2 Team Elite DDR3 / 1x2 GEIL DDR3, are you running four RAM cards?
Four RAM cards will usually need a little adjusting to run stable.
cluberti found a reference to a core failure, this needs to be looked at. The cause can be from RAM or the CPU as he mentioned.
Lets check the settings and temperatures, to see where we can start from.
As for the RAM, I am currently using only the 2x2 Team Elite DDR3 RAM sticks. I already removed the GeIL ones.
As for the BIOS, it is currently updated to the latest version. I updated it prior to reformatting and reinstalling Win7 x64.
As for checking the temps, I'm currently using HWMonitor from cpuid.com. So far the temps are fine. When I played games like GTA4, the GPU temps topped at around 60+ I think. I need to do another check using GTA4 for the GPU and Prime 95 for CPU temp benchmarking.
I'll also try to post the voltages.
Thanks for letting us know the results.
Glad to hear you got it runing stable, mixing RAM can cause lots of problems.
Let us know how the how the other tests are going.
Glad to hear you got it runing stable, mixing RAM can cause lots of problems.
Let us know how the how the other tests are going.
Roundhouse, that is good news. Looks like the mixed RAM types were not helping you any.
Không có nhận xét nào:
Đăng nhận xét