HELP REQUIRED PLEASE!! WIN 7 64 bit system

[EnemyWithin]

Built-in Administrator Account - Enable or Disable

 

[Nomad8459]

The minidump files are uploaded as far as i am aware, please see an earlier reply on this thread.......even after defaulting the BIOS, the system is running for around 20-30 mins and then shutting down.....


All help appreciated, thanks

 

[CommonTater]

OK here is the deal...... new PC arrives

Operative term here "new PC"... as in "under warranty".... send it back and get one that actually works.

 

[EnemyWithin]

This the analysis of your minidup files, but I'm afraid I'm in unknown territories lol


Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 4/10/2010 16:19:44 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E52B7E, 0x0, 0x80000000004)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\041010-19297-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 4/11/2010 10:47:12 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80021C9A50, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\041110-19328-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 4/10/2010 14:55:36 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80023636A0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\041010-16614-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 4/10/2010 15:56:26 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800214F7A0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\041010-25256-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 4/11/2010 11:01:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002DB8D9C, 0x0, 0x10000000000)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\041110-22105-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 4/10/2010 15:28:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80023E1DF0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\041010-20701-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 4/11/2010 10:57:14 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF98000DAE6DF, 0x8, 0xFFFFF98000DAE6DF, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\041110-19843-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[EnemyWithin]

... though it appears (to me) that 5 out of 7 craches are caused by some memory faults probably hardware side. I would power off the pc, reinsert the memory modules and check their operating voltage and timings : start the system and boot from a memtest CD.
If there are errors, I'd try to manually set up the RAM parameters in the bios and re-run the test.

 

[gregrocker]

Run the memtest overnight or at least 6 passes to get a clear fix on which sticks are bad to RMA them.

With a new computer you want your (included one-year) Tech Support to be in on this so they can properly RMA the bad parts or the entire machine if necessary.

I'd give them one shot at replacing bad parts (likely RAM) before asking for machine RMA or refund.

 

[Nomad8459]

Hey guys, thanks for your help with this, i have kind of been reluctant to admit defeat as i have installed quite a bit of software already, the PC runs fine and allows all operations such as install, web browsing, etc, etc, the system itself seems fairly stable in terms of the OS but just randomly crashes all the time, windows detects the memory as i say and can see that there is 8GB installed, i am minded that it is probably driver related rather than hardware, but i am no expert, i understand the comments about tech support and they have been contacted, ( they are not open at weekends thouigh ) it is just really infuriating that although at times i seem to have a good healthy system that it will just randomly crash like this.

There doesnt seem to be one trigger, for example i can download lots of things and install but i have tried several times to install AVG and every time while downloading, the system will crash, it just all seems too random, having done some research, i was tempted to believe that something may be going on with the RAM timings, etc, the RAM slots are dual channel architecture and all four are used in this configuration, the RAM is samsung DDR 2 6400 800mhz 4x2GB and i have heard that timings can be important.

From what i have read, things like 4-4-4-12 are taljked about.

When i looked in the bios however, the number strings seemed much longer than this and it just confused me, i tried to research what the RAM timings should be for this particular RAM but didnt get anywhere, i dont know if anyone on here could shed some light.

I may have to give in, in the end as i feel every time i take a step forward with this system, it knocks me back four.

If anyone can shed light on RAM timings and they believ this will help, then i would be grateful to hear from you.

I installed driver detective which seems to say that there are four driver related issues, these were: nvidia chipset, via hd audio, realtek hd audio and a driver for my HP psc2355c which is an all in one printer/scanner/copier.

The chipset driver which i think could be the main issue is very large indeed and the system always crashes before i can complete the download, does anyone think that this driver is the culprit? and will installing the latest driver help or fix this? or is it more a case of the fact that the available driver needs some sort of hotfix or patch in order to operate properly, it did bother me that i am trying to run an ATI graphics card on a NVIDIA chipset motherboard and i wondered if there were issues due to this........

Thanks

 

[gregrocker]

Troubleshoot by studying the Event Viewer>Admin view and Perfomance-Diagnostics log accessed at Control Panel\All Control Panel Items\Performance Information and Tools\Advanced Tools for repeat errors or errors occuring just before or during crashes.

Generate a System Health report and look for cued issues while on Advanced Tools page.

Have you eliminated a virus as a possiblity? Install and run Microsoft Security Essentials full scan, then run Spybot S&D in Safe Mode after installing and updating from desktop. Spybot can flush viruses from memory.

Test your memory with memtest86 for at least 6 passes, then run full scan of HD's maker's diagnostics/repair CD from here: Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Run sfc /scannow from elevated CMD to check for corrupt system files.

Finally, run a http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R which is next best thing to reinstall but saves your programs and settings. You will need to borrow or obtain a 64 bit WIn7 installer of your version to do this, but you want one anyway to get the cleanest possible install.

 

[Nomad8459]

Well, decided to do something that i thought of earlier which i now wish i had done much soooooner as it were, i don't know if this is the final answer but i noticed that on start up when pressing F5 at the ASUS boot screen with the Windows 7 install disc inserted into my dvd-rom drive that there was a memory diagnostic tool.

I had thought of testing each stick one at a time and so i did, basically i inserted just one of the RAM sticks and ran the memory diagnostic, no errors found, ran then with 2 x 2GB sticks, no errors found, then took the second stick out and tried one of the others......

Almost straight away the diagnostic said that there were hardware issues.

Dud RAM!!

Then tested the last stick and this too had no errors, so i then inserted all three good RAM and ran a full standard test using the diagnostic and with the 6GB RAM installed all seems well according to the diagnostic.

Thing is, i know i had some dud RAM but what from there? Are my other errors all related to this??

I really don't know, i am worried that maybe a virus got on while i was without internet security, i have had bad pool header and non page file errors too, i am not sure what these are at all??

Also do i now attempt a clean install of windows 7 or simply a repair? there does seem to be good motive for both??

Thanks for all your help,

The elevated cmd, i am not sure about, i tried the sfc/scannow and it wouldn't allow me to do it.

I am running Home Premium Win 7 64 bit.

If it is a virus will the repair option get rid of it?

If there are still driver issues, how do i sort these out without risking further random crashes?

Should i just clean install........ i ponder!

 

[CommonTater]

Well, decided to do something that i thought of earlier which i now wish i had done much soooooner as it were, i don't know if this is the final answer but i noticed that on start up when pressing F5 at the ASUS boot screen with the Windows 7 install disc inserted into my dvd-rom drive that there was a memory diagnostic tool.

I had thought of testing each stick one at a time and so i did, basically i inserted just one of the RAM sticks and ran the memory diagnostic, no errors found, ran then with 2 x 2GB sticks, no errors found, then took the second stick out and tried one of the others......

Almost straight away the diagnostic said that there were hardware issues.

Dud RAM!!

Then tested the last stick and this too had no errors, so i then inserted all three good RAM and ran a full standard test using the diagnostic and with the 6GB RAM installed all seems well according to the diagnostic.

Thing is, i know i had some dud RAM but what from there? Are my other errors all related to this??

I really don't know, i am worried that maybe a virus got on while i was without internet security, i have had bad pool header and non page file errors too, i am not sure what these are at all??

Also do i now attempt a clean install of windows 7 or simply a repair? there does seem to be good motive for both??

Thanks for all your help,

The elevated cmd, i am not sure about, i tried the sfc/scannow and it wouldn't allow me to do it.

I am running Home Premium Win 7 64 bit.

If it is a virus will the repair option get rid of it?

If there are still driver issues, how do i sort these out without risking further random crashes?

Should i just clean install........ i ponder!

Before you end up wasting an enormous amout *more* of your time... now that you know what the problem is (most likely)... get hold of tech support and get the hardware working and stabilized before you even consider screwing about with more software stuff.... Well, unless, of course, you truly enjoy spinning your wheels and going noplace.

 

[gregrocker]

A clean reinstall is always a good option, like getting a new computer - except better since new computers have corrupting bloatware larded on them.

You might want to try running awhile with the bad RAM removed.

To run an elevated Command prompt, type CMD in start Search box, right click to Run As Admin and type sfc /scannow to check integrity of System files.

A Repair Install reinstalls the OS while keeping all Programs, files and settings in place. It is next best to a Clean Reinstall since corruption can be imported in Settings.

Neither will remove a virus, which needs to be done by using a virus scan like superior free MS Security Essentials and Malwarebytes. I would also run Spybot S&D from Safe Mode (tap F8 at bootup) after installing and updating from Desktop.

 

[Nomad8459]

Decided to do the repair option, i instantly started windows security essentials upon entering the OS, this promptly found 3 or 4 trojans, nasty things!!

Also installed Spybot S+D to double check things.

System seems much more stable without that DUD RAM!

Now running on 6GB at the moment until i can get them to send me some more RAM.

Going to try and update drivers and install windows updates now that the system is more stable and hopefully should be able to resolve most issues from here...

Again thanks for help....

 

[gregrocker]

You need to determine with certainty that your machine is cleaned up. An infestation of Trojans as you have can be a terminal situation if not. I would run MSE in Safe Mode, as well as Spybot as specified before. Then I'd run Malwarebytes to be sure. You need to know that you are clean, as if not then you have no choice but to wipe the HD and reinstall.

Do you have access to an Win7 installer of your version? You will need one to do a Repair Install (Upgrade over itself from desktop) or reinstall, or for its repair console if the system becomes unbootable. If not, then make a Repair CD asap since you have no way to repair startup if it fails.