[rshaffer61]

OK now get the smsbus and xeon processor drivers. Install the smbus first please.

[Advertisements]

ok, updated those. will do them incrementally

thanks for all of your wonderful help

[jogibso1]

ok, updated those. will do them incrementally

thanks for all of your wonderful help

[rshaffer61]

No problem and I justt help that getting all these drivers updated will do the trick for you.

[jogibso1]

Well, I have been updating drivers daily, two at a time, and continue to have crash issues, but kept going hoping I'd get to the problem one.

Then I tried installing the Dell Wireless 1702 driver thru DriverMax, and the machine crashed. One rebooted I tried again, and now my wireless card is unreachable, I cant install the driver, and I cant find my wireless network or turn it on. Is the card now unusable? Hard wiring into this machine isnt an option because of where its located, so I am totally off network now. Any ideas??

[rshaffer61]

OK go into Device Manager and find the card listed. expand the entry and you should be given the option to rollback the driver which should resolve that issue.

Can you get a new WhoCrashed for me so I can see where the little critter is hiding.

[jogibso1]

Rollback is not activated...it's the only option I cant click








System Information (local)
--------------------------------------------------------------------------------

computer name: JOSHDESKTOP-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i5-3450 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8551428096 total
VM: 2147352576, free: 1915551744




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 10/6/2013 1:57:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-31559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x755E2E09, 0x2, 0x0, 0xFFFFF880075C7B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 10/6/2013 1:57:01 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4A (0x755E2E09, 0x2, 0x0, 0xFFFFF880075C7B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/4/2013 1:41:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-57751-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x75152E09, 0x2, 0x0, 0xFFFFF88006975B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/4/2013 12:06:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-27315-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x738D2E09, 0x2, 0x0, 0xFFFFF8800648FB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/4/2013 5:58:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-28532-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74212E09, 0x2, 0x0, 0xFFFFF88006952B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/4/2013 4:04:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-37502-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74942E09, 0x2, 0x0, 0xFFFFF88006438B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 10/2/2013 7:33:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100213-50029-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74A12E09, 0x2, 0x0, 0xFFFFF880088A1B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/1/2013 1:32:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093013-29811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x736E2E09, 0x2, 0x0, 0xFFFFF88008A7EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/28/2013 3:00:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-22666-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73A22E09, 0x2, 0x0, 0xFFFFF88007C64B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/28/2013 7:12:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-21231-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x750D2E09, 0x2, 0x0, 0xFFFFF8800867BB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/27/2013 3:17:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-22635-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73932E09, 0x2, 0x0, 0xFFFFF88008A7EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 8:12:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-47720-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73B42E09, 0x2, 0x0, 0xFFFFF880088B2B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 7:42:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-19125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73EF2E09, 0x2, 0x0, 0xFFFFF88007CFCB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 4:24:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-24523-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74892E09, 0x2, 0x0, 0xFFFFF880088F2B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 11:21:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-19624-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73E52E09, 0x2, 0x0, 0xFFFFF88007C9AB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

26 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually 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.

[rshaffer61]

OK lets try a different approach.

SFC /Scannow Win7

Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.

[jogibso1]

did it, the sfcdetails.txt was totally blank...

[rshaffer61]

OK found some other causes of this error in my research so we'll start with looking at those possibilities.

Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.

• It is normally the key above your number pad between the F12 key and the Scroll Lock key
• Now go to Start and then to All Programs
• Scroll to Accessories and then click on Paint
• In the Empty White Area click and hold the CTRL key and then click the V
• Go to the File option at the top and click on Save as
• Save as file type JPEG and save it to your Desktop
• Attach it to your next reply

Please download and run Hardware Monitor
Installation (setup version only)
HWMonitor is a hardware monitoring program that reads PC systems main health sensors : voltages, temperatures, fans speed.
The program handles the most common sensor chips, like ITE® IT87 series, most Winbond® ICs, and others. In addition, it can read modern CPUs on-die core thermal sensors, as well has hard drives temperature via S.M.A.R.T, and video card GPU temperature. Please get a screenshot of the sensors window and post it in your next reply.





Do you know what DirectX version you have installed as that may be a possible reason for this. Also how often do you clean the inside of the system out using a can of compressed air?

[jogibso1]

DirectX...I have no idea the version. I searched and cannot tell but know it is there.

I seldom clean out the system, but perhaps I should start.

Is there a simple fix to getting the machine back online? every wireless driver Ive tried hasnt worked (I am doing all of my communication through a different machine, and using USBs to transfer files)

[rshaffer61]

I found 3 different wireless drivers on Dell's site for your system

Intel 2230


Dell Wifi and BT driver dated 5\13\13.
This package provides driver for Dell DW1704 BT4.0 + HS


Dell Wifi and BT driver dated 3/14/2013. This package provides driver for Dell DW1703 BT4.0 + HS Driver.


One of these 3 should be the correct driver. The other way you can do this is to delete the wireless driver completely, reboot and then manually install all of the three above. One will work I'm sure.

[jogibso1]

I tried them all. No dice. This is really frustrating.


They give me something to this effect:
setup error:
This software package cannot be installed on your system. This setup application will exit.

The driver originally was this one

dell wireless 1702 802.11b/g/v (2.4ghz) driver

but somehow DriverMax rendered it unusable or corrupt. I cant even find it on DriverMax anymore!

[jogibso1]

Going to a system restore point to before the last time I ran DriverMax. It's the only thing I can think of. From what I could tell, the driver that I THINK was giving me trouble isnt even a part of that list you sent, which is really confusing.

[jogibso1]

never mind, that didnt work either .

Sorry this is such a pain; losing connectivity is collateral damage from other problems i guess

[rshaffer61]

If drivermax restore didn't work you can use the system restore point.


How To Restore back to a earlier date.


To do a System Restore follow these steps:

 Click Start and then to All Programs
 Scroll to Accessories and then System Tools
 Click on System Restore
 A Welcome screen will come up and you need to click on Restore My Computer To A Earlier Date
 Then click on Next
 Now you will see in the window Select A Restore Point. From here select a date a couple of days before the problem started.
 Then click Next
 On the Confirm Restore Point Selection window verify the Restore Point you chose is correct.
 Close all open programs and click Next
 The computer will now automatically shut down and reboot. When it restarts you will see ”Restoration Complete” page and then click OK
