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

Windows 7: BSOD I suspect product 768_1

05 Sep 2012   #1

Windows 7 Home Premium 64bit
BSOD I suspect product 768_1

I just recently reformatted my hard drive and did a clean install of Windows 7 home edition 64bit.

I can't nail this down but I think it's a USB driver issue. It reboots almost every hour only when the PC is unattended. The message logs all refer to product 768_1 whatever that is.

Example details:
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.
Locale ID: 1033

Extra information about the problem
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA800D82B440
BCP3: FFFFFA800D82B720
BCP4: FFFFF8000339C510
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I appreciate any help.


My System SpecsSystem Spec
07 Sep 2012   #2

Microsoft Windows 7 Ultimate: x64 (SP1)

Hello Vectorgeek and welcome to Sevenforums.

* Did you run 64-bit or 32 before this install of Windows?
* What's your temperatures just before a crash?


Problem Devices

Not Available	ACPI\INT33A0\0	The drivers for this device are not installed.
Problem devices can be found in your Device Manager. Search Device Manager in Start, and look for . Note that if the warning sign isn't there, select View on the top of the window, and end with Show hidden devices.

I do not not what this device is all about, but maybe you have more knowledge around it.
SFC /scannow --We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

Tip   Tip
If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker
Best Regards,
My System SpecsSystem Spec
07 Sep 2012   #3

Windows 7 Home Premium 64bit

Wow thank you so much Frederik!

This was a 64 bit install and my temps are fine.

I feel kind of dumb for not checking my device manager. There was one glaring device not found. I vaguely remember this happening before and it turns out it was a Intel Smart Connect driver. I didn't install in on purpose because I don't want it or the features but the chipset requires it to be installed so I installed it. The missing device cleared up right away.

The scan showed no problems with my Windows 7 install. So now I've re-enabled hybernate and I'll see if I have any problems.

This place is a great resource and it's my first time using it even though I've been building PCs for a long time. Thanks again!
My System SpecsSystem Spec
07 Sep 2012   #4

Microsoft Windows 7 Ultimate: x64 (SP1)

You're welcome mate. I sort of meant your previous system, but maybe that was a 64-bit too? I might have misunderstood you. Glad you got it sorted with the device.

The next thing we want to do is Memtest86+. That's about some memory troubleshooting, it's easy as 123!
Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
Be sure to check your warranty rules and regulations before opening your case.
* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.
Thank you for all those kind words!

Best Regards,
My System SpecsSystem Spec
07 Sep 2012   #5

Windows 7 Home Premium 64bit

Yeah the previous install was also Windows 64bit and this was a clean install after Java exploit trojan infection.
I'll have to check my memory when I get a chance. I have two 8gb sticks of ram. Thanks for the additional info Frederik.

My System SpecsSystem Spec
08 Sep 2012   #6

Microsoft Windows 7 Ultimate: x64 (SP1)

Take all the time you'll need, Jerry.
My System SpecsSystem Spec
08 Sep 2012   #7

Windows 7 Home Premium 64bit
Another BSOD after I thought we fixed it.

I thought I had this fixed since I found a missing chipset driver that I thought was causing the problem. I re-enabled hibernate and now I get another BSOD. I'm really in the dark as to what this could be. All devices show up fine with no missing drivers. Windows scan shows a good Windows 7 install. Memory scan shows no errors and everything like games and my Adobe Creative suite all runs great.

Your help is appreciated as always.

My System SpecsSystem Spec
09 Sep 2012   #8

Microsoft Windows 7 Ultimate: x64 (SP1)

Alright Jerry, let's enable 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) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).

For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.

Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD

Then, here's the procedure to run Driver Verifier:
- 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 "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- 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 locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.

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:
Delete these registry keys to stop Driver Verifier from loading (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
Best Regards,
My System SpecsSystem Spec
10 Sep 2012   #9

Windows 7 Home Premium 64bit

I probably won't have the time to do this till Sunday or next week sometime. Right now I've just disabled hybernate and everything works fine. I'll post when I've run the Driver Verifier.

Thanks again for your prompt and informative reply!


My System SpecsSystem Spec
11 Sep 2012   #10

Microsoft Windows 7 Ultimate: x64 (SP1)

Cheers Jerry.

Best Regards,
My System SpecsSystem Spec

 BSOD I suspect product 768_1

Thread Tools

Similar help and support threads for2: BSOD I suspect product 768_1
Thread Forum
BSOD with product 768_1 BSOD Help and Support
BSOD 6.1.7601. local id 1033 servicepack 1 product 768_1 BSOD Help and Support
BSOD using 3ds max 2012 BCCode a Product 768_1 BSOD Help and Support
BSOD when opening folder in MS word. locale id 2057 Product 768_1 BSOD Help and Support
Error Code 124 product 768_1 BSOD Help and Support
BSOD product 768_1 BSOD Help and Support
Memory Crash Dump (BSOD, Product 768_1) BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

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

© Designer Media Ltd

All times are GMT -5. The time now is 08:05 AM.
Twitter Facebook Google+

Windows 7 Forums

Seven Forums Android App Seven Forums IOS App