BSOD on windows 7

[mvali]

Hello Here is the memory minidump asked for diagnostics.

The system is AMD x2 4600 with gigabyte motherboard m61pme-s2.
\Haev received may bsod screens. Tested memory, the seahate hdd sith seatools give no error. Updated the video driver from the producer and it appears top be stable..
Until i installed the printer epson DX4450 producer drivers (old one's) as the client ordered.. And now I'm getting this screen again. And I'm notsute it is from printer drivers

Windows 7 x64, sp1 updated.

112612-19000-01.dmp
26.11.2012 21:29:35 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02a06b05 fffff880`04931e90 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\112612-19000-01.dmp 2 15 7601 284.008

Please let me know what can I do to solve this.
Thank You

 

[mvali]

Maybe this will help you figure out what happened from BlueScreenView program:
==================================================
Dump File : 112612-19000-01.dmp
Crash Time : 26.11.2012 21:29:35
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02a06b05
Parameter 3 : fffff880`04931e90
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112612-19000-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 284.008

Please Help me understand what happened here.
Thank You

 

[Shintaro]

Welcome to the W7 Forums.

Please start by updating you nVidia drivers.

If you still have crashes after you update the Video drivers, then please enable Driver Verifier:

Driver verifier

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:

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft and click "Next"
7. 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.

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.

Let us know how you go.